Most of my servers have sqlwatch v3. I have not updated the ddl since then.
I installed the new version 4.6 on a test server today to see what is new and different.
I see that a lot of the checks logic changed to be specific per database and per job. I see that it created a new check for each individual job to check if that job failed or not.
as a result, I went from having about 25 checks to now having 1,085 checks running!
I’m curious on the thought process behind this. Personally, I like the old way better, sqlwatch would be running 1 query against the database engine to see if any jobs failed, opposed to running 663 queries at the same time to check each job one by one.
I tested creating a new job, and it made a new check for that job. but then after I deleted that job, the check remained. so sql watch will continue querying for failures for that job that got deleted unless I manually clean them up.
I guess with this approach I could disable individual checks if there were specific jobs that I didn’t care if they failed? Is there any other benefit that I haven’t thought of? This seems like it would create more overhead needing to check each job individually, and backups for each database one by one, etc.
thanks
Matt