Skip to content

Commit 8e92fe9

Browse files
LitKndLitKnd
committed
Incorporating feedback
1 parent 75f8ed9 commit 8e92fe9

20 files changed

Lines changed: 74 additions & 66 deletions

‎docs/includes/paragraph-content/sql-on-premises-vs-azure-similar-sys-views-include.md‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,15 @@
77

88
Some Transact-SQL code examples written for SQL Server on-premises need small changes to run in the cloud. One category of such code examples involves system views whose name prefixes differ slightly between the two database systems:
99

10-
- **server\_**   -   _prefix for SQL Server and SQL Managed Instance_
10+
- **server\_**   -   _prefix for SQL Server and Azure SQL Managed Instance_
1111
- **database\_**   -   _prefix for Azure SQL Database and SQL Managed Instance_
1212

13-
[!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] can only execute database-scoped sessions. [!INCLUDE[ssazuremi_md](../../includes/ssazuremi_md.md)] supports both database-scoped sessions and more capable server-scoped sessions.
13+
Azure SQL Database supports only database-scoped sessions. [SQL Server Management Studio](../../ssms/sql-server-management-studio-ssms.md) (SSMS) fully supports database-scoped sessions for Azure SQL Database: an **Extended Events** node containing database-scoped sessions appears under each database in [Object Explorer](../../ssms/object/object-explorer.md).
14+
15+
Azure SQL Managed Instance supports both database-scoped sessions and server-scoped sessions. Server-scoped sessions are recommended for managed instances. SSMS fully supports server-scoped sessions for SQL Managed Instance: an **Extended Events** node containing all server-scoped sessions appears under the **Management** folder for each managed instance in Object Explorer.
16+
17+
> [!NOTE]
18+
> Database-scoped sessions are not displayed in Object Explorer in SSMS for Azure SQL Managed Instance. Database-scoped sessions may only be queried and managed with Transact-SQL when using a managed instance.
1419
1520
For illustration, the following table lists and compares two subsets of the system views. For brevity, the subsets are restricted to view names that also contain the string `_event`. The subsets have differing name prefixes because they come from two different database systems.
1621

‎docs/relational-databases/extended-events/extended-events.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,15 @@ author: LitKnd
1414
ms.author: kendralittle
1515
ms.custom:
1616
- intro-overview
17-
ms.date: 03/29/2022
17+
ms.date: 04/18/2022
1818
monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
1919
---
2020

2121
# Extended events overview
2222

2323
[!INCLUDE [SQL Server Azure SQL Database SQL Managed instance](../../includes/applies-to-version/sql-asdbmi.md)]
2424

25-
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] The Extended Events architecture enables users to collect as much or as little data as is necessary to troubleshoot or identify a performance problem. Extended Events is highly configurable, lightweight, and scales very well. For more information, see [Extended Events Architecture](extended-events.md#extended-events-architecture).
25+
The Extended Events architecture enables users to collect as much or as little data as is necessary to troubleshoot or identify a performance problem. Extended Events is highly configurable, lightweight, and scales very well. For more information, see [Extended Events Architecture](extended-events.md#extended-events-architecture).
2626

2727
Extended Events replace the deprecated [SQL Trace](../../relational-databases/sql-trace/sql-trace.md) and SQL Server Profiler features.
2828

‎docs/relational-databases/system-catalog-views/sys-database-connection-stats-azure-sql-database.md‎

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
description: "sys.database_connection_stats (Azure SQL Database)"
33
title: "sys.database_connection_stats"
44
titleSuffix: Azure SQL Database
5-
ms.date: "03/30/2022"
5+
ms.date: "04/18/2022"
66
ms.service: sql-database
77
ms.reviewer: ""
88
ms.topic: "reference"
@@ -75,20 +75,21 @@ This view may not include all connection and error information:
7575

7676
- This view does not include all [!INCLUDE[ssSDS](../../includes/sssds-md.md)] database errors that could occur, only those specified in Event Types in [sys.event_log (Azure SQL Database)](../../relational-databases/system-catalog-views/sys-event-log-azure-sql-database.md).
7777
- If there is a machine failure within the [!INCLUDE[ssSDS](../../includes/sssds-md.md)] datacenter, a small amount of data may be missing from the event table.
78-
- If an IP address has been blocked through DoSGuard, connection attempt events from that IP address cannot be collected and will not appear in this view.
78+
- If an IP address has been blocked through [DoSGuard](/azure/security/fundamentals/infrastructure-sql#dosguard), connection attempt events from that IP address cannot be collected and will not appear in this view.
7979

8080
## Permissions
8181

82-
Users with permission to access the **master** database on the [logical server](/azure/azure-sql/database/logical-servers) in Azure SQL Database have read-only access to this view.
82+
Requires permission to access the **master** database on the [logical server](/azure/azure-sql/database/logical-servers) in Azure SQL Database.
8383

8484
## Examples
8585

86-
This example queries **sys.database_connection_stats** to return a summary of the database connections that occurred between noon on March 29, 2022 and noon on March 30, 2022 (UTC). By default, the query results are sorted by **start_time** (ascending order). Connect to the **master** database on the [logical server](/azure/azure-sql/database/logical-servers) in Azure SQL Database to run the query.
86+
This example queries **sys.database_connection_stats** to return a summary of the database connections that occurred between noon on March 29, 2022 and noon on March 30, 2022 (UTC). Connect to the **master** database on the [logical server](/azure/azure-sql/database/logical-servers) in Azure SQL Database to run the query.
8787

8888
```sql
89-
SELECT database_name, start_time, end_time, success_count, total_failure_count, connection_failure_count0
89+
SELECT database_name, start_time, end_time, success_count, total_failure_count, connection_failure_count
9090
FROM sys.database_connection_stats
91-
WHERE start_time>='2022-03-29 12:00:00' and end_time<='2022-03-30 12:00:00';
91+
WHERE start_time>='2022-03-29 12:00:00' and end_time<='2022-03-30 12:00:00'
92+
ORDER BY start_time ASC;
9293
```
9394

9495
## Next steps

‎docs/relational-databases/system-catalog-views/sys-database-event-session-actions-azure-sql-database.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: "sys.database_event_session_actions (Azure SQL Database and Azure S
33
title: "sys.database_event_session_actions"
44
titleSuffix: Azure SQL Database and Azure SQL Managed Instance
55
ms.custom: ""
6-
ms.date: "03/30/2022"
6+
ms.date: "04/18/2022"
77
ms.prod: sql
88
ms.prod_service: "database-engine, sql-database"
99
ms.reviewer: ""
@@ -21,7 +21,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
2121

2222
Returns a row for each action on each event of a database-scoped event session. For information on actions in *active* database-scoped event sessions, see [sys.dm_xe_database_session_event_actions](../system-dynamic-management-views/sys-dm-xe-database-session-event-actions-azure-sql-database.md).
2323

24-
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and more capable [server-scoped sessions](../extended-events/extended-events.md).
24+
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and [server-scoped sessions](../extended-events/extended-events.md). Server-scoped sessions are recommended for managed instances: learn more in [CREATE EVENT SESSION](../../t-sql/statements/create-event-session-transact-sql.md#code-examples-can-differ-for-azure-sql-database-and-sql-managed-instance).
2525

2626
|Column name|Data type|Description|
2727
|-----------------|---------------|-----------------|

‎docs/relational-databases/system-catalog-views/sys-database-event-session-events-azure-sql-database.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: "sys.database_event_session_events (Azure SQL Database and Azure SQ
33
title: "sys.database_event_session_events"
44
titleSuffix: Azure SQL Database and Azure SQL Managed Instance
55
ms.custom: ""
6-
ms.date: "03/30/2022"
6+
ms.date: "04/18/2022"
77
ms.prod: sql
88
ms.prod_service: "database-engine, sql-database"
99
ms.reviewer: ""
@@ -21,7 +21,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
2121

2222
Returns a row for each event in a database-scoped event session. For information on events in *active* database-scoped sessions, see [sys.dm_xe_database_session_events](../system-dynamic-management-views/sys-dm-xe-database-session-events-azure-sql-database.md).
2323

24-
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and more capable [server-scoped sessions](../extended-events/extended-events.md).
24+
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and [server-scoped sessions](../extended-events/extended-events.md). Server-scoped sessions are recommended for managed instances: learn more in [CREATE EVENT SESSION](../../t-sql/statements/create-event-session-transact-sql.md#code-examples-can-differ-for-azure-sql-database-and-sql-managed-instance).
2525

2626
|Column name|Data type|Description|
2727
|-----------------|---------------|-----------------|

‎docs/relational-databases/system-catalog-views/sys-database-event-session-fields-azure-sql-database.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: "sys.database_event_session_fields (Azure SQL Database and Azure SQ
33
title: "sys.database_event_session_fields"
44
titleSuffix: Azure SQL Database and Azure SQL Managed Instance
55
ms.custom: ""
6-
ms.date: "03/30/2022"
6+
ms.date: "4/18/2022"
77
ms.prod: sql
88
ms.prod_service: "database-engine, sql-database"
99
ms.reviewer: ""
@@ -21,7 +21,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
2121

2222
Returns a row for each customizable column that was explicitly set on [events](sys-database-event-session-events-azure-sql-database.md) and [targets](sys-database-event-session-targets-azure-sql-database.md) in a database-scoped event session.
2323

24-
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and more capable [server-scoped sessions](../extended-events/extended-events.md).
24+
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and [server-scoped sessions](../extended-events/extended-events.md). Server-scoped sessions are recommended for managed instances: learn more in [CREATE EVENT SESSION](../../t-sql/statements/create-event-session-transact-sql.md#code-examples-can-differ-for-azure-sql-database-and-sql-managed-instance).
2525

2626
|Column name|Data type|Description|
2727
|-----------------|---------------|-----------------|

‎docs/relational-databases/system-catalog-views/sys-database-event-session-targets-azure-sql-database.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: "sys.database_event_session_targets (Azure SQL Database and Azure S
33
title: "sys.database_event_session_targets"
44
titleSuffix: Azure SQL Database and Azure SQL Managed Instance
55
ms.custom: ""
6-
ms.date: "03/30/2022"
6+
ms.date: "4/18/2022"
77
ms.prod: sql
88
ms.prod_service: "database-engine, sql-database"
99
ms.reviewer: ""
@@ -22,7 +22,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
2222

2323
Returns a row for each event target for a database-scoped event session. For information about *active* database-scoped sessions, see [sys.dm_xe_database_session_targets](../system-dynamic-management-views/sys-dm-xe-database-session-targets-azure-sql-database.md).
2424

25-
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and more capable [server-scoped sessions](../extended-events/extended-events.md).
25+
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and [server-scoped sessions](../extended-events/extended-events.md). Server-scoped sessions are recommended for managed instances: learn more in [CREATE EVENT SESSION](../../t-sql/statements/create-event-session-transact-sql.md#code-examples-can-differ-for-azure-sql-database-and-sql-managed-instance).
2626

2727
|Column name|Data type|Description|
2828
|-----------------|---------------|-----------------|

‎docs/relational-databases/system-catalog-views/sys-database-event-sessions-azure-sql-database.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ description: "sys.database_event_sessions (Azure SQL Database and Azure SQL Mana
33
title: "sys.database_event_sessions"
44
titleSuffix: Azure SQL Database and Azure SQL Managed Instance
55
ms.custom: ""
6-
ms.date: "03/30/2022"
6+
ms.date: "4/18/2022"
77
ms.service: sql-database
88
ms.reviewer: ""
99
ms.topic: "reference"
@@ -19,7 +19,7 @@ monikerRange: "= azuresqldb-current"
1919

2020
Lists all the database-scoped event session definitions that exist in the current database. For information about *active* database-scoped event sessions, see [sys.dm_xe_database_sessions](../system-dynamic-management-views/sys-dm-xe-database-sessions-azure-sql-database.md).
2121

22-
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and more capable [server-scoped sessions](../extended-events/extended-events.md).
22+
Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/database/xevent-db-diff-from-svr). Azure SQL Managed Instance supports both database-scoped sessions and [server-scoped sessions](../extended-events/extended-events.md). Server-scoped sessions are recommended for managed instances: learn more in [CREATE EVENT SESSION](../../t-sql/statements/create-event-session-transact-sql.md#code-examples-can-differ-for-azure-sql-database-and-sql-managed-instance).
2323

2424
|Column name|Data type|Description|
2525
|-----------------|---------------|-----------------|
@@ -37,7 +37,7 @@ Azure SQL Database supports only [database-scoped sessions](/azure/azure-sql/dat
3737

3838
## Permissions
3939

40-
Requires the VIEW SERVER STATE permission.
40+
Requires the VIEW DATABASE STATE permission.
4141

4242
## Next steps
4343

‎docs/relational-databases/system-catalog-views/sys-event-log-azure-sql-database.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
description: "sys.event_log (Azure SQL Database)"
33
title: "sys.event_log (Azure SQL Database)"
44
ms.custom: ""
5-
ms.date: "03/30/2022"
5+
ms.date: "04/18/2022"
66
ms.service: sql-database
77
ms.prod_service: "sql-database"
88
ms.reviewer: ""
@@ -29,7 +29,7 @@ monikerRange: "= azuresqldb-current"
2929
Returns successful [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] database connections and connection failures. You can use this information to track or troubleshoot your database activity.
3030

3131
> [!CAUTION]
32-
> For installations having a large number of databases or high numbers of logins, activity in sys.event_log can cause limitations in performance, high CPU usage, and possibly result in login failures. Queries of sys.event_log can contribute to the problem. Microsoft is working to resolve this issue. In the meantime, to reduce the impact of this issue, limit queries of sys.event_log.
32+
> For [logical servers](/azure/azure-sql/database/logical-servers) with a large number of databases and/or high numbers of logins, querying sys.event_log can cause high resource usage in the master database, possibly resulting in login failures. To reduce the impact of this issue, limit queries of sys.event_log.
3333
3434
The `sys.event_log` view contains the following columns.
3535

@@ -118,7 +118,7 @@ Connect to the **master** database on the [logical server](/azure/azure-sql/data
118118

119119
### Query the sys.event_log view
120120

121-
The following query returns all events that occurred between noon on March 25, 2022 and noon on March 30, 2022 (UTC). By default, query results are sorted by **start_time** (ascending order).
121+
The following query returns all events that occurred between noon on March 25, 2022 and noon on March 30, 2022 (UTC). By default, query results are sorted by **start_time** (ascending order).
122122

123123
```sql
124124
SELECT database_name, start_time, end_time, event_category,

‎docs/relational-databases/system-catalog-views/sys-resource-stats-azure-sql-database.md‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
description: "sys.resource_stats returns CPU usage and storage data for an Azure SQL Database. "
33
title: "sys.resource_stats (Azure SQL Database)"
44
ms.custom: ""
5-
ms.date: "03/30/2022"
5+
ms.date: "4/18/2022"
66
ms.service: sql-database
77
ms.topic: "reference"
88
f1_keywords:
@@ -70,18 +70,20 @@ Returns CPU usage and storage data for a database in Azure SQL Database. The dat
7070

7171
You must be connected to the `master` database on the [logical server](/azure/azure-sql/database/logical-servers) to query `sys.resource_stats`.
7272

73-
The following example returns all databases that are averaging at least 80% of compute utilization over the last one week.
73+
The following example returns all databases that are averaging at least 80% of CPU utilization over the last one week.
7474

7575
```sql
7676
DECLARE @s datetime;
7777
DECLARE @e datetime;
7878
SET @s= DateAdd(d,-7,GetUTCDate());
7979
SET @e= GETUTCDATE();
80-
SELECT database_name, AVG(avg_cpu_percent) AS Average_Compute_Utilization
80+
81+
SELECT database_name, AVG(avg_cpu_percent) AS Average_CPU_Utilization
8182
FROM sys.resource_stats
8283
WHERE start_time BETWEEN @s AND @e
8384
GROUP BY database_name
8485
HAVING AVG(avg_cpu_percent) >= 80;
86+
GO
8587
```
8688

8789
## See also

0 commit comments

Comments
 (0)