Eventclasses from Profiler

Hi
Where do I find the EventClasses that are shown when I run a trace?
Resson for asking is that I have setup a trace that dumps the data to a
table, and in here the EventClass is just shown as a number. I then need
to know which event class this number represents.
Regards
SteenLook in SQL Server Books Online under sp_trace_setevent.
HTH
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:ezuNNbA0FHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi
> Where do I find the EventClasses that are shown when I run a trace?
> Resson for asking is that I have setup a trace that dumps the data to a
> table, and in here the EventClass is just shown as a number. I then need
> to know which event class this number represents.
> Regards
> Steen|||http://sqldev.net/misc/fn_trace.htm
:-)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:ezuNNbA0FHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi
> Where do I find the EventClasses that are shown when I run a trace?
> Resson for asking is that I have setup a trace that dumps the data to a table, and in here the
> EventClass is just shown as a number. I then need to know which event class this number
> represents.
> Regards
> Steen|||Hi Steen
If you want to lookup the event names for a few rows, the function that
Tibor will point you to will work great. You may find that if you want to
translate eventClass values for a large table, it is more efficient to join
to a lookup table. I find it easiest to create a table that maps event
number to name, and
join this table with the trace table.
Here is code to do that. By giving the table a name that starts with sp_,
you can access the table from any database without needing to fully qualify
it,
even though you create it in master.
USE master
GO
CREATE TABLE sp_EventID_Table (ID int, Description varchar(50) )
GO
SET NOCOUNT ON
GO
INSERT INTO sp_EventID_Table VALUES (0, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (1, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (2, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (3, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (4, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (5, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (6, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (7, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (8, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (9, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (10, 'RPC:Completed')
INSERT INTO sp_EventID_Table VALUES (11, 'RPC:Starting')
INSERT INTO sp_EventID_Table VALUES (12, 'SQL:BatchCompleted')
INSERT INTO sp_EventID_Table VALUES (13, 'SQL:BatchStarting')
INSERT INTO sp_EventID_Table VALUES (14, 'Login')
INSERT INTO sp_EventID_Table VALUES (15, 'Logout')
INSERT INTO sp_EventID_Table VALUES (16, 'Attention')
INSERT INTO sp_EventID_Table VALUES (17, 'ExistingConnection')
INSERT INTO sp_EventID_Table VALUES (18, 'ServiceControl')
INSERT INTO sp_EventID_Table VALUES (19, 'DTCTransaction')
INSERT INTO sp_EventID_Table VALUES (20, 'Login Failed')
INSERT INTO sp_EventID_Table VALUES (21, 'EventLog')
INSERT INTO sp_EventID_Table VALUES (22, 'ErrorLog')
INSERT INTO sp_EventID_Table VALUES (23, 'Lock:Released')
INSERT INTO sp_EventID_Table VALUES (24, 'Lock:Acquired')
INSERT INTO sp_EventID_Table VALUES (25, 'Lock:Deadlock')
INSERT INTO sp_EventID_Table VALUES (26, 'Lock:Cancel')
INSERT INTO sp_EventID_Table VALUES (27, 'Lock:Timeout')
INSERT INTO sp_EventID_Table VALUES (28, 'DOP Event')
INSERT INTO sp_EventID_Table VALUES (29, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (30, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (31, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (32, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (33, 'Exception')
INSERT INTO sp_EventID_Table VALUES (34, 'SP:CacheMiss')
INSERT INTO sp_EventID_Table VALUES (35, 'SP:CacheInsert')
INSERT INTO sp_EventID_Table VALUES (36, 'SP:CacheRemove')
INSERT INTO sp_EventID_Table VALUES (37, 'SP:Recompile')
INSERT INTO sp_EventID_Table VALUES (38, 'SP:CacheHit')
INSERT INTO sp_EventID_Table VALUES (39, 'SP:ExecContextHit')
INSERT INTO sp_EventID_Table VALUES (40, 'SQL:StmtStarting')
INSERT INTO sp_EventID_Table VALUES (41, 'SQL:StmtCompleted')
INSERT INTO sp_EventID_Table VALUES (42, 'SP:Starting')
INSERT INTO sp_EventID_Table VALUES (43, 'SP:Completed')
INSERT INTO sp_EventID_Table VALUES (44, 'SP:StmtStarting')
INSERT INTO sp_EventID_Table VALUES (45, 'SP:StmtCompleted')
INSERT INTO sp_EventID_Table VALUES (46, 'Object:Created')
INSERT INTO sp_EventID_Table VALUES (47, 'Object:Deleted')
INSERT INTO sp_EventID_Table VALUES (48, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (49, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (50, 'SQL Transaction')
INSERT INTO sp_EventID_Table VALUES (51, 'Scan:Started')
INSERT INTO sp_EventID_Table VALUES (52, 'Scan:Stopped')
INSERT INTO sp_EventID_Table VALUES (53, 'CursorOpen')
INSERT INTO sp_EventID_Table VALUES (54, 'Transaction Log')
INSERT INTO sp_EventID_Table VALUES (55, 'Hash Warning')
INSERT INTO sp_EventID_Table VALUES (56, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (57, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (58, 'Auto Update Stats')
INSERT INTO sp_EventID_Table VALUES (59, 'Lock:Deadlock Chain')
INSERT INTO sp_EventID_Table VALUES (60, 'Lock:Escalation')
INSERT INTO sp_EventID_Table VALUES (61, 'OLE DB Errors')
INSERT INTO sp_EventID_Table VALUES (62, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (63, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (64, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (65, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (66, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (67, 'Execution Warnings')
INSERT INTO sp_EventID_Table VALUES (68, 'Execution Plan')
INSERT INTO sp_EventID_Table VALUES (69, 'Sort Warnings')
INSERT INTO sp_EventID_Table VALUES (70, 'CursorPrepare')
INSERT INTO sp_EventID_Table VALUES (71, 'Prepare SQL')
INSERT INTO sp_EventID_Table VALUES (72, 'Exec Prepared SQL')
INSERT INTO sp_EventID_Table VALUES (73, 'Unprepare SQL')
INSERT INTO sp_EventID_Table VALUES (74, 'CursorExecute')
INSERT INTO sp_EventID_Table VALUES (75, 'CursorRecompile')
INSERT INTO sp_EventID_Table VALUES (76, 'CursorImplicitConversion')
INSERT INTO sp_EventID_Table VALUES (77, 'CursorUnprepare')
INSERT INTO sp_EventID_Table VALUES (78, 'CursorClose')
INSERT INTO sp_EventID_Table VALUES (79, 'Missing Column Statistics')
INSERT INTO sp_EventID_Table VALUES (80, 'Missing Join Predicate')
INSERT INTO sp_EventID_Table VALUES (81, 'Server Memory Change')
INSERT INTO sp_EventID_Table VALUES (82, 'User Configurable 0')
INSERT INTO sp_EventID_Table VALUES (83, 'User Configurable 1')
INSERT INTO sp_EventID_Table VALUES (84, 'User Configurable 2')
INSERT INTO sp_EventID_Table VALUES (85, 'User Configurable 3')
INSERT INTO sp_EventID_Table VALUES (86, 'User Configurable 4')
INSERT INTO sp_EventID_Table VALUES (87, 'User Configurable 5')
INSERT INTO sp_EventID_Table VALUES (88, 'User Configurable 6')
INSERT INTO sp_EventID_Table VALUES (89, 'User Configurable 7')
INSERT INTO sp_EventID_Table VALUES (90, 'User Configurable 8')
INSERT INTO sp_EventID_Table VALUES (91, 'User Configurable 9')
INSERT INTO sp_EventID_Table VALUES (92, 'Data File Auto Grow')
INSERT INTO sp_EventID_Table VALUES (93, 'Log File Auto Grow')
INSERT INTO sp_EventID_Table VALUES (94, 'Data File Auto Shrink')
INSERT INTO sp_EventID_Table VALUES (95, 'Log File Auto Shrink')
INSERT INTO sp_EventID_Table VALUES (96, 'Show Plan Text')
INSERT INTO sp_EventID_Table VALUES (97, 'Show Plan ALL')
INSERT INTO sp_EventID_Table VALUES (98, 'Show Plan Statistics')
INSERT INTO sp_EventID_Table VALUES (99, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (100, 'RPC Output Parameter')
INSERT INTO sp_EventID_Table VALUES (101, 'Reserved')
INSERT INTO sp_EventID_Table VALUES (102, 'Audit Statement GDR')
INSERT INTO sp_EventID_Table VALUES (103, 'Audit Object GDR')
INSERT INTO sp_EventID_Table VALUES (104, 'Audit Add/Drop Login')
INSERT INTO sp_EventID_Table VALUES (105, 'Audit Login GDR')
INSERT INTO sp_EventID_Table VALUES (106, 'Audit Login Change Property')
INSERT INTO sp_EventID_Table VALUES (107, 'Audit Login Change Password')
INSERT INTO sp_EventID_Table VALUES (108, 'Audit Add Login to Server Role')
INSERT INTO sp_EventID_Table VALUES (109, 'Audit Add DB User')
INSERT INTO sp_EventID_Table VALUES (110, 'Audit Add Member to DB')
INSERT INTO sp_EventID_Table VALUES (111, 'Audit Add/Drop Role')
INSERT INTO sp_EventID_Table VALUES (112, 'App Role Pass Change')
INSERT INTO sp_EventID_Table VALUES (113, 'Audit Statement Permission')
INSERT INTO sp_EventID_Table VALUES (114, 'Audit Object Permission')
INSERT INTO sp_EventID_Table VALUES (115, 'Audit Backup/Restore')
INSERT INTO sp_EventID_Table VALUES (116, 'Audit DBCC')
INSERT INTO sp_EventID_Table VALUES (117, 'Audit Change Audit')
INSERT INTO sp_EventID_Table VALUES (118, 'Audit Object Derived
Permission')
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message
news:ezuNNbA0FHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi
> Where do I find the EventClasses that are shown when I run a trace?
> Resson for asking is that I have setup a trace that dumps the data to a
> table, and in here the EventClass is just shown as a number. I then need
> to know which event class this number represents.
> Regards
> Steen
>|||Kalen Delaney wrote:
> Hi Steen
> If you want to lookup the event names for a few rows, the function that
> Tibor will point you to will work great. You may find that if you want to
> translate eventClass values for a large table, it is more efficient to join
> to a lookup table. I find it easiest to create a table that maps event
> number to name, and
> join this table with the trace table.
> Here is code to do that. By giving the table a name that starts with sp_,
> you can access the table from any database without needing to fully qualify
> it,
> even though you create it in master.
>
> USE master
> GO
> CREATE TABLE sp_EventID_Table (ID int, Description varchar(50) )
> GO
> SET NOCOUNT ON
> GO
> INSERT INTO sp_EventID_Table VALUES (0, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (1, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (2, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (3, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (4, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (5, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (6, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (7, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (8, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (9, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (10, 'RPC:Completed')
> INSERT INTO sp_EventID_Table VALUES (11, 'RPC:Starting')
> INSERT INTO sp_EventID_Table VALUES (12, 'SQL:BatchCompleted')
> INSERT INTO sp_EventID_Table VALUES (13, 'SQL:BatchStarting')
> INSERT INTO sp_EventID_Table VALUES (14, 'Login')
> INSERT INTO sp_EventID_Table VALUES (15, 'Logout')
> INSERT INTO sp_EventID_Table VALUES (16, 'Attention')
> INSERT INTO sp_EventID_Table VALUES (17, 'ExistingConnection')
> INSERT INTO sp_EventID_Table VALUES (18, 'ServiceControl')
> INSERT INTO sp_EventID_Table VALUES (19, 'DTCTransaction')
> INSERT INTO sp_EventID_Table VALUES (20, 'Login Failed')
> INSERT INTO sp_EventID_Table VALUES (21, 'EventLog')
> INSERT INTO sp_EventID_Table VALUES (22, 'ErrorLog')
> INSERT INTO sp_EventID_Table VALUES (23, 'Lock:Released')
> INSERT INTO sp_EventID_Table VALUES (24, 'Lock:Acquired')
> INSERT INTO sp_EventID_Table VALUES (25, 'Lock:Deadlock')
> INSERT INTO sp_EventID_Table VALUES (26, 'Lock:Cancel')
> INSERT INTO sp_EventID_Table VALUES (27, 'Lock:Timeout')
> INSERT INTO sp_EventID_Table VALUES (28, 'DOP Event')
> INSERT INTO sp_EventID_Table VALUES (29, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (30, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (31, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (32, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (33, 'Exception')
> INSERT INTO sp_EventID_Table VALUES (34, 'SP:CacheMiss')
> INSERT INTO sp_EventID_Table VALUES (35, 'SP:CacheInsert')
> INSERT INTO sp_EventID_Table VALUES (36, 'SP:CacheRemove')
> INSERT INTO sp_EventID_Table VALUES (37, 'SP:Recompile')
> INSERT INTO sp_EventID_Table VALUES (38, 'SP:CacheHit')
> INSERT INTO sp_EventID_Table VALUES (39, 'SP:ExecContextHit')
> INSERT INTO sp_EventID_Table VALUES (40, 'SQL:StmtStarting')
> INSERT INTO sp_EventID_Table VALUES (41, 'SQL:StmtCompleted')
> INSERT INTO sp_EventID_Table VALUES (42, 'SP:Starting')
> INSERT INTO sp_EventID_Table VALUES (43, 'SP:Completed')
> INSERT INTO sp_EventID_Table VALUES (44, 'SP:StmtStarting')
> INSERT INTO sp_EventID_Table VALUES (45, 'SP:StmtCompleted')
> INSERT INTO sp_EventID_Table VALUES (46, 'Object:Created')
> INSERT INTO sp_EventID_Table VALUES (47, 'Object:Deleted')
> INSERT INTO sp_EventID_Table VALUES (48, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (49, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (50, 'SQL Transaction')
> INSERT INTO sp_EventID_Table VALUES (51, 'Scan:Started')
> INSERT INTO sp_EventID_Table VALUES (52, 'Scan:Stopped')
> INSERT INTO sp_EventID_Table VALUES (53, 'CursorOpen')
> INSERT INTO sp_EventID_Table VALUES (54, 'Transaction Log')
> INSERT INTO sp_EventID_Table VALUES (55, 'Hash Warning')
> INSERT INTO sp_EventID_Table VALUES (56, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (57, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (58, 'Auto Update Stats')
> INSERT INTO sp_EventID_Table VALUES (59, 'Lock:Deadlock Chain')
> INSERT INTO sp_EventID_Table VALUES (60, 'Lock:Escalation')
> INSERT INTO sp_EventID_Table VALUES (61, 'OLE DB Errors')
> INSERT INTO sp_EventID_Table VALUES (62, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (63, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (64, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (65, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (66, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (67, 'Execution Warnings')
> INSERT INTO sp_EventID_Table VALUES (68, 'Execution Plan')
> INSERT INTO sp_EventID_Table VALUES (69, 'Sort Warnings')
> INSERT INTO sp_EventID_Table VALUES (70, 'CursorPrepare')
> INSERT INTO sp_EventID_Table VALUES (71, 'Prepare SQL')
> INSERT INTO sp_EventID_Table VALUES (72, 'Exec Prepared SQL')
> INSERT INTO sp_EventID_Table VALUES (73, 'Unprepare SQL')
> INSERT INTO sp_EventID_Table VALUES (74, 'CursorExecute')
> INSERT INTO sp_EventID_Table VALUES (75, 'CursorRecompile')
> INSERT INTO sp_EventID_Table VALUES (76, 'CursorImplicitConversion')
> INSERT INTO sp_EventID_Table VALUES (77, 'CursorUnprepare')
> INSERT INTO sp_EventID_Table VALUES (78, 'CursorClose')
> INSERT INTO sp_EventID_Table VALUES (79, 'Missing Column Statistics')
> INSERT INTO sp_EventID_Table VALUES (80, 'Missing Join Predicate')
> INSERT INTO sp_EventID_Table VALUES (81, 'Server Memory Change')
> INSERT INTO sp_EventID_Table VALUES (82, 'User Configurable 0')
> INSERT INTO sp_EventID_Table VALUES (83, 'User Configurable 1')
> INSERT INTO sp_EventID_Table VALUES (84, 'User Configurable 2')
> INSERT INTO sp_EventID_Table VALUES (85, 'User Configurable 3')
> INSERT INTO sp_EventID_Table VALUES (86, 'User Configurable 4')
> INSERT INTO sp_EventID_Table VALUES (87, 'User Configurable 5')
> INSERT INTO sp_EventID_Table VALUES (88, 'User Configurable 6')
> INSERT INTO sp_EventID_Table VALUES (89, 'User Configurable 7')
> INSERT INTO sp_EventID_Table VALUES (90, 'User Configurable 8')
> INSERT INTO sp_EventID_Table VALUES (91, 'User Configurable 9')
> INSERT INTO sp_EventID_Table VALUES (92, 'Data File Auto Grow')
> INSERT INTO sp_EventID_Table VALUES (93, 'Log File Auto Grow')
> INSERT INTO sp_EventID_Table VALUES (94, 'Data File Auto Shrink')
> INSERT INTO sp_EventID_Table VALUES (95, 'Log File Auto Shrink')
> INSERT INTO sp_EventID_Table VALUES (96, 'Show Plan Text')
> INSERT INTO sp_EventID_Table VALUES (97, 'Show Plan ALL')
> INSERT INTO sp_EventID_Table VALUES (98, 'Show Plan Statistics')
> INSERT INTO sp_EventID_Table VALUES (99, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (100, 'RPC Output Parameter')
> INSERT INTO sp_EventID_Table VALUES (101, 'Reserved')
> INSERT INTO sp_EventID_Table VALUES (102, 'Audit Statement GDR')
> INSERT INTO sp_EventID_Table VALUES (103, 'Audit Object GDR')
> INSERT INTO sp_EventID_Table VALUES (104, 'Audit Add/Drop Login')
> INSERT INTO sp_EventID_Table VALUES (105, 'Audit Login GDR')
> INSERT INTO sp_EventID_Table VALUES (106, 'Audit Login Change Property')
> INSERT INTO sp_EventID_Table VALUES (107, 'Audit Login Change Password')
> INSERT INTO sp_EventID_Table VALUES (108, 'Audit Add Login to Server Role')
> INSERT INTO sp_EventID_Table VALUES (109, 'Audit Add DB User')
> INSERT INTO sp_EventID_Table VALUES (110, 'Audit Add Member to DB')
> INSERT INTO sp_EventID_Table VALUES (111, 'Audit Add/Drop Role')
> INSERT INTO sp_EventID_Table VALUES (112, 'App Role Pass Change')
> INSERT INTO sp_EventID_Table VALUES (113, 'Audit Statement Permission')
> INSERT INTO sp_EventID_Table VALUES (114, 'Audit Object Permission')
> INSERT INTO sp_EventID_Table VALUES (115, 'Audit Backup/Restore')
> INSERT INTO sp_EventID_Table VALUES (116, 'Audit DBCC')
> INSERT INTO sp_EventID_Table VALUES (117, 'Audit Change Audit')
> INSERT INTO sp_EventID_Table VALUES (118, 'Audit Object Derived
> Permission')
>
>
Hi Kalen
Thanks a lot for the script. It do makes things a bit easier than have
to look up every single evensclass manually...:-).
Regards
Steen|||Hi Steve
I have actually created a table with all the eventclasses, subclasses, modes
etc however I've run into probs with the event categories being duplicated
for 2005:
Broker:Forwarded Message Sent - EventClass 190, designated as Always 190
Progress Report: Online Index Operation - EventClass 190
Data File Auto Grow event class - EventClass 92
Log File Auto Grow event class - EventClass 92
Data File Auto Shrink event class - EventClass 95
Log File Auto Shrink event class - EventClass 95
If I can resolve this then I'll be posting the table schema & data.
Anyone else discovered this or is this by 'design', and of course has anyone
from MS got an idea on the 'right' event numbers?
Cheers
Charl
Small sample:
Eventclass_nr, SQLVer_nr, Eventname, eventcategory, description
142 90 Broker:Transmission Broker
indicates that error..
This is then joined to the trace table (remembering to add the SQLVer
number!) via the eventclass_nr
"Steen Persson (DK)" wrote:
> Hi
> Where do I find the EventClasses that are shown when I run a trace?
> Resson for asking is that I have setup a trace that dumps the data to a
> table, and in here the EventClass is just shown as a number. I then need
> to know which event class this number represents.
> Regards
> Steen
>|||Hi Charl
Where are you getting these numbers from?
For SQL Server 2005, there is already a table that has this info.
If you select from sys.trace_events you'll see that Data File Auto Grow is
92 and Log File Auto Grow is 93.
The auto shrink events are 94 and 95.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Charl" <Charl@.discussions.microsoft.com> wrote in message
news:30616526-3B2F-4B04-AF51-5E2C529895BB@.microsoft.com...
> Hi Steve
> I have actually created a table with all the eventclasses, subclasses,
> modes
> etc however I've run into probs with the event categories being duplicated
> for 2005:
> Broker:Forwarded Message Sent - EventClass 190, designated as Always 190
> Progress Report: Online Index Operation - EventClass 190
> Data File Auto Grow event class - EventClass 92
> Log File Auto Grow event class - EventClass 92
> Data File Auto Shrink event class - EventClass 95
> Log File Auto Shrink event class - EventClass 95
> If I can resolve this then I'll be posting the table schema & data.
> Anyone else discovered this or is this by 'design', and of course has
> anyone
> from MS got an idea on the 'right' event numbers?
> Cheers
> Charl
> Small sample:
> Eventclass_nr, SQLVer_nr, Eventname, eventcategory,
> description
> 142 90 Broker:Transmission Broker
> indicates that error..
> This is then joined to the trace table (remembering to add the SQLVer
> number!) via the eventclass_nr
> "Steen Persson (DK)" wrote:
>> Hi
>> Where do I find the EventClasses that are shown when I run a trace?
>> Resson for asking is that I have setup a trace that dumps the data to a
>> table, and in here the EventClass is just shown as a number. I then need
>> to know which event class this number represents.
>> Regards
>> Steen
>|||Hi Kalen
These numbers have been drawn from the BOL information for Event monitoring
which is why I'm questioning the results. While I had overlooked the
sys.trace_events, surely we can expect the data shown there to match the BOL
entries and / or contain more info than BOL?
The reason for this question arose because I have created a table to contain
all the eventclasses from the previous SQL versions and of course naturally
extended this to SQL 2005 - forgot we had some new views! Other than the
duplicate effort it did promptly show the discrepancies in BOL detailed below.
All the best,
Charl
"Kalen Delaney" wrote:
> Hi Charl
> Where are you getting these numbers from?
> For SQL Server 2005, there is already a table that has this info.
> If you select from sys.trace_events you'll see that Data File Auto Grow is
> 92 and Log File Auto Grow is 93.
> The auto shrink events are 94 and 95.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Charl" <Charl@.discussions.microsoft.com> wrote in message
> news:30616526-3B2F-4B04-AF51-5E2C529895BB@.microsoft.com...
> > Hi Steve
> > I have actually created a table with all the eventclasses, subclasses,
> > modes
> > etc however I've run into probs with the event categories being duplicated
> > for 2005:
> >
> > Broker:Forwarded Message Sent - EventClass 190, designated as Always 190
> >
> > Progress Report: Online Index Operation - EventClass 190
> >
> > Data File Auto Grow event class - EventClass 92
> >
> > Log File Auto Grow event class - EventClass 92
> >
> > Data File Auto Shrink event class - EventClass 95
> >
> > Log File Auto Shrink event class - EventClass 95
> >
> > If I can resolve this then I'll be posting the table schema & data.
> >
> > Anyone else discovered this or is this by 'design', and of course has
> > anyone
> > from MS got an idea on the 'right' event numbers?
> >
> > Cheers
> >
> > Charl
> >
> > Small sample:
> >
> > Eventclass_nr, SQLVer_nr, Eventname, eventcategory,
> > description
> > 142 90 Broker:Transmission Broker
> > indicates that error..
> >
> > This is then joined to the trace table (remembering to add the SQLVer
> > number!) via the eventclass_nr
> >
> > "Steen Persson (DK)" wrote:
> >
> >> Hi
> >>
> >> Where do I find the EventClasses that are shown when I run a trace?
> >>
> >> Resson for asking is that I have setup a trace that dumps the data to a
> >> table, and in here the EventClass is just shown as a number. I then need
> >> to know which event class this number represents.
> >>
> >> Regards
> >> Steen
> >>
> >
>
>|||Hi Charl
>> surely we can expect the data shown there to match the BOL
entries and / or contain more info than BOL <<
I don't expect that at all. BOL is a nice place to start, but there are
many times its information is incomplete or wrong. You can supply feedback
to the BOL writers.
Truth be told, I did the same thing you did. I have a table for SQL 2000
listing all the event classes, and I have posted that table here on the
forums several times. I spent a bit of time expanding that table for SQL
2005, and also created one that had all the data column definitions also,
and wrote about them for a SQL Server Magazine article. After the article
had already been submitted, Itzik Ben-Gan told me about the sys.trace_events
view and the one for the data columns (I don't have SQL 2005 running right
now) and I had to quickly rewrite parts of the article. :-)
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Charl" <Charl@.discussions.microsoft.com> wrote in message
news:FDBCCB12-19A7-4D1F-AA1D-B07B8A83522C@.microsoft.com...
> Hi Kalen
> These numbers have been drawn from the BOL information for Event
> monitoring
> which is why I'm questioning the results. While I had overlooked the
> sys.trace_events, surely we can expect the data shown there to match the
> BOL
> entries and / or contain more info than BOL?
> The reason for this question arose because I have created a table to
> contain
> all the eventclasses from the previous SQL versions and of course
> naturally
> extended this to SQL 2005 - forgot we had some new views! Other than the
> duplicate effort it did promptly show the discrepancies in BOL detailed
> below.
> All the best,
> Charl
> "Kalen Delaney" wrote:
>> Hi Charl
>> Where are you getting these numbers from?
>> For SQL Server 2005, there is already a table that has this info.
>> If you select from sys.trace_events you'll see that Data File Auto Grow
>> is
>> 92 and Log File Auto Grow is 93.
>> The auto shrink events are 94 and 95.
>> --
>> HTH
>> Kalen Delaney, SQL Server MVP
>> www.solidqualitylearning.com
>>
>> "Charl" <Charl@.discussions.microsoft.com> wrote in message
>> news:30616526-3B2F-4B04-AF51-5E2C529895BB@.microsoft.com...
>> > Hi Steve
>> > I have actually created a table with all the eventclasses, subclasses,
>> > modes
>> > etc however I've run into probs with the event categories being
>> > duplicated
>> > for 2005:
>> >
>> > Broker:Forwarded Message Sent - EventClass 190, designated as Always
>> > 190
>> >
>> > Progress Report: Online Index Operation - EventClass 190
>> >
>> > Data File Auto Grow event class - EventClass 92
>> >
>> > Log File Auto Grow event class - EventClass 92
>> >
>> > Data File Auto Shrink event class - EventClass 95
>> >
>> > Log File Auto Shrink event class - EventClass 95
>> >
>> > If I can resolve this then I'll be posting the table schema & data.
>> >
>> > Anyone else discovered this or is this by 'design', and of course has
>> > anyone
>> > from MS got an idea on the 'right' event numbers?
>> >
>> > Cheers
>> >
>> > Charl
>> >
>> > Small sample:
>> >
>> > Eventclass_nr, SQLVer_nr, Eventname, eventcategory,
>> > description
>> > 142 90 Broker:Transmission Broker
>> > indicates that error..
>> >
>> > This is then joined to the trace table (remembering to add the SQLVer
>> > number!) via the eventclass_nr
>> >
>> > "Steen Persson (DK)" wrote:
>> >
>> >> Hi
>> >>
>> >> Where do I find the EventClasses that are shown when I run a trace?
>> >>
>> >> Resson for asking is that I have setup a trace that dumps the data to
>> >> a
>> >> table, and in here the EventClass is just shown as a number. I then
>> >> need
>> >> to know which event class this number represents.
>> >>
>> >> Regards
>> >> Steen
>> >>
>> >
>>
>>
>