SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Database activity


Database activity

Author
Message
jralston88
jralston88
SSC-Addicted
SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)SSC-Addicted (449 reputation)

Group: General Forum Members
Points: 449 Visits: 689
Hello,
We have a SQL Server 2005 Enterprise Edition - 64 bit instance with 12 user databases. The activity monitor database drop down shows only 1 user database - thats not accurate. Of the other databases, one is offline. How do you go about determining the level of activity for the others. Would profiler be the next step?

Any comments / URLs would be appreciated - thanks.
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)

Group: General Forum Members
Points: 100925 Visits: 33014
I'd suggest not relying too much on those screens. Instead, if you're interested in monitoring the system, use a combination of Performance Monitor, Dynamic Management Objects and Extended Events. You'll get a much better and more accurate view of what is up with your systems.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
kevaburg
kevaburg
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4613 Visits: 1025
For this sort of thing I would recommend a server-side profiler trace. Don't use the Profiler itself if you intend to trace over an extended period.
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)

Group: General Forum Members
Points: 100925 Visits: 33014
kevaburg (12/6/2013)
For this sort of thing I would recommend a server-side profiler trace. Don't use the Profiler itself if you intend to trace over an extended period.


If you're on 2008 or better, I strongly recommend not using trace. Extended events are much less intrusive, filter better, collect better information more easily. The only problem with them is that they're just a little more difficult to consume since in 2008 & 2008R2 there is no GUI available.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
kevaburg
kevaburg
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4613 Visits: 1025
Grant Fritchey (12/6/2013)
kevaburg (12/6/2013)
For this sort of thing I would recommend a server-side profiler trace. Don't use the Profiler itself if you intend to trace over an extended period.


If you're on 2008 or better, I strongly recommend not using trace. Extended events are much less intrusive, filter better, collect better information more easily. The only problem with them is that they're just a little more difficult to consume since in 2008 & 2008R2 there is no GUI available.


why the recommendation not to use them? Performance implications or because extended events are simply better?
Grant Fritchey
Grant Fritchey
SSC Guru
SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)SSC Guru (100K reputation)

Group: General Forum Members
Points: 100925 Visits: 33014
kevaburg (12/6/2013)
Grant Fritchey (12/6/2013)
kevaburg (12/6/2013)
For this sort of thing I would recommend a server-side profiler trace. Don't use the Profiler itself if you intend to trace over an extended period.


If you're on 2008 or better, I strongly recommend not using trace. Extended events are much less intrusive, filter better, collect better information more easily. The only problem with them is that they're just a little more difficult to consume since in 2008 & 2008R2 there is no GUI available.


why the recommendation not to use them? Performance implications or because extended events are simply better?


Both.

I have tons of evidence, but I'll give you just one.

When you filter a trace event, the event fires, the data is collected, it goes into the buffer, then a determination is made if that event meets the filter criteria. In short, it filters after collecting the data. With an extended event, the event fires, the filter checks to see if the criteria is met, if so, it collects the data, if not, the data is never collected. Just that one thing alone makes a huge difference in how those two different mechanisms interact with the system and there are lots more.

----------------------------------------------------
The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
Theodore Roosevelt

The Scary DBA
Author of: SQL Server Query Performance Tuning and SQL Server Execution Plans
Product Evangelist for Red Gate Software
kevaburg
kevaburg
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4613 Visits: 1025
Grant Fritchey (12/6/2013)
kevaburg (12/6/2013)
Grant Fritchey (12/6/2013)
kevaburg (12/6/2013)
For this sort of thing I would recommend a server-side profiler trace. Don't use the Profiler itself if you intend to trace over an extended period.


If you're on 2008 or better, I strongly recommend not using trace. Extended events are much less intrusive, filter better, collect better information more easily. The only problem with them is that they're just a little more difficult to consume since in 2008 & 2008R2 there is no GUI available.


why the recommendation not to use them? Performance implications or because extended events are simply better?


Both.

I have tons of evidence, but I'll give you just one.

When you filter a trace event, the event fires, the data is collected, it goes into the buffer, then a determination is made if that event meets the filter criteria. In short, it filters after collecting the data. With an extended event, the event fires, the filter checks to see if the criteria is met, if so, it collects the data, if not, the data is never collected. Just that one thing alone makes a huge difference in how those two different mechanisms interact with the system and there are lots more.


Thank you! It makes sense if you think about it.....;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search