Collect SQL Server/Process Information - Quickly
Execute this script to get information on SQL server, databases, processes, memory, buffer, locks, etc.
2011-04-21 (first published: 2009-09-03)
5,643 reads
Execute this script to get information on SQL server, databases, processes, memory, buffer, locks, etc.
2011-04-21 (first published: 2009-09-03)
5,643 reads
2011-01-21 (first published: 2011-01-11)
2,904 reads
Script will display current status of SQL server services and even show if not installed. Works on SQL 2005,2008 2008R2. Both 32 and 64 bit servers.
2010-11-15 (first published: 2010-11-09)
3,566 reads
The purpose of this code is to create a T-SQL output that can be execute on SQL Server (2005 and higher) to recofigure the SQL server as compared to the settings on which you have executed this code from.
2010-10-14 (first published: 2010-10-05)
1,377 reads
This script will display information about the instance(s) on your cluster. Name of nodes, active node and drive letters of the resources
2009-05-08 (first published: 2009-04-15)
1,415 reads
Locate and remove/delete user logins from all databases and even SQL server.
2008-08-08
11,202 reads
Do you have more than 10 sql servers you must manage? Most DBA s do, I have over 120 sql instances to manage. Before I used to use ISQL/OSQL in a batch to execute a command on all these instances. It works but not very nice. Below is the code I use to collect information […]
2006-12-28 (first published: 2006-10-16)
805 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers