Activity overview
Latest activity by VoiceOfRock
I put SQL monitor back on the test server with this OS/SQL combo and within a few hours cpu hit 100% so proved this is the issue. / comments
I put SQL monitor back on the test server with this OS/SQL combo and within a few hours cpu hit 100% so proved this is the issue.
Upgrade to 7.0.11.7623 caused 100% cpu on several SQL 2008 servers
Upgraded from 7.0.3 to 7.0.11.7623 on Friday morning last week. Within an hour I had a prod server hit and stay at 100% cpu and be totally unresponsive. At the time I didn't put this down to SQL M...
Hi Anu,
I have emailed with attachments for config and log files / comments
Hi Anu,
I have emailed with attachments for config and log files
Latest version - 1.6.5.639 / comments
Latest version - 1.6.5.639
Service wont start if UserSettings.config exists
I created a new UserSettings.config file as per the documentation and the DLM Dashboard Monitoring Service then refused to restart.
when I removed the config file it restarted instantly. put it bac...
Hi Alex,
Hopefully you've received a few direct emails with screenshots.
3 servers on 2008 Std Edition and one on 2008R2 Std are affected.
all are Simple and have Full backups each night. / comments
Hi Alex,
Hopefully you've received a few direct emails with screenshots.
3 servers on 2008 Std Edition and one on 2008R2 Std are affected.
all are Simple and have Full backups each night.
Bugs in 5.0.3
in read only login mode the Alerts screen doesn't display correctly with the data details in the wrong columns. Each column has data meant for the column to the right of it!
Databases in Simple re...
We are monitoring 17 instances and have been for at least 12 months, yet our Monitor db has grown much faster and larger than expected despite our purging settings.
if you are still struggling with response times but don't want to rollback to V4 it might be worth starting with a new db like I have done but you'll have to go through changing all your settings again though which may take a while.
Not having the groups working at all is still a major pain too. / comments
We are monitoring 17 instances and have been for at least 12 months, yet our Monitor db has grown much faster and larger than expected despite our purging settings.
if you are still struggling with...
I took a decision to delete my existing Monitor db (135GB) and create a brand new one rather than revert to the old v4.
The response times now are a few seconds rather than several minutes.
My new db has 3GB of data in after just a couple of days so obviously the UI has hardly anything to process.
I'd be interested to know the Monitor db sizes of other slow response sufferers.
Incidentally, my old db had its purging levels at 1 month on most settings and 1 week on a couple of the high volume data. / comments
I took a decision to delete my existing Monitor db (135GB) and create a brand new one rather than revert to the old v4.
The response times now are a few seconds rather than several minutes.
My new ...
Yes, its not just you, this is another thing not working in this version! :roll:
It's not possible to view them all in the config screen either.
really poor release that hasn't been tested properly. :x / comments
Yes, its not just you, this is another thing not working in this version! :roll:
It's not possible to view them all in the config screen either.
really poor release that hasn't been tested properly...