• David.Poole (10/5/2008)


    Does it work? Yes

    Should it be used? Not if you want a robust scaleable solution.

    In the environment where I work we had to buy and install a server solely to let users query data away from the live environment.

    We found that our live servers had strange locking and timeout problems which were solved by replicating data to a reporting server.

    However, this has simply shifted the problem elsewhere. The other issue is that we now have an unknown number of "mission critical" applications that are uncatalogued and unsupported. I am currently working on a project where we have to put a compromise solution in place to cater for such unknown mission critical apps.

    There is nothing wrong with the article. It presents a solution that works.

    I agree... nothing wrong with the article.

    Not sure why you think you'd end up with uncatalogued and unsupported apps, though. The method I recommended would be done through supported views (or procs). The Excel spreadsheet is just to make the output "pretty".

    I do, very much, agree that this type of reporting should probably be done through a reporting database rather than the production database for the very reasons you mentioned.

    --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)