| title | Dynamic Management Views (Transact-SQL) | Microsoft Docs | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| ms.custom | |||||||||||
| ms.date | 06/29/2017 | ||||||||||
| ms.prod | sql | ||||||||||
| ms.prod_service | database-engine, sql-database, sql-data-warehouse, pdw | ||||||||||
| ms.reviewer | |||||||||||
| ms.technology | system-objects | ||||||||||
| ms.topic | language-reference | ||||||||||
| dev_langs |
|
||||||||||
| helpviewer_keywords |
|
||||||||||
| ms.assetid | cf893ecb-0bf6-4cbf-ac00-8a1099e405b1 | ||||||||||
| author | stevestein | ||||||||||
| ms.author | sstein | ||||||||||
| monikerRange | >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEtsql-appliesto-ss2008-all-md]
Dynamic management views and functions return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance.
Important
Dynamic management views and functions return internal, implementation-specific state data. Their schemas and the data they return may change in future releases of [!INCLUDEssNoVersion]. Therefore, dynamic management views and functions in future releases may not be compatible with the dynamic management views and functions in this release. For example, in future releases of [!INCLUDEssNoVersion], Microsoft may augment the definition of any dynamic management view by adding columns to the end of the column list. We recommend against using the syntax SELECT * FROM dynamic_management_view_name in production code because the number of columns returned might change and break your application.
There are two types of dynamic management views and functions:
-
Server-scoped dynamic management views and functions. These require VIEW SERVER STATE permission on the server.
-
Database-scoped dynamic management views and functions. These require VIEW DATABASE STATE permission on the database.
Dynamic management views can be referenced in [!INCLUDEtsql] statements by using two-part, three-part, or four-part names. Dynamic management functions on the other hand can be referenced in [!INCLUDEtsql] statements by using either two-part or three-part names. Dynamic management views and functions cannot be referenced in [!INCLUDEtsql] statements by using one-part names.
All dynamic management views and functions exist in the sys schema and follow this naming convention dm_*. When you use a dynamic management view or function, you must prefix the name of the view or function by using the sys schema. For example, to query the dm_os_wait_stats dynamic management view, run the following query:
SELECT wait_type, wait_time_ms
FROM sys.dm_os_wait_stats; To query a dynamic management view or function requires SELECT permission on object and VIEW SERVER STATE or VIEW DATABASE STATE permission. This lets you selectively restrict access of a user or login to dynamic management views and functions. To do this, first create the user in master and then deny the user SELECT permission on the dynamic management views or functions that you do not want them to access. After this, the user cannot select from these dynamic management views or functions, regardless of database context of the user.
Note
Because DENY takes precedence, if a user has been granted VIEW SERVER STATE permissions but denied VIEW DATABASE STATE permission, the user can see server-level information, but not database-level information.
Dynamic management views and functions have been organized into the following categories.
GRANT Server Permissions (Transact-SQL)
GRANT Database Permissions (Transact-SQL)
System Views (Transact-SQL)