In my scenario, I have a SQL Server Express that is my data source. It periodically produce batch of data, that should be uploaded to a central repository (a SQL Server SE in the cloud). The data source know the central repository, but central repository does not know any possible data source (may change over time). I don't know if SQL Server Express support log shipping, nor I am familiar with this technology, anyway I would specify that for other reason it's not a viable solution.
My current solution is to upload, from data source, through linked server (point to the cloud SQL Server SE), all the data when needed. It's work no doubt, but monitoring the central SQL Server SE (in the cloud) I see a high volume of request. Reading documentation seems to me that pushing data is inefficient and will push a row at time (that explain the poor performance I experience and the volume of request on central SQL Server SE).
I am wondering if there is a way to remotely execute a pull on the central SQL Server, triggered by the remote one. That way I can exploit the fact that pulling data should be efficient that pushing it and bypassing the issue that central SQL Server does not know which data source will contact it and when.