Use the Spotlight Cloud Diagnostic Server App to manage connections
The Spotlight Cloud Diagnostic Server App is installed locally. Double click the desktop icon.
Sign in with your Quest account, and then from the Configuration panel, click Connections.
This opens the Spotlight Connection Manager. To enter connection details either double click Add new Connection or double click on the connection with details you want to edit.
Specify the connect string used to link to the SQL Server (that is, the Server Name, Server Instance Name, or IP address).
For a Microsoft Cluster Server (MSCS) enter the virtual name of the cluster.
If the SQL Server instance is hosted on a Windows server and UDP port 1434 is closed then the port number must be included in the address used to connect Spotlight Cloud to the SQL Server instance.
Specify the authentication for Spotlight Cloud to use to connect to the SQL Server instance.
Select Windows Authentication (using Diagnostic Server credentials) to use the Windows user configured to run the Spotlight Cloud Diagnostic Server (as a Windows service). Ensure this account is trusted by the SQL Server instance. When using Windows authentication to connect to a SQL Server, and that SQL server is in a different domain to the Spotlight Cloud Diagnostic Server, the domain the SQL Server is in must trust the domain the Spotlight Cloud Diagnostic Server is in.
Alternatively, fill in the Database User and Password fields. Ensure the database user has sufficient account permissions to retrieve performance data from the SQL Server instance and host by WMI. Typically the account will be a member of the sysadmin server role. It could be a SQL Server login (such as ‘sa’). If this is not feasible in your environment, see How to grant SQL Server account permissions to a trusted user.
The connection will fail if the account permissions are insufficient to allow Spotlight Cloud to collect the data it needs.
Read Only Intent
Select this option if the SQL Server instance hosts a secondary replica of an Availability Group and for this secondary replica ApplicationIntent=ReadOnly. Failure to select this option when required will result in some data not being collected for the secondary replica.
Use Extended Events
The Spotlight Cloud Diagnostic Server will use Extended Events to collect data from the SQL Server instance.
The Spotlight Cloud Diagnostic Server will use SQL Server Trace to collect data for deadlock checks.
Select the Windows server hosting the SQL Server.
Do not monitor
Select Do not monitor if you do not want Spotlight Cloud to monitor the Windows server.
Cluster (monitor active node)
Select Cluster (monitor active node) for a Microsoft Cluster Server (MSCS).
Spotlight Cloud uses the current host node name to select the operating system connection. Therefore each Windows node in the cluster must be monitored by Spotlight Cloud. Verify each Windows node is in the list of Windows server connections.
Click Create to add a Windows server to the list. Manage Windows Server Connections.
Select the alarms configuration template to apply to this connection or select Factory Settings Template to apply the Factory Settings shipped with Spotlight Cloud. Select from any of the SQL Server configuration templates that you have created through Configure Alarms.
The template will apply to the Windows host of the SQL Server instance if known / monitored by Spotlight Cloud.
The alarms template option is applicable only when creating a new SQL Server connection. To apply a template to an existing SQL Server connection, see Configuration Templates.