Find tables unused since last SQL Server restart
This script will return tables that haven't had any user activity since the SQL Server Service was last restarted. SQL 2005+
2011-07-22 (first published: 2010-01-28)
5,575 reads
Kill all SPIDs with a certain user ID
This script is used to disconnect all connections by a particular individual to a server. I use it when I have to disconnect somebody and they have too many processes to do it by hand. Normally, you can just connect the offending process, but if there are multiple processes that are causing a problem , […]
2004-03-08
2,786 reads
Blogs
TSQL Tuesday #188 Growing community
I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...
Time to Revive our YouTube Channel
It’s been forgotten about and neglected for few years but I’ve decided to dust...
Microsoft MVP 2025: Continuing the Data Platform Journey
I am honored to announce that I have been renewed as a Microsoft MVP...
Forums
How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory
Comments posted to this topic are about the item How a Legacy Logic Choked...
Navigating Multi Platform Realities in My Database Life
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
Import/Export SSMS Settings issue
I have tried a number of times to export and then import my SSMS...
Question of the Day
Query Plan Regressions --
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