Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Monitoring a remote SQL Server Expand / Collapse
Author
Message
Posted Friday, September 27, 2013 8:29 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, December 11, 2013 2:22 PM
Points: 1, Visits: 19
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
Post #1499422
Posted Monday, September 30, 2013 11:49 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 7:30 AM
Points: 414, Visits: 1,332
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/

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.
Post #1500137
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse