It is now possible to use a database on another server than the one where Server Monitoring is installed.
There are different prerequisites, especially on the server where the database is located:
- the SQL Server instance must already be installed on the machine in question.
- in SQL configuration manager, on the instance in question, TCP/IP must be activated:
- You need to create a new incoming rule in the Firewall, for port 49237 in TCP
- In the instance properties, on SQL Server Management Studio (SSMS), make sure that the authentication to the server can be done as windows authent AND SQL Server :
Once this is done, you can install ServerMonitoring, except that in the "Instance Name" field, you will have to fill in the IP address of the server containing the SQL Server instance + the port + the instance name.
Example, if from a server SRV1, you want to install TSplus-ServerMonitoring and you want to use a database on server SRV2:
You put SRV2 ,49237\SQLExpress , or xxx.xxx.xxx.xxx,49237\SQLExpress , xxx.xxx... being the IP address of the server
(it's a comma, between the server address and the port, and not a colon)
If you have already installed Server Monitoring, and you want to correct it afterwards, you just have to modify directly the registry key InstanceName in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Digital River\ServerMonitoring
(and DatabaseName if you want to use another database name than the default one),
then restart the TSplus-ServerMonitoring Data Service so that the installation of the database can be done (creation of the tables and other objects)
Here is what it looks like on a sample VM, to point to serveur "dv.tsplus.net" :
