Skip to content

Commit af3bc00

Browse files
dimitri-furmanrwestMSFT
authored andcommitted
Update SQL DB XE
1 parent f4f1cb9 commit af3bc00

20 files changed

Lines changed: 1988 additions & 2780 deletions
43.3 KB
Loading
41.8 KB
Loading
51.3 KB
Loading
74.4 KB
Loading

azure-sql/database/xevent-code-event-file.md

Lines changed: 97 additions & 456 deletions
Large diffs are not rendered by default.

azure-sql/database/xevent-code-ring-buffer.md

Lines changed: 78 additions & 301 deletions
Large diffs are not rendered by default.

azure-sql/database/xevent-db-diff-from-svr.md

Lines changed: 122 additions & 126 deletions
Large diffs are not rendered by default.
Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,38 @@
11
---
22
author: rwestMSFT
33
ms.author: randolphwest
4-
ms.date: 12/30/2022
4+
ms.date: 10/22/2023
55
ms.service: sql-database
66
ms.topic: include
77
---
8-
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:
8+
Some Transact-SQL code examples written for SQL Server need small changes to run in Azure. One category of such code examples involves catalog views whose name prefixes differ depending on the database engine type:
99

10-
- **server_** - *prefix for SQL Server and Azure SQL Managed Instance*
11-
- **database_** - *prefix for Azure SQL Database and SQL Managed Instance*
10+
- `server_` - *prefix for SQL Server and Azure SQL Managed Instance*
11+
- `database_` - *prefix for Azure SQL Database and SQL Managed Instance*
1212

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).
13+
Azure SQL Database supports only database-scoped event sessions. [SQL Server Management Studio](../../ssms/sql-server-management-studio-ssms.md) (SSMS) fully supports database-scoped event 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).
1414

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.
15+
Azure SQL Managed Instance supports both database-scoped sessions and server-scoped sessions. 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.
1616

1717
> [!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.
18+
> Server-scoped sessions are recommended for managed instances. Database-scoped sessions aren't displayed in Object Explorer in SSMS for Azure SQL Managed Instance. Database-scoped sessions can only be queried and managed with Transact-SQL when using a managed instance.
1919
20-
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.
20+
For illustration, the following table lists and compares two subsets of catalog views. For brevity, the subsets are restricted to view names that also contain the string `_event`. The subsets have differing name prefixes because they support different database engine types.
2121

22-
| Name from SQL Server | Name from cloud service |
22+
| Name in SQL Server and Azure SQL Managed Instance | Name in Azure SQL Database and Azure SQL Managed Instance |
2323
| :--- | :--- |
2424
| server_event_notifications<br />server_event_session_actions<br />server_event_session_events<br />server_event_session_fields<br />server_event_session_targets<br />server_event_sessions<br />server_events<br />server_trigger_events | database_event_session_actions<br />database_event_session_events<br />database_event_session_fields<br />database_event_session_targets<br />database_event_sessions |
2525

26-
The two lists in the preceding table were accurate as of March 2022. For an accurate list, run the following Transact-SQL SELECT statement:
26+
The two lists in the preceding table were accurate as of March 2022. For an up-to-date list, run the following Transact-SQL `SELECT` statement:
2727

2828
```sql
2929
SELECT name
3030
FROM sys.all_objects
3131
WHERE
32-
(name LIKE 'database\_%' { ESCAPE '\' } OR
33-
name LIKE 'server\_%' { ESCAPE '\' })
34-
AND name LIKE '%\_event%' { ESCAPE '\' }
32+
(name LIKE 'database[_]%' OR
33+
name LIKE 'server[_]%' )
34+
AND name LIKE '%[_]event%'
3535
AND type = 'V'
36+
AND SCHEMA_NAME(schema_id) = 'sys'
3637
ORDER BY name;
3738
```

0 commit comments

Comments
 (0)