Troubleshooting MSSQL NRDOT monitoring

Troubleshoot common issues you may encounter when monitoring your Microsoft SQL Server with the NRDOT Collector.

Common issues

Network connectivity issues

If you encounter any network connectivity issues with the NRDOT Collector, run the following commands to test connectivity to your SQL Server instance:

For Windows, run:
bash
```
$Test-NetConnection -ComputerName <YOUR_IP_ADDRESS> -Port <YOUR_PORT_NUMBER>
```

For Linux, run:

bash

$nc -zv <YOUR_IP_ADDRESS> <YOUR_PORT_NUMBER>

Data not appearing in New Relic

To check for rate-limit-related issues, run:
```
SELECT * FROM NrIntegrationError
```
If data still isn't flowing, check whether there are any drop rules set on your Metric and Log events. See Drop log data with drop filter rules and Pipeline control.

Linux instrumentation for self-hosted environments

Learn how to set up MSSQL monitoring in self-hosted Linux environments with New Relic.

Windows instrumentation for self-hosted environments

Learn how to set up MSSQL monitoring in self-hosted Windows environments with New Relic.

Set up APM-database correlation

Learn how to correlate your application performance with database operations in New Relic.