Good morning all
I'm creating a table drawn from all the various books online for SQL
Profiler event classes and have discovered seeming duplicates in the SQL 2005
BOL topic "SQL Server Event Class Reference" (which appeared AFTER the
December update):
Broker:Forwarded Message Sent - EventClass 190 (was 139), designated as
Always 190
Progress Report: Online Index Operation - EventClass 190
Broker:Forwarded Message Dropped - EventClass 191 (was 140)
TM:Save Tran Starting - EventClass 191
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
Broker:Queue Disabled - EventClass 143 (REMOVED?)
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
CharlCharl wrote:
> Good morning all
> I'm creating a table drawn from all the various books online for SQL
> Profiler event classes and have discovered seeming duplicates in the
> SQL 2005 BOL topic "SQL Server Event Class Reference" (which appeared
> AFTER the December update):
> Broker:Forwarded Message Sent - EventClass 190 (was 139), designated
> as Always 190
> Progress Report: Online Index Operation - EventClass 190
> Broker:Forwarded Message Dropped - EventClass 191 (was 140)
> TM:Save Tran Starting - EventClass 191
> 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
> Broker:Queue Disabled - EventClass 143 (REMOVED?)
> 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
Query the system view sys.trace_events
--
David Gugick
Quest Software
www.quest.com|||Hi Charl
I addressed this in your other thread, posted 10 minutes earlier than this
one.
Please look at the new metadata view in SQL Server 2005 called
sys.trace_events.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"Charl" <Charl@.discussions.microsoft.com> wrote in message
news:AC94110E-12E3-41C3-AE20-52F4F20AD891@.microsoft.com...
> Good morning all
> I'm creating a table drawn from all the various books online for SQL
> Profiler event classes and have discovered seeming duplicates in the SQL
> 2005
> BOL topic "SQL Server Event Class Reference" (which appeared AFTER the
> December update):
> Broker:Forwarded Message Sent - EventClass 190 (was 139), designated as
> Always 190
> Progress Report: Online Index Operation - EventClass 190
> Broker:Forwarded Message Dropped - EventClass 191 (was 140)
> TM:Save Tran Starting - EventClass 191
> 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
> Broker:Queue Disabled - EventClass 143 (REMOVED?)
> 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
>|||Thanks to Kalen and David for the reply, I have joined the table previously
created from the BOL information to sys.trace_events. Having retained the
original data from BOL before the December update and ignoring the Broker
eventclass changes there is only one missing eventclass - 144 Broker:Mirror
Route.
My point is that the BOL data is somewhat inaccurate in this case especially
given that most DBAs needing to run Profiler will (I hope!) be refering to
BOL...
Thus when you refer to the EventClass information and it lists an eventclass
it is surely fair to expect the data to be valid?
Best regards,
Charl
"Kalen Delaney" wrote:
> Hi Charl
> I addressed this in your other thread, posted 10 minutes earlier than this
> one.
> Please look at the new metadata view in SQL Server 2005 called
> sys.trace_events.
> --
> HTH
> Kalen Delaney, SQL Server MVP
> www.solidqualitylearning.com
>
> "Charl" <Charl@.discussions.microsoft.com> wrote in message
> news:AC94110E-12E3-41C3-AE20-52F4F20AD891@.microsoft.com...
> > Good morning all
> >
> > I'm creating a table drawn from all the various books online for SQL
> > Profiler event classes and have discovered seeming duplicates in the SQL
> > 2005
> > BOL topic "SQL Server Event Class Reference" (which appeared AFTER the
> > December update):
> >
> > Broker:Forwarded Message Sent - EventClass 190 (was 139), designated as
> > Always 190
> >
> > Progress Report: Online Index Operation - EventClass 190
> >
> > Broker:Forwarded Message Dropped - EventClass 191 (was 140)
> >
> > TM:Save Tran Starting - EventClass 191
> >
> > 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
> >
> > Broker:Queue Disabled - EventClass 143 (REMOVED?)
> >
> > 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
> >
> >
>
>|||Charl wrote:
> Thanks to Kalen and David for the reply, I have joined the table
> previously created from the BOL information to sys.trace_events.
> Having retained the original data from BOL before the December update
> and ignoring the Broker eventclass changes there is only one missing
> eventclass - 144 Broker:Mirror Route.
> <SNIP>
You can email feedback directly to Microsoft about the page in question
using the Send Feedback option at the top and then pressing the Send
Feedback button at the bottom.
David Gugick
Quest Software
Showing posts with label profiler. Show all posts
Showing posts with label profiler. Show all posts
Tuesday, March 20, 2012
Thursday, March 8, 2012
Blocking in profiler?
Is tehre a way to profile blocking that occurs on a SQL Server
Th
DedrickThere is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
Th
DedrickThere is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
Blocking in profiler?
Is tehre a way to profile blocking that occurs on a SQL Server?
Thx
Dedrick
There is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
Thx
Dedrick
There is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
Blocking in profiler?
Is tehre a way to profile blocking that occurs on a SQL Server?
Thx
DedrickThere is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
Thx
DedrickThere is a deadlock chain seet of events, but there is not a good and direct
way to watch the aggregate impact of blocking. You can see how long locks
take to acquire with the lock events, but these are typically too voluminous
to run on a productioin server. Alas, there is not data column for any of
the stmt completed events that will let you see the amount of time a
statement waited on locks.
However, dbcc sqlperf(waitstats) is a good source of this info. Combined
with sampling of sysprocesses and profiler data you can usually figure out
which statements are being blocked for significant periods of time
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick|||To add to Brian's response, you can monitor the Profiler Locks: Lock
Acquired event for long durations. Be sure to filter for a value > 0 since
the data can be quite voluminous.
Hope this helps.
Dan Guzman
SQL Server MVP
"Dedrick Winston" <anonymous@.discussions.microsoft.com> wrote in message
news:306B5F74-91F2-496B-81BC-E794F47C3B90@.microsoft.com...
> Is tehre a way to profile blocking that occurs on a SQL Server?
> Thx
> Dedrick
blocking
I am trying to create a SQL Profiler trace.
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
Bill
Looks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
Bill
Looks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
blocking
I am trying to create a SQL Profiler trace.
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
BillLooks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
BillLooks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
Wednesday, March 7, 2012
blocking
I am trying to create a SQL Profiler trace.
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
BillLooks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
I am confused because the Sessions event class only has the Existing
connection event, and no Connect or Disconnect events.
Why is this? Microsoft support articles like #224453 suggest including the
Connect and Disconnect events in a trace, but I can't find them (or some
others).
Thanks
BillLooks like that article is talking about SQL Server 7.0 Profiler. And the
same is not applicable to SQL Server 2000 Profiler. In SQL Server 2000
Profiler, you should be using the 'Audit Login' and 'Audit Logout' evernts
of the 'Security Audit' event class.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>|||What you want is under the Security Audit Event Class. Look for Audit Login
and Audit Logout
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"bille" <belgie@.datamti.com> wrote in message
news:OkCcgHQaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I am trying to create a SQL Profiler trace.
> I am confused because the Sessions event class only has the Existing
> connection event, and no Connect or Disconnect events.
> Why is this? Microsoft support articles like #224453 suggest including
the
> Connect and Disconnect events in a trace, but I can't find them (or some
> others).
> Thanks
> Bill
>
Thursday, February 16, 2012
Blank hostname in profiler, anyone got a workaround?
Doing a profile on a server, I'm getting blank hostnames coming through. I
think we've found that they're coming from some legacy ColdFusion code.
However, when I profile and set a filter of a specific hostname, I still get
line entries that have empty hostnames.
The only item in the MS Support site talks about system processes, which
these are not.
Anyone know of a way to filter out these entries that I do not want to see?Technically, they are NULL, not blank. The Profiler GUI presents them as
blanks. Unfortunately, NULL matches any filter condition, so NULL fields
get through. You can dump the Profiler output to a SQL table and do some
querying on it to improve your filtering capabilities.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Patrick Parker" <pparker@.motivaction.com> wrote in message
news:uGysrkq5DHA.1504@.TK2MSFTNGP12.phx.gbl...
> Doing a profile on a server, I'm getting blank hostnames coming through.
I
> think we've found that they're coming from some legacy ColdFusion code.
> However, when I profile and set a filter of a specific hostname, I still
get
> line entries that have empty hostnames.
> The only item in the MS Support site talks about system processes, which
> these are not.
> Anyone know of a way to filter out these entries that I do not want to
see?
>
>
think we've found that they're coming from some legacy ColdFusion code.
However, when I profile and set a filter of a specific hostname, I still get
line entries that have empty hostnames.
The only item in the MS Support site talks about system processes, which
these are not.
Anyone know of a way to filter out these entries that I do not want to see?Technically, they are NULL, not blank. The Profiler GUI presents them as
blanks. Unfortunately, NULL matches any filter condition, so NULL fields
get through. You can dump the Profiler output to a SQL table and do some
querying on it to improve your filtering capabilities.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Patrick Parker" <pparker@.motivaction.com> wrote in message
news:uGysrkq5DHA.1504@.TK2MSFTNGP12.phx.gbl...
> Doing a profile on a server, I'm getting blank hostnames coming through.
I
> think we've found that they're coming from some legacy ColdFusion code.
> However, when I profile and set a filter of a specific hostname, I still
get
> line entries that have empty hostnames.
> The only item in the MS Support site talks about system processes, which
> these are not.
> Anyone know of a way to filter out these entries that I do not want to
see?
>
>
Blank hostname in profiler, anyone got a workaround?
Doing a profile on a server, I'm getting blank hostnames coming through. I
think we've found that they're coming from some legacy ColdFusion code.
However, when I profile and set a filter of a specific hostname, I still get
line entries that have empty hostnames.
The only item in the MS Support site talks about system processes, which
these are not.
Anyone know of a way to filter out these entries that I do not want to see?Technically, they are NULL, not blank. The Profiler GUI presents them as
blanks. Unfortunately, NULL matches any filter condition, so NULL fields
get through. You can dump the Profiler output to a SQL table and do some
querying on it to improve your filtering capabilities.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Patrick Parker" <pparker@.motivaction.com> wrote in message
news:uGysrkq5DHA.1504@.TK2MSFTNGP12.phx.gbl...
I
get
see?
think we've found that they're coming from some legacy ColdFusion code.
However, when I profile and set a filter of a specific hostname, I still get
line entries that have empty hostnames.
The only item in the MS Support site talks about system processes, which
these are not.
Anyone know of a way to filter out these entries that I do not want to see?Technically, they are NULL, not blank. The Profiler GUI presents them as
blanks. Unfortunately, NULL matches any filter condition, so NULL fields
get through. You can dump the Profiler output to a SQL table and do some
querying on it to improve your filtering capabilities.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Patrick Parker" <pparker@.motivaction.com> wrote in message
news:uGysrkq5DHA.1504@.TK2MSFTNGP12.phx.gbl...
quote:
> Doing a profile on a server, I'm getting blank hostnames coming through.
I
quote:
> think we've found that they're coming from some legacy ColdFusion code.
> However, when I profile and set a filter of a specific hostname, I still
get
quote:
> line entries that have empty hostnames.
> The only item in the MS Support site talks about system processes, which
> these are not.
> Anyone know of a way to filter out these entries that I do not want to
see?
quote:
>
>
Subscribe to:
Posts (Atom)