QUESTION:
How to monitor SQL Server Express or Named Instances?
RESOLUTION:
Out of the box, Traverse will attempt to discover performance/availability metrics from the default instance of Microsoft SQL Server. If you are running SQL Server Express, or a named instance of SQL Server, Traverse may not be able to discover any relevant metrics. This is due to the difference in naming of the relevant WMI classes for difference version/instance of SQL Server. In order to add support for SQL Server Express, the following steps will need to be performed:
- On the BVE server:
- Launch Windows Explorer and navigate into Traverse installation directory (eg. C:\Program Files (x86)\Traverse).
- Create a copy of etc\typedef\95_wmi_ms_sqlsvr.xml as plugin\monitors\95_wmi_ms_sqlsvr_express.xml.
- Right click on plugin\monitors\95_wmi_ms_sqlsvr_express.xml and open the file using Notepad.
- Press Control-H to search and replace all occurrences of MSSQLSERVER_SQLServer with MSSQLSQLEXPRESS_MSSQLSQLEXPRESS.
- Save the file.
The same steps are applicable if Traverse DGE is running on Linux/Solaris with appropriate path names. Now when you perform WMI test discovery via Administration -> Devices -> Tests (for server running SQL Server Express) -> Add New Standard Tests, metrics for the SQL Server Express will be discovered.
The same procedure is also applicable for named instances of Microsoft SQL Server. You will need to create a copy of etc\typedef\95_wmi_ms_sqlsvr.xml under plugin\monitors directory with unique suffix (similar to_express above) and replace all occurrences of MSSQLSERVER_SQLServer with MSSQLSQLXYZ_MSSQLSQLXYZ where XYZ is the name of the instance. (It has been reported by one customer that all occurrences may need to be replaced with MSSQLXYZ_MSSQLXYZ. You may want to review the class names using wbemtest).
Please also note that when monitoring multiple named instances against the same Microsoft SQL Server, the test names in the signature will need to be prefixed with the instance name.
For SaaS customer, kindly open a ticket with support and attach the modified file.