Skip to main content

An easier way to deal with sp_who2

As a DBA sp_who2 is a stored procedure I use on a daily basis, however, it is not possible to filter its output or manipulate it in any way.

To help with this I use the simple script below as a snippet that exports the output of sp_who2 to a temporary table where I can play with the results much easier.

-- Export sp_who2 to temp table
IF EXISTS (SELECT 1 FROM tempdb..sysobjects WHERE id=OBJECT_ID('tempdb..#spwho2')) DROP TABLE #spwho2
CREATE TABLE #spwho2(
    [SPID] INT
    ,[Status] VARCHAR(30)
    ,[Login] VARCHAR(50)
    ,[HostName] VARCHAR(30)
    ,[BlkBy] VARCHAR(30)
    ,[DBName] VARCHAR(30)
    ,[Command] VARCHAR(50)
    ,[CPUTime] INT
    ,[DiskIO] INT
    ,[LastBatch] VARCHAR(30)
    ,[ProgramName] VARCHAR(100)
    ,[SPID2] INT
    ,[RequestID] INT
)
INSERT INTO #spwho2
EXEC sp_who2

SELECT [SPID]
       ,[Status]
       ,[Login]
       ,[HostName]
       ,[BlkBy]
       ,[DBName]
       ,[Command]
       ,[CPUTime]
       ,[DiskIO]
       ,[LastBatch]
       ,[ProgramName]
       ,[SPID2]
       ,[RequestID]
FROM #spwho2








Comments

Popular posts from this blog

Generate scripts to attach multiple databases

There is a handy little "by product", if you like, when running queries which means you can quickly generate scripts to do different things. Below is an example of generating multiple "attach" commands that you can copy from the results pane into the main SSMS window for execution. I have found this very handy in the past:


SELECT 'CREATE DATABASE ['+name+'] ON ( FILENAME = N''F:\MSSQL\Data\'+name+'.mdf'' ), ( FILENAME = N''E:\MSSQL\Log\'+name+'_log.ldf'' )  FOR ATTACH GO ' FROMmaster.dbo.sysdatabases WHEREnamenotin('master','msdb','model','tempdb')
ORDERBYname

How to move the Microsoft Assessment and Planning Toolkit (MAP) database to a different drive

The Microsoft Assessment and Planning Toolkit (MAP) is a very useful tool for scanning your network to find instances of SQL Server plus all manner of detailed information about the installed product, OS and hardware it sits on.


<Click image to enbiggen>
There is an issue with it the database it uses to store the data it collects, however. Assuming you don't have an instance called MAPS on your server, the product will install using LocalDB (a cut down version of SQL Server Express) and puts the databases on your C: drive. If you then scan a large network you could easily expand the database to 10GB which may cause issues on a server when that drive is often one of the smallest. However, there is a simple solution: connect to LocalDB using Management Studio, detach the databases, move to a different drive, set permissions on the new location if required and reattach the database. How do you connect to LocalDB? Here you go:

Connect to (localdb)\MAPTOOLKIT


The databases I move…

The Purge SQL Agent Job for MDW takes a long time to complete

I use the dbWarden alerts to inform me if a SQL job is taking longer to complete than normal and I got one this morning:
I noticed by looking at the history this purge job was gradually taking longer and longer to complete each day since I installed it again (see mylast post on this):
RunDate RunTime Duration ExecutionStatus JobName 04/10/2013 02:00:01 00:00:45 Succeded mdw_purge_data_[MDW] 05/10/2013 02:00:00 00:13:27 Succeded mdw_purge_data_[MDW] 06/10/2013 02:00:00 00:17:03 Succeded mdw_purge_data_[MDW] 07/10/2013 02:00:01