Stop monitoring server from executing xp_cmdshell (4286000)

Stop monitoring server from executing xp_cmdshell

Example scenario: have two SQL clusters both having the xp_cmdshell disabled. However, we can see xp_cmdshell commands going from the monitoring server to the SQL clusters. In Spotlight when drilling down to Support Services -> Cluster Services, on one of the clusters it immediately displays "Cannot use xp_cmdshell". No Data Available". On the other cluster however, it displays a "No data" after staying a long time in the Loading phase. The question is how we can stop the monitoring server to execute xp_cmdshell commands against one of the SQL Clusters?

We have raised enhancement request case SOSSE-2347 to include an option “Do not run this collection ever” in the Scheduling dialog for your this case issue.

In the meantime as a work around try the following.

The product runs xp_cmdshell command in 2 cases:
( Please copy original file to other folder)

1. Once a day the Diagnostic Server runs the QS_ClusterInfo.sql script to get cluster setup information.
You can find this script in the <Quest Software>\Diagnostic Server\Agent\conf\Package\sqlserver_spotlight\20** folder (which corresponds to version of monitored SQL Server) on the Diagnostic Server-machine, open it as text file, remove all SQL statements leaving the file blank and save changes.

2. The product runs QS_ServiceControl.sql script located in the same directory when you navigate to the Support Services drilldown using Spotlight-client.
You can either avoid opening this drilldown in Spotlight or similar to point 1 above remove all SQL text from the QS_ServiceControl.sql script leaving the file blank, and save the file.

SOSSE-2347