Comments
1 comment
-
Hi Bill,
Great stuff - Thanks for taking the time to put all that down, I can assure you we'll take it into account.
I just picked up on one thing in particular I'd like to check with you:preachuk wrote:6. One of the Recommendations was 'DB needs Integrity check,' but we are in fact doing a DBCC in SQL 2005 Maintenance plan using the default wizard. it does a 'DBCC CHECKDB with NO_INFOMSGS' so I am guessing this is a false-positive.
We use SQL Server's error log to detect DBCC CHECKDB runs which should still show, for instance if I run the same command on the Adventure Works database then my error log has something like:DBCC CHECKDB (AdventureWorks) WITH no_infomsgs executed by MYDOMAIN\nigel.morse found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 10 seconds.
Now there was an issue here with the original beta (Data base need integrity check) but I think that made the new updated beta build 520 available here so if you're not using that you might like to see if that one works, and if you are already using it then please let me know as we may need to look at it again!
Thanks,
Nigel
Add comment
Please sign in to leave a comment.
I am sending this in lieu of meeting with Claire Brooking.
I'll copy her on it.
Background: I am currently monitoring 9 instances on 5 physical servers. This includes 32 & 64 bit SQL Servers, one SQL cluster, plus one set of DBs running on a SQL Server 2005 box with SQL 6.5 compatibility level. So far, no issues.
My first reaction is that it is very helpful. Being able to see disk space along with backup, maintenance plan status is very useful. I often end up auditing and cleaning up existing (old) servers for customers. bringing them up to speed and ensuring that they have adequate space, recoverability, and are consistent. I can definitely use this tool.
Here are some things I noticed, in no particular order:
1. For 'Long Running Queries' the SQL Fragment window cannot be resized. It seems that other places have code windows that cannot be resized.
2. For multiple Long Running queries on the same server - these all get lumped into a single group. I found 4 specific long running queries that became 8 Incidents (some of them repeated). I wanted to close some of them, but not all of them. Whever I closed one of the 'Long Running Query' events it closed all of them. It'd be nice to close 1 incident instead of the entire Incident group at once.
3. I am unsure what 'Job Overrun' and 'Job Underrun' mean...
4. I am unable to reorder the information for Open|Closed|Recommendations based on the tab headings. For example, for Recommendations I'd like to order it by 'Incident Type' or 'Occurred.'
5. Being an ex-Canadian living in Minnesota, I love the British text. Please keep 'whilst' and 'could do with' in SQL Response when it goes live. ;-)
6. One of the Recommendations was 'DB needs Integrity check,' but we are in fact doing a DBCC in SQL 2005 Maintenance plan using the default wizard. it does a 'DBCC CHECKDB with NO_INFOMSGS' so I am guessing this is a false-positive.
7. The workflow aspect (Open, Closed, Recommendations) is very useful to me. Being able to show what needs to be fixed and what has been fixed is terrific.
8. I am hoping that the cost remains low - like SQL Compare and SQL Backup. It will make it that much more likely that it gets bought & installed on all our client sites.
I hope this helps. If anything else comes up, I'll post it here.
Thanks for involving me in the beta. Let me know if I can be of more assistance,
Bill.