2005-12-30 (first published: 2005-12-09)
137 reads
2005-12-30 (first published: 2005-12-09)
137 reads
This script returns the index locking strategy informationfor all user tables in a database. It also generates the required TSQL statement to alter locking strategies if required. These statements require CTRL-C and CTRL-V individually into query analyser for execution. Results are best viewed in text only. This TSQL can be wrapped in a stored procedure […]
2002-07-04
1,383 reads
This script reindexes all user and system indexes in the database using the original fillfactor allocated to that index. It can be executed from the Query Analyzer as stand alone SQL or you could wrap it in a stored procedure.
2002-01-11
8,128 reads
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers