DBCC INPUTBUFFER (Transact-SQL)
Applies to: 
SQL Server
Azure SQL Database
Azure SQL Managed Instance
Displays the last statement sent from a client to an instance of SQL Server.
Transact-SQL syntax conventions
Syntax
DBCC INPUTBUFFER ( session_id [ , request_id ] )
[ WITH NO_INFOMSGS ]
Arguments
session_id
The session ID associated with each active primary connection.
request_id
The exact request (batch) to search for within the current session.
The following query returns request_id:
SELECT request_id
FROM sys.dm_exec_requests
WHERE session_id = @@spid;
WITH
Enables options to be specified.
NO_INFOMSGS
Suppresses all informational messages that have severity levels from 0 through 10.
Result sets
DBCC INPUTBUFFER returns a rowset with the following columns.
| Column name | Data type | Description |
|---|---|---|
| EventType | nvarchar(30) | Event type. This could be RPC Event or Language Event. The output will be No Event when no last event was detected. |
| Parameters | smallint | 0 = Text 1- n = Parameters |
| EventInfo | nvarchar(4000) | For an EventType of RPC, EventInfo contains only the procedure name. For an EventType of Language, only the first 4000 characters of the event are displayed. |
For example, DBCC INPUTBUFFER returns the following result set when the last event in the buffer is DBCC INPUTBUFFER (11).
EventType Parameters EventInfo
-------------- ---------- ---------------------
Language Event 0 DBCC INPUTBUFFER (11)
(1 row(s) affected)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Note
Starting with SQL Server 2014 (12.x) SP2, use sys.dm_exec_input_buffer to return information about statements submitted to an instance of SQL Server.
Permissions
SQL Server requires the VIEW SERVER STATE permission, or membership in the sysadmin fixed server role.
Without any of these, users can only view the input buffer of their own session. That means the session_id must be the same as the session ID on which the command is being run. To determine the session ID. execute the following query:
SELECT @@spid;
SQL Database Premium and Business Critical tiers require the VIEW DATABASE STATE permission in the database. SQL Database Standard, Basic, and General Purpose tiers require the SQL Database admin account.
Examples
The following example runs DBCC INPUTBUFFER on a second connection while a long transaction is running on a previous connection.
CREATE TABLE dbo.T1 (Col1 INT, Col2 CHAR(3));
GO
DECLARE @i INT = 0;
BEGIN TRANSACTION
SET @i = 0;
WHILE (@i < 100000)
BEGIN
INSERT INTO dbo.T1
VALUES (@i, CAST(@i AS CHAR(3)));
SET @i += 1;
END;
COMMIT TRANSACTION;
--Start new connection #2.
DBCC INPUTBUFFER (52);