This script features as we can through the CTE Top10FilesWithLargerDiskConsumption the top ten data files that are showing greater consumption of hard drive related data-reading activities.
2019-01-15 (first published: 2019-01-08)
1,088 reads
Collect CPU % for a time period and alert if Average CPU usage is high
2019-01-14 (first published: 2019-01-08)
1,794 reads
Quick check SQL connection and process details with current SQL text
2018-12-06 (first published: 2018-11-27)
995 reads
2018-11-30 (first published: 2017-04-01)
1,146 reads
2018-11-29 (first published: 2018-11-23)
472 reads
2018-11-15 (first published: 2018-11-08)
1,608 reads
If you have a SQL Server with a High Availability solution (AlwaysOn Availability Groups, Database Mirroring, etc.), and you also have a bunch of jobs which you need to be run on the Primary server only. You need to be able to "failover" the jobs in case the Primary server is no longer Primary.
2018-11-14 (first published: 2018-11-12)
6,154 reads
Find a string in a stored procedure and replace with powershell
2018-11-13 (first published: 2018-11-06)
1,274 reads
I was using this script to check disk space on individual servers for quite some time. And now since I started to use registered servers for MS SQL, I thought of a little modification to the script.
2018-11-09 (first published: 2018-10-24)
1,179 reads
Some times you need to parse over punch values at the while running a query.
Here is an utility function to help with that task.
2018-11-07 (first published: 2018-10-31)
910 reads
By Steve Jones
It’s a small change, but a handy one. Flyway Desktop (FWD) now includes the...
By Steve Jones
Software is hard. While I love our Lucid Gravity, I realize that they are...
By James Serra
Making Data AI-Ready, Part 2 (This is the second article in a three-part series...
Hi everyone, I'm hoping some of the longtime SQL Server professionals here might be...
Comments posted to this topic are about the item Checking the Error Log II
Comments posted to this topic are about the item Parameter Sniffing on SQL Server...
What is the reason I should change my old code that uses xp_readerrorlog?
See possible answers