Redaguoti

Dalintis per


Warehouse connectivity

Applies to: ✅ SQL analytics endpoint and Warehouse in Microsoft Fabric

In Microsoft Fabric, users access a SQL analytics endpoint or Warehouse through a Tabular Data Stream (TDS) endpoint. This endpoint is familiar to all modern web applications that interact with a SQL Server TDS endpoint. Within Microsoft Fabric settings, this endpoint is labeled as the SQL connection string.

Tip

For a tutorial on connecting with common tools, see Connect to Fabric Data Warehouse.

Authentication to warehouses in Fabric

In Microsoft Fabric, the SQL connection string supports two types of authenticated users:

  • Microsoft Entra ID user principals, or user identities
  • Microsoft Entra ID service principals

For more information, see Microsoft Entra authentication as an alternative to SQL authentication in Microsoft Fabric.

The SQL connection string requires TCP port 1433 to be open. TCP 1433 is the standard SQL Server port number. The SQL connection string also respects the Warehouse or Lakehouse SQL analytics endpoint security model for data access. Users can access data for all objects to which they have permission.

For more information about security in the SQL analytics endpoint, see OneLake security for SQL analytics endpoints.

Best practices

Add retries to your applications and ETL jobs to make them more resilient. For more information, see the following documentation:

Allow Azure service tags through firewall

To enable connectivity through the firewall, you need to allow Power BI service tags and SQL service tags. For more information, see Power BI Service Tags and Service tags.

You can't use the Fully Qualified Domain Name (FQDN) of the TDS Endpoint alone.

Considerations and limitations

  • SQL Authentication isn't supported.
  • Multiple Active Result Sets (MARS) isn't supported for Microsoft Fabric Warehouse. MARS is disabled by default. If MultipleActiveResultSets is included in the connection string, remove it or set it to false.
  • If you receive the error "Couldn't complete the operation because we reached a system limit", it's due to the system token size reaching its limit. This error can occur if the workspace has too many warehouses or SQL analytics endpoints, if the user is part of too many Microsoft Entra groups, or a combination of these two factors. To prevent this error, limit the number of warehouses and SQL analytics endpoints per workspace to 40 or fewer. If the error persists, contact support.
  • If you receive error code 24804 with the message "Couldn't complete the operation due to a system update. Close out this connection, sign in again, and retry the operation" or error code 6005 with the message "SHUTDOWN is in progress. Execution fail against sql server. Please contact SQL Server team if you need further support.", it's due to temporary connection loss, likely because of a system deployment or reconfiguration. To resolve this issue, sign in again and retry. To learn how to build resiliency and retries in your application, see Best Practices.
  • Linked server connections from SQL Server aren't supported.

Next step