Skip to main content

The trouble with DBCC INPUTBUFFER()

DBCC INPUTBUFFER() is a very handy and easy to remember Database Console Command to show what SQL a specific user (mapped to a SPID) is executing. BUT it only returns a maximum of 255 characters which is often not enough to show the full command being executed.

There are a couple of solutions to this, thankfully. First, however, we need to know which users are currently logged in and their associated SPID (Server Process Identifier). To do this we use the trusty system stored procedure sp_who2:

EXEC sp_who2

Click to enlarge

If we put the SPID we are interested in into:


It returns the command being executed:

Click to enlarge

All well and good, but we can use this piece of code to return the full contents of the buffer:

USE master


SELECT @Handle = sql_handle
FROM sysprocesses
WHERE spid = 54

FROM ::fn_get_sql(@Handle)

Click to enlarge

I have happily been using the above script for years now, but wait there's a problem - ::fn_get_sql is marked as deprecated and though still currently available will be removed from future versions of SQL Server. Therefore we are being encouraged to use the Dynamic Management Function sys.dm_exec_sql_text() to return the text of commands. In the example below I have used sys.dm_exec_requests combined with the aforementioned function to return the contents of the buffer:

SET @spid = 54

SELECT r.session_id SPID
       ,DB_NAME(database_id) 'DBName'
FROM sys.dm_exec_requests r
CROSS APPLY sys.dm_exec_sql_text(r.sql_handle) t
WHERE r.session_id = @spid;

Click to enlarge

This is now my default way of dealing with this situation especially as we have some useful extra columns, however, remembering this (let alone typing it every time I need it) can be a nuisance so I have created a "snippet" from it - a new feature of SQL Server Management Studio 2012 details of which will follow in another posting. Previous to this I used snippets with the aid of SSMS Tools Pack which was free prior to the 2012 version but probably still worth buying if you like the other features it provides.

BTW, have you ever wondered what the double colon :: was before the function name? It is one of the peculiarities of SQL server and is only used in a few instances, more details of which can be found at Karen Delaney's blog.

This piece of code is ideal for a Snippet.


  1. Nice Article !
    This is my pleasure to read your article.
    Really this will help to people of SQL Server Community.

    I have also prepared one article about, Get last executed statement of lead blocker query using SQL Server DBCC Inputbuffer
    You can also visit my article, your comments and reviews are most welcome.


Post a Comment

Popular posts from this blog

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…

Fun and games with the Management Data Warehouse (MDW and Data Collectors)

The SQL Server Management Data Warehouse (when you first come across it) seems to promise so much if the verbiage from Microsoft and some other websites is to to believed. But when you install it you may find that it is not as useful as it could be. This is a shame but we are currently only on v2 of the product with SQL 2012 so one hopes it will improve in subsequent versions.

However, it probably is worth playing with if you have never used it before - at least you can show your boss some reports on general server health when he asks for it and you have nothing else in place.

There is one big problem with it though if you decide that you don't want to use it any more, uninstalling it is not supported! Mad, I know. But as usual some very helpful people in the community have worked out, what seems to me, a pretty safe way of doing it.

I had a problem with my MDW. The data collector jobs were causing a lot of deadlocking on some production servers and impacting performance. It looks…

SSIS Job fails when it calls Excel via the SQL Agent but succeeds from SSDT

If you have an SSIS package which fails when run on a schedule but succeeds when executed interactively in Visual Studio/BIDS/SSDT, it may produce an error like this:
Executed as user: DOMAIN\user. Microsoft (R) SQL Server Execute Package Utility  Version 12.0.4100.1 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  10:52:25  Error: 2017-02-06 10:52:26.26     Code: 0x00000001     Source: Open Spreadsheet and Run Macro      Description: Exception has been thrown by the target of an invocation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  10:52:25  Finished: 10:52:26  Elapsed:  0.485 seconds.  The package execution failed.  The step failed.
The issue is a type of permissions error. Excel needs to have its permissions changed via the DCOM applet in Control Panel. By default it is on “The launching user.” This needs to be changed to a user with more permissions, in this case we have used the service account used by SQL A…