September 27, 2013 at 8:29 am
Can dbWarden be installed on a nonproduction SQL Server and be used to monitor a production server? I installed dbWarden in our test environment and really like what dbWarden has to offer, but I was wondering if there was a way to point the same installation to monitor our production environment as well. Thank You, Rob
September 30, 2013 at 11:49 am
robrseidel (9/27/2013)
Can dbWarden be installed on a nonproduction SQL Server and be used to monitor a production server? I installed dbWarden in our test environment and really like what dbWarden has to offer, but I was wondering if there was a way to point the same installation to monitor our production environment as well. Thank You, Rob
Did you check the website's wiki?
A simply search via Google found this:
DBWarden can be installed by simply running the SQL script on your database server. There is a header in the file that contains the objects included in the script and brief install instructions. The script can be found on our Sourceforge page http://sourceforge.net/projects/dbwarden/.
Taken from this link: http://www.sqlservercentral.com/articles/Monitoring/98106/%5B/url%5D
So I would suggest open the setup script and look for something similar to db server name or target name. You can also setup on your Dev box and see what happens. After all, it's your Dev box. If does not work or fails, you still can go back and delete or try again.
Usually, monitoring tools use a web service interface, an agent and a database repository. Those can be installed outside the production server but the actual agent that sends the monitoring information. I have not used DBWarden myself but I would be surprise if you can't do the same.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply