February 16, 2016 at 3:14 pm
Hi,
I am interested to know some details about the extended events
We have some extended events running on the server (SQL Server 2008R2).
When I run the query.
select * from sys.dm_xe_packages
I received 4 rows. Looks first 3 is common even though we didn't create extended event.
From select * from sys.dm_xe_sessions I received two records but the create_time for both of them are different.
Questions:
How to we know who created the extended events and when they created on the server
What is the path of the extended events and what it is capturing (Any filters?)
What is the retention period they kept to the data in the extended events
How can we read data from those?
February 16, 2016 at 3:53 pm
Those are probably the built-in sessions. System_health is running on all 2008 and better systems. If you have availability groups on the server, you'll also get a session for those. You can read those sessions, and control them, the same way as you do any session you create. Personally, I'd leave them in place. system_health, for example, captures deadlocks, so you don't need to set traceflags to get that information. It's already being captured.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 16, 2016 at 5:08 pm
How to know the information about the user created one?
February 16, 2016 at 5:14 pm
Same as anything else, use the dynamic management views and system views. They're documented here at MSDN.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply