Just Visiting
I made some updates to sp_QuickieStore recently, which you can download here.
The main updates to the code are to:
- Add support for SQL Server 2022 views
- Add the ability to search by query hash, plan hash, and SQL handle
The SQL Server 2022 stuff isn’t important just yet, but… Hey, maybe someday.
The new search functionality is really important though, at least for how I use sp_QuickieStore much of the time. Often, you’ll find hashes and handles in other parts of the database:
- Plan cache
- Deadlock XML
- Blocked process report
- Query plans
There’s still no good way for you to search Query Store by anything. Not plan or query id, not query text, not object names. Nothing.
Don’t worry, I’m here for you.
Some other minor updates were to:
- Improve the help section
- Improve code comments throughout
- Remove the filter to only show successful executions (sometimes you need to find queries that timed out or something)
- If you filter on any hash or handle, I’ll display that in the final output so they’re easy to identify
- Replace TRY_CONVERT with TRY_CAST, which throws errors in fewer circumstances
That’s about all the stuff you need to know about. Aside from that, all my changes were slight logical errors or plumbing to implement the new features.
Thanks for reading!
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 performance problems quickly.
Related Posts
- How To Find Poorly Performing SQL Server Queries To Tune Using Query Store
- SQL Server Community Tools: The Wrap Up And Combined Link
- SQL Server Community Tools: How To Dig Deeper With Expert Mode With sp_QuickieStore
- SQL Server Community Tools: Formatting sp_QuickieStore Output So It’s Easier To Understand
That’s interesting about TRY CAST vs. TRY CONVERT. That may be worth a blog post of its own, especially since it is generally considered better to use CONVERT instead of CAST (specifically for date/time values), so it is interesting that you found TRY_CAST to be less problematic than TRY_CONVERT. Your May 16 post doesn’t address this specific issue, so a new post with more detail on the issue of a difference in errors would be interesting, at least to me. 🙂
It sounds like you have all the tools in your hands to write a post, too.
True, but I couldn’t do it with your delightfully snarky style!
Hi Eric, great stuff as usual. You might want to update a copywrite line in your code.
By all means, don’t be more specific than that!