Some Questions I’ve Answered Recently On Database Administrators Stack Exchange

Fun and No Profit

Normally I don’t have many questions, but here are a couple that I did ask:

• Improve The Performance Of Multiple Date Range Predicates
• XML Query keeps converting < to &lt; and > to &gt;

Here’s the list of answers on dba.stackexchange.com:

• Comparing an aggregate function’s result against a column
• Do I need to run add UNCOMMITTED hints to IndexOptimize?
• Constraint design for maintaining a unique “most recent’ row
• When should I use Query Store over the plan cache?
• Query performance when updating 50 million rows
• Trouble with the EVENTDATA function
• Efficient queue table design and querying
• Plan cache problems with multi-tenant database design
• Optimizing Recursive Common Table Expressions
• How to figure out how many tables cascading deletes touch
• Low selectivity indexes
• What happened to my backups?
• When should I look at SQL Server’s error log?
• The ten millionth question about deleting duplicate/system statistics
• Why is sp_who2 so hard to understand?
• Does indexing a table variable make using one okay?
• Just how stupid is it to set min server memory equal to max server memory?
• Why oh why doesn’t Query Store tell me about tempdb spills?
• Partitioning and Primary Keys
• Advice for switching to using Read Committed Snapshot Isolation
• What do “Parallelism” waits in Query Store translate to?
• How can I tell if the Version Store is causing issues?
• The 10 millions question about default ordering of query results (there isn’t one)
• Help my dynamic SQL is broken
• Another question about queue table design and querying
• Why is SPID -5 and why is it causing blocking?
• Slow In The Application, Fast In SSMS 😭

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 database performance problems quickly. You can also get a quick, low cost health check with no phone time required.