• Eric M Russell - Tuesday, September 26, 2017 10:06 AM

    richardmgreen1 - Tuesday, September 26, 2017 3:03 AM

    Hi all

    Thanks for all the advice.
    We need to move a lot of data on a regular basis (which is why we were looking at replication).

    I don't fancy setting up an ETL process for a couple of hundred tables (but that's what it may come down to).

    A couple of hundred tables are required? The plot thickens. In that case, log-shipping (or simply a daily restore) of the entire database locally would make sense.

    It thickens indeed.....

    Do you have a high availability groups infrastructure in place?  Could you install a readable secondary in the same serverroom as the server that you are making the call from?  The readable secondary database could even reside on the same instance as the server making the call. 

    You can help to reduce the latency in the high availability Group by installing it asynchronously to the Primary.

    Thoughts?