sp_WhoIsActive: Advanced Logging To Tables
Going Further
If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that, and need to solve database performance problems quickly. You can also get a quick, low cost health check with no phone time required.
Related Posts
- Indexing SQL Server Queries For Performance: Equality vs. Inequality Searches
- Why Read Committed Queries Can Still Return Bad Results In SQL Server
- Join Me And Kendra Little At PASS For Two Days Of SQL Server Performance Tuning Precons
- Updates To sp_QuickieStore, sp_HumanEventsBlockViewer, and sp_PressureDetector
This kicks ass. Used it on one of my systems. Even with query store, this grabs details I want without ridiculous navigation.
Aw, thanks! Yeah, I’m pretty happy with it. Glad someone else is actually using it, too.
I use a simple whoisactive table logging, but now I gonna try this out ! Looks awesome !
Thx for all the good stuff !
Great, lemme know how it works out.
Thanks, using your code. I was missing the databasename in the blocking view, which I added by myself. However, the view doesn’t recreate because it’s already there, so I removed the “if view exists” part (the creation is a CREATE OR ALTER which is my preferred way of creating). Also worth to mention is that the objects are created in master. Make sure you change that (in case you don’t want to mess with system databases) in both the job create script and the sp_WhoIsActiveLogging_Main proc