How to find out, where (on which SQL server and instance, if any) are the SQL databases used by the Operations Manager?
In the product console we will not find this information (at most we will eventually track down the monitored SQL databases and hit the ones of interest to us). In theory, the post-implementation documentation should contain such information. In practice, however, it varies.
However, in order to check which databases our Operations Manager All you have to do is look at the registry on one of the management servers (Management Server). When you hit the right place, you can already see what the servers, instances and SQL database names are. The place to look in the registry is the key:Â HKLMSOFTWAREMicrosoft Operations Manager3.0Setup.. Inside we will see:
Using the REG QUERY command, this information can be displayed in text mode:
There remains the issue of the possible database used by the component for collecting Security log entries, the ACS. The service ACS is not always enabled, so in many cases there is no need to look for this base. Here it is not so simple. First you need to check the configuration of the ADTServer collector service:
The ODBCConnection variable indicates the name of the ODBC source, which needs to be found in another entirely different registry location:
Only now you can see that the SQL database is named OperationsManagerAC, while it is located on the same server on which the ACS collector runs (the Server variable has the value ".").