Comments
Sort by recent activity
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.
Latest version - 1.6.5.639 / comments
Latest version - 1.6.5.639
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
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.
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...
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 ...
I have a support call open now too.
I've 4 Cpu on the server where the web server and base monitor are located and its steady between 30 and 50% usage and there's plenty of free memory (6GB free)
This is also the case with the server where the SQL db is located.
Never had any response issues on any previous versions - this is clearly a UI issue as the app itself is still working behind the scenes and firing out email alerts etc.
Groups are also not working. Even on the config screen it only shows 1 server for each group and you cant expand the group. / comments
I have a support call open now too.
I've 4 Cpu on the server where the web server and base monitor are located and its steady between 30 and 50% usage and there's plenty of free memory (6GB free)
T...
Since upgrading from V4.2.0.243 to V5.0.2 yesterday SQL Monitor has become totally unusable due to the response time. The UI takes a minimum of 10 minutes to respond to anything before I get a refreshed screen.
Despite doubling the cpu in the server with the services on there has been no change in performance.
I'm going to have to take the drastic step of uninstalling and reverting back to V4.2 unless there is a quick fix / comments
Since upgrading from V4.2.0.243 to V5.0.2 yesterday SQL Monitor has become totally unusable due to the response time. The UI takes a minimum of 10 minutes to respond to anything before I get a ref...
Hi Manfred,
i have sysadmin rights on all our SQL servers so permission shouldnt be the problem. / comments
Hi Manfred,
i have sysadmin rights on all our SQL servers so permission shouldnt be the problem.