sp_what
Better* than sp_who2, with less re-checking data to get answers. Also, it is SnaZy. With a capital Z.
*Dont you just love totally non subjective assessments like this?
2018-11-01 (first published: 2018-10-22)
2,929 reads
Better* than sp_who2, with less re-checking data to get answers. Also, it is SnaZy. With a capital Z.
*Dont you just love totally non subjective assessments like this?
2018-11-01 (first published: 2018-10-22)
2,929 reads
Will take a stored procedure and email the results in a dynamically generated embedded HTML table or as an attachment.
2016-12-05 (first published: 2015-05-29)
2,785 reads
This script returns the date for the most recent log/full backups and checks if a DBCC CHECKDB has ran within a week.
2015-07-23 (first published: 2015-06-23)
1,312 reads
This script simply returns the most recent restore information about databases for a server.
Returns the destination database name, the device used to perform the restore and the restore date.
2015-07-15 (first published: 2015-06-10)
728 reads
2013-12-06 (first published: 2011-01-31)
4,791 reads
This script uses the backup tables to get info on the growth of your database files.
2013-05-07 (first published: 2009-02-03)
14,432 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