Backup History
Can you tell me the drive we were backing up server #58 to exactly 8 months ago, and, if possible,...
2013-05-14
418 reads
Can you tell me the drive we were backing up server #58 to exactly 8 months ago, and, if possible,...
2013-05-14
418 reads
This script is so simple you’ll start off by asking why you’d ever use it. Then you’ll use it and...
2013-05-14
596 reads
There are two scripts I like to use to look at the file sizes on servers. The first one is...
2013-05-14
443 reads
Copy / Paste formatted text is a nightmare in WordPress. I’m singling out WordPress because I use it, and, from what...
2013-05-13
573 reads
This script looks much more intimidating than the results it produces, so I recommend running it before reading through it. ...
2013-05-11
465 reads
2013-05-10
402 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...
I have tried a number of times to export and then import my SSMS...
Hi I need to connect to a SQL server via FQDN - that is...
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