• LinksUp (11/19/2013)


    pmscorca (11/19/2013)


    Ultimately, the batch approach seems the better solution ..., isn't it?

    Test, test, and test!!

    There are a number of techniques to populate a test table with millions of rows in a very short time. Then you can implement the different different scenarios to see which is the fastest, uses the fewest resources, has the best execution plan, etc. . .

    +1000

    When dealing with performance improvements, the only sure way to choose is by testing and testing again after any changes on SQL Server.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2