We're trialing SQL Monitor 2.3 in our environment and I'm having some issues with suspended monitoring. I also have some questions about DB filtering.
We have a few solutions where a database will be backed up from one environment/server, and then copied/restored to another as a means of bulk data transfer over some very slow links.
Each day the DB will be recreated, backed up, copied and restored again. SQL Monitor loses it's permissions each time this happens, and suspends monitoring for all databases.
Now, I know the 'simple' answer is "just add the permissions before you backup", but we're in strict RBAC security contexts, and the security context between the environments is different. It's not practical to essentially embed SQL Monitor roles into our applications/solutions. We're also not comfortable integrating a monitoring tool that closely.
We're also not allowed to run SQL Monitor under an 'sa' account. (Again, highly secure environment).
Ideally, if there was a way to disable monitoring for certain databases, I think this would solve our issue. Our of 20-30 db's, there are only 5 that really need constant monitoring, others are archives, or temp data stores.
It's quite annoying that SQL Monitor needs access to all of these databases, even though we have no interest in monitoring them.