Best Practice to Query SQL Server from Another SQL Server

  • Hi,

    I'm the original poster.  Thank you all for your input it has been very helpful/insightful.

    Going into this post, I was leaning towards replication because we have our sister companies replicating into our data warehouse and it is efficient and we have never have had issues.  Plus, it would not create a new "way" of migrating data in our environment and would use the same method we already use.  The difference with that use case and the one I posted here is that we require large amounts of data from them and need it almost in real time.  This use case does not require the large amounts of data nor has to be real time.  That is why I posted this question to get your thoughts because I thought maybe using a linked server method might be a better practice in this use case.

     

  • best of luck - if you have the chance, try both methods, ignore us all and go with the one that best suits you

    MVDBA

  • MVDBA (Mike Vessey) wrote:

    best of luck - if you have the chance, try both methods, ignore us all and go with the one that best suits you

    Ditto dat!

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • And let us know how it works.

    If you're interested, the decision you make and why, as well as the result of the implementation, would make a nice article to publish here.

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply