SQL Server performance monitoring and alerting
Moderators: eddie davis, priyasinha, Adam, chriskelly, Chris Lambrou, Chris Spencer
I'm familiar with the purging configuration page ( Configuration/Purging ).
Is there a way to force the monitor to immediately purge to the configured values?
It would also be extremely helpful to have some summary stats for each configurable section. Ex: total row counts and size from sp_spaceused.
On a slight tangent, what is the calculation of CollectionDate bigint columns?
634680627046629255 is an awefully big number. If that is seconds, then it predates the big bang by 7 billion years. Even if it were milliseconds, it goes back to the early Miocene epoch - 20+ million years ago.
- Posts: 28
- Joined: Tue Feb 15, 2005 10:02 pm
- Location: Nashville, TN
The purge is scheduled to run every hour but it won't attempt to purge all the data in one attempt. Restarting the base monitor service should trigger it but it'll still only purge a chunk of the data.
We have an existing enhancement request (ref SRP-4323) to introduce some extra information onto the purge page so that users can make a more informed decision.
The CollectionDate columns use the bigint data type but contain ticks.
To quote MSDN on the subject of ticks:
A single tick represents one hundred nanoseconds or one ten-millionth of a second. There are 10,000 ticks in a millisecond.
The value of this property represents the number of 100-nanosecond intervals that have elapsed since 12:00:00 midnight, January 1, 0001
Therefore 634680627046629255 equates to 2012-03-23 01:25:04.663 (late Holocene?). We have a function called Utils.TicksToDateTime() that can convert the bigint data to datetime. It can be found in the SQL Monitor data repository under Programmability > Functions > Scalar-valued functions.
- Posts: 301
- Joined: Tue Aug 29, 2006 9:09 am
- Location: Red Gate - Cambridge
Return to SQL Monitor 3
Who is online
Users browsing this forum: No registered users and 0 guests