Lately I've been faced with dual problems: how to spot which stored procs are performing the worst within an application which has been released, and secondly, how to help developers write code that runs quickly before deploying it to production.
Of course you can run Traces, or have a look into System Views, but knowing the how is a lot different to knowing the whiches, whens and whys. For example, which trace events do you enable?
This article by Preethiviraj Kulasingham at SQL Server Universe set off a few light bulbs for me.
No comments:
Post a Comment