Who Truncated That Table and What Do I Do Now?
This article describes a way to identify the user who truncated the table & how you can recover the data.
2015-02-20 (first published: 2014-06-05)
34,461 reads
Sujeet Singh
Instant File Initialization
This article describes a way to speed up various file operations performed by SQL Server.
2014-07-10
4,437 reads
Automating Database Restores
This article describes a way to automatically restore multiple database backups from a directory.
2014-04-21
6,190 reads
2012-09-17
2,711 reads
Blogs
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...
What is KTLO? Keep The Lights On vs Project Work in Agile
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
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