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

> #### 💡 PREVIEW
>
> We're still working on this feature, but we'd love for you to try it out!
>
> This feature is currently provided as part of a preview pursuant to our [pre-release policies](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy/).

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:

    ```shell
    Test-NetConnection -ComputerName <YOUR_IP_ADDRESS> -Port <YOUR_PORT_NUMBER>
    ```

-   For Linux, run:

    ```bash
    nc -zv <YOUR_IP_ADDRESS> <YOUR_PORT_NUMBER>
    ```

## Related documentation [#related-docs]

[Linux instrumentation for self-hosted environments](https://docs.newrelic.com/docs/opentelemetry/database/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/database/mssql/windows-hosted)

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/database/capabilities/db-apm)

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