Skip to content

Latest commit

 

History

History
101 lines (75 loc) · 4.51 KB

File metadata and controls

101 lines (75 loc) · 4.51 KB
description sys.dm_exec_input_buffer (Transact-SQL)
title sys.dm_exec_input_buffer (Transact-SQL) | Microsoft Docs
ms.custom
ms.date 11/14/2019
ms.prod sql
ms.prod_service database-engine, sql-database
ms.reviewer
ms.technology system-objects
ms.topic language-reference
f1_keywords
sys.dm_exec_input_buffer
sys.dm_exec_input_buffer _tsql
dm_exec_input_buffer
dm_exec_input_buffer_tsql
dev_langs
TSQL
helpviewer_keywords
sys.dm_exec_input_buffer dynamic management function
ms.assetid fb34a560-bde9-4ad9-aa96-0d4baa4fc104
author markingmyname
ms.author maghan
monikerRange =azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

sys.dm_exec_input_buffer (Transact-SQL)

[!INCLUDEtsql-appliesto-2014sp2-asdb-xxxx-xxx-md]

Returns information about statements submitted to an instance of [!INCLUDEssNoVersion].

Syntax

sys.dm_exec_input_buffer ( session_id , request_id )

Arguments

session_id Is the session ID executing the batch to be looked up. session_id is smallint. session_id can be obtained from the following dynamic management objects:

request_id The request_id from sys.dm_exec_requests. request_id is int.

Table Returned

Column name Data type Description
event_type nvarchar(256) The type of event in the input buffer for the given spid.
parameters smallint Any parameters provided for the statement.
event_info nvarchar(max) The text of the statement in the input buffer for the given spid.

Permissions

On [!INCLUDEssNoVersion], if the user has VIEW SERVER STATE permission, the user will see all executing sessions on the instance of [!INCLUDEssNoVersion]; otherwise, the user will see only the current session.

Important

Running this DMV outside of SQL Server Management Studio against SQL Server without VIEW SERVER STATE permissions (such as in a trigger, stored procedure, or function) throws a permission error on the master database.

On [!INCLUDEssSDS], if the user is the database owner, the user will see all executing sessions on the [!INCLUDEssSDS]; otherwise, the user will see only the current session.

Important

Running this DMV outside of SQL Server Management Studio against Azure SQL Database without owner permissions (such as in a trigger, stored procedure, or function) throws a permission error on the master database.

Remarks

This dynamic management function can be used in conjunction with sys.dm_exec_sessions or sys.dm_exec_requests by doing CROSS APPLY.

Examples

A. Simple example

The following example demonstrates passing a session ID (SPID) and a request ID to the function.

SELECT * FROM sys.dm_exec_input_buffer (52, 0);
GO

B. Using cross apply to additional information

The following example lists the input buffer for sessions with session ID greater than 50.

SELECT es.session_id, ib.event_info
FROM sys.dm_exec_sessions AS es
CROSS APPLY sys.dm_exec_input_buffer(es.session_id, NULL) AS ib
WHERE es.session_id > 50;
GO

See Also