I have created this script for one of our client, the requirement was all the databases should be in full recovery model and should be monitored. Also, I added other important parameters like AutoShrink, AutoClose etc. Output:
2020-06-16
1,129 reads
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
By Steve Jones
The PASS Summit goes on tour this year, with a September stop in Dallas....
By Kevin3NF
Settings That Could Be Hurting Your Performance If you’ve ever created a new SQL...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Formatting Dates and Times: The...
Comments posted to this topic are about the item 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