usp_ShrinkAllLogs
Replacement script for usp_ShrinkDBLogs, updates for SQL 2008 deprecating the WITH TRUNCATE_ONLY method.
2009-11-27 (first published: 2009-10-30)
973 reads
Replacement script for usp_ShrinkDBLogs, updates for SQL 2008 deprecating the WITH TRUNCATE_ONLY method.
2009-11-27 (first published: 2009-10-30)
973 reads
When creating XML messages for Service Broker or other applications use this simple method to build a validation XSD.
2009-10-28 (first published: 2009-10-06)
1,494 reads
Ammends the sp_who2 procedure with the input buffer contents, ususally the SQL statement for that SPID
2009-04-24 (first published: 2009-03-27)
1,270 reads
2008-11-20 (first published: 2008-10-06)
967 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