July 19, 2004 at 1:12 pm
I have a database that I am monitoring, using Profiler, to see what errors and warnings are found. So far, I am finding that, on average, there are about 70 errors and warnings captured for this database every hour. I realize that I need to check out exactly what the statements are that are causing the errors but I am wondering...
Is there a "normal" amount of errors and warnings that I should expect to capture? I mean, am I chasing after something that I should not worry about?
For instance, this database does a lot. Out of over a million transactions every hour, I am finding 70 errors or warnings. Is this an acceptable level? I actually think that we should try to troubleshoot all the warnings so that there are 0 errors and warnings. Some of these warnings are because statistices need to be updated. So, there is some maintenance that needs to be performed on the database. Others are hash, sort warnings, and missing predicates. Since I do not have exclusive control over the statements that are passed into the database, there is always going to be room for erroneous statments to be made.
But, is there an acceptable level of number or warnings and errors? I personally don't think there should be any but am open to other opinions.
Thanks!
--Lori
July 21, 2004 at 1:26 pm
IMHO, I would definately want to understand the errors depending on the severity. Warnings are basically what level you are comfortable with.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply