Upcoming Events
2024-11-04 @ 09:00 - 17:00
Whether you’re aiming to be the next great query tuning wizard or you simply need to tackle tough business problems at work...read more
2024-11-05 @ 09:00 - 17:00
Picture this: a day crammed with fun, fascinating demonstrations for SQL Server and Azure SQL. This isn’t your typical training day; this session follows the mantra of “learning by doing,” with...read more
2024-09-06 @ 09:00 - 17:00
Whether you want to be the next great query tuning wizard, or you just need to learn how to start solving tough business problems at work, you need a solid understanding of not only what makes things fast, but also what makes them slow.
thx for posting that video. for a long time I didn’t use sp_whoisactive because i wanted to try and write my own. Well, I was an idiot. Such a great tool.
Yeah, a lot of people have that inclination, but they don’t realize that Adam spent north of 100 hours working on it.
I’m all in favor of people doing that stuff to learn how DMVs work and relate, because at some point you’re going to need something outside of what a pre-packaged proc does, or you’ll wanna contribute to an open source project that one is a part of.
Thanks!
Thanks Adam! I have fixed a lot of procedures where I suspected the issue was parameter sniffing, but I never knew how to verify that that was the issue. In fact, just last night, I killed a running proc @ 25+ minutes, applied my fix and it ran in < 5 seconds. Now I can go back and see if that was the actual issue. I will often add 'option (optimize for unknown)' to the end of the select, if I can't find any other problematic joins or missing indexes and it will usually fix the problem. Do you have other potential fixes you would use?
Yeah, tons. You can search my blog for other tips, or you can check out my training videos for in-depth parameter sniffing troublshooting.