I'm guessing that this is not recommended but what issues could come up by installing the SQL Monitor on the same server that you are trying to monitor. And if that becomes our only option, does creating another sql instance for the SQL Monitor database solve anything?
Comments
1 comment
-
Hi Configio,
Thanks for posting on the Redgate forums.
You are correct that the setup described isn't recommended. The main issue is if you start seeing performance issues on the server these will be exacerbated by SQL Monitor.
You end up in a loop where the server has low resource/memory and SQL Monitor is trying to write to a struggling server to alert on a struggling server.
We do see problems of this nature very rarely however it is something to take into consideration.
Add comment
Please sign in to leave a comment.