I was prompted to dig into using Extended Events in Azure Data Studio (ADS) after the latest release came out from the Tools Team this past Monday. After you download and install ADS, and connect to an instance, you’ll want to navigate to the Extension Manager (blue box in image), then scroll through the list to find SQL Server Profiler (purple box in image):
Azure Data Studio Extension Manager
NOTE: Even though the extension is named SQL Server Profiler, it is using Extended Events. The documentation states explicitly:
“The SQL Server Profiler extension provides a simple SQL Server tracing solution similar to SSMS Profiler except built using XEvents.”
To clarify, the extension in ADS is like XEvent Profiler in Management Studio (which also is built using Extended Events). The name “SQL Server Profiler” is confusing, as this is not the same tool (UI) that’s been available since SQL Server 7.0.
To install the extension, click on it, and then select Install. Once it’s installed you can select Reload and it will move into the top half of the window under Enabled. Notice that when you select the extension, information about how to use it also appears.
The easiest way to start using Extended Events in ADS is to use Alt+P (for Windows) or Ctrl+Alt+P (for macOS). You can also click on the Manage icon in the bottom left, select Command Palette… and then type Profiler. Using either method, you’ll get a Connection window to connect to the instance:
Once you’ve connected, you’ll be prompted to select what type of session to create, and there are three options currently available:
This is where things get interesting.
There are three template options:
Within XEvent Profiler in SSMS there are only two options:
The events in the Standard_OnPrem and Standard event sessions are the same. The events in the TSQL_OnPrem and TSQL event sessions are the same. The Standard_Azure event session cannot be created for an on-premises installation – it will silently fail.
Once you select the session you want and select Start, a new window opens which is like the Live Data Viewer in SSMS, but with options. As queries are executing, they will start to appear in the window. When you have found the information you need, you can stop the event session using the stop button (red box in image, along with Start and Pause) or you can close the window. If you close the window you will be prompted to stop the event session, which I would recommend doing. You can also change the view using the Select View drop down (blue box in image), which changes which columns appear in the window. Lastly, when you have stopped an event session, you can select a different event session which already exists on the instance from the Select Session drop down (purple box in image) and start it from the window.
A few things worth noting:
- The Event Sessions created in ADS write to the ring_buffer target, the ones created in SSMS do not write to any target.
- If you have an event session running:
- Closing the Profiler window in ADS does prompt you to stop the event session.
- Closing ADS entirely does not prompt you to stop the event session.
- You can create the TSQL and Standard event sessions in SSMS, and you can create the Standard_OnPrem and TSQL_OnPrem event sessions in ADS, and theoretically run all of them at the same time. I wouldn’t recommend this, but if you have multiple users, be aware it’s possible.
- To see what event sessions are running, you can execute:
- To stop an event session using T-SQL, you can execute:
ALTER EVENT SESSION ADS_Standard_OnPremES
STATE = STOP;
- You can still create, alter, and stop event sessions using T-SQL in Azure Data Studio.