---
title: Troubleshooting MSSQL NRDOT monitoring
source: https://docs.newrelic.com/docs/opentelemetry/db360/mssql/troubleshooting
---

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

## Common issues [#common-issues]

### Network connectivity issues [#network-connectivity]

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:

    ```shell
    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 [#data-not-flowing]

-   To check for rate-limit-related issues, run:

    ```sql
    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](https://docs.newrelic.com/docs/logs/ui-data/drop-data-drop-filter-rules/) and [Pipeline control](https://docs.newrelic.com/docs/new-relic-control/pipeline-control/overview/).

## Related documentation [#related-docs]

[Linux instrumentation for self-hosted environments](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/linux-hosted)

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

[Windows instrumentation for self-hosted environments](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-hosted-sql)

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

[Set up APM-database correlation](https://docs.newrelic.com/docs/opentelemetry/db360/capabilities/db-apm)

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