---
title: Configuration reference for Microsoft SQL Server monitoring with NRDOT
source: https://docs.newrelic.com/docs/opentelemetry/db360/mssql/config-reference
---

This reference provides comprehensive YAML configurations for Microsoft SQL Server monitoring with the New Relic Distribution of OpenTelemetry (NRDOT) Collector. These full-feature configurations include all available metrics, advanced processor settings, and optimized pipelines for production environments across Linux and Windows, both self-hosted and AWS RDS deployments.

> #### ⚠️ IMPORTANT
>
> **Looking to get started quickly?** These are advanced configurations for production use. If you're setting up SQL Server monitoring for the first time, we recommend starting with the standard configurations in our setup guides and returning to these comprehensive configurations once you've verified basic functionality.

## For Linux [#linux]

**For Linux self-hosted**

This configuration provides comprehensive database monitoring with all available metrics for Linux self-hosted environments.

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Linux self-hosted guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/linux-hosted) to complete the setup.

**For Linux RDS**

This configuration provides comprehensive database monitoring with all available metrics for AWS RDS SQL Server environments on Linux.

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Linux RDS guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/linux-rds) to complete the setup.

## For Windows [#windows]

**For Windows self-hosted - SQL Server authentication**

This configuration provides comprehensive database monitoring with all available metrics for Windows self-hosted environments using SQL Server authentication.

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows self-hosted guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-hosted-sql) to complete the setup using SQL Server authentication.

**For Windows self-hosted - Windows domain authentication**

This configuration provides comprehensive database monitoring with all available metrics for Windows self-hosted environments using Windows Domain Authentication (integrated security).

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows self-hosted guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-hosted-domain) to complete the setup using Windows authentication.

**For Windows self-hosted - gMSA authentication**

This configuration provides comprehensive database monitoring with all available metrics for Windows self-hosted environments using gMSA authentication (integrated security).

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows self-hosted guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-hosted-gmsa) to complete the setup using gMSA authentication.

**For Windows RDS - SQL Server authentication**

This configuration provides comprehensive database monitoring for Windows environments connecting to AWS RDS SQL Server instances using SQL Server authentication.

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows RDS guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-rds-sql) to complete the setup using SQL Server authentication.

**For Windows RDS - Windows domain authentication**

This configuration provides comprehensive database monitoring for Windows environments connecting to AWS RDS SQL Server instances using Windows Domain Authentication (integrated security).

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows RDS guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-rds-domain) to complete the setup using Windows authentication.

**For Windows RDS - gMSA authentication**

This configuration provides comprehensive database monitoring for Windows environments connecting to AWS RDS SQL Server instances using Group Managed Service Account (gMSA) authentication with integrated security.

Once you've downloaded or pasted the full configuration into your `mssql-config.yaml` file, follow the [Windows RDS guide](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/windows-rds-gmsa) to complete the setup using gMSA authentication.

## Configure the receiver [#receiver]

You can use `max_concurrent_queries` to control how many metric queries the receiver executes in parallel against SQL Server during each scrape cycle. The default value is 4 if omitted or set to 0.

```yaml
receivers:
  nrsqlserver:
    max_concurrent_queries: 4  # default is 4 if omitted or set to 0
```

## Related documentation [#related-docs]

[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.

[Metrics reference](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/metrics-reference)

Learn about the available metrics collected by the NRDOT Collector.

[Troubleshooting](https://docs.newrelic.com/docs/opentelemetry/db360/mssql/troubleshooting)

Learn how to troubleshoot your MSSQL monitoring setup in New Relic.