Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

From notebook, with jdbc connector, we can't connect to SQL Virtual Machine (legacy)

We are developing a new Data Platform on Fabric and we need to write data from Fabric notebook to a SQLVM (legacy), as part of our immediate release. From notebook, with jdbc connector, we can't connect.

 

Error message from Notebook cell: 

Py4JJavaError: An error occurred while calling o4725.jdbc.
: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host x.x.x.x, port 1433 has failed. Error: "connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

 

Anyone with any workaround?

  • Hello Anonymous 

     

    Microsoft Fabric notebooks cannot use on-premises data gateways for connectivity to legacy SQL VMs or other on-prem resources

     

    From the Fabric security documentation on Private Links:
    “For Fabric users: On-premises data gateways aren’t supported and fail to register when Private Link is enabled. To run the gateway, disable Private Link for the tenant.”

     

    https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview

     

     


    This limitation applies specifically to notebooks due to their reliance on Spark clusters, which operate in isolated managed virtual networks.

     

    In contrast, other Fabric tools like Dataflows Gen2 and Pipelines fully support on-premises gateways for secure data integration.
    For notebooks, Microsoft recommends:
    • Using Dataflows Gen2 (low-code ETL with gateway support) or Pipelines (gateway-enabled data orchestration) instead.
    • Avoiding direct SQL VM exposure by staging data in OneLake or Azure Blob Storage first

     

     

2 Replies

  • Hello Anonymous 

     

    Microsoft Fabric notebooks cannot use on-premises data gateways for connectivity to legacy SQL VMs or other on-prem resources

     

    From the Fabric security documentation on Private Links:
    “For Fabric users: On-premises data gateways aren’t supported and fail to register when Private Link is enabled. To run the gateway, disable Private Link for the tenant.”

     

    https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview

     

     


    This limitation applies specifically to notebooks due to their reliance on Spark clusters, which operate in isolated managed virtual networks.

     

    In contrast, other Fabric tools like Dataflows Gen2 and Pipelines fully support on-premises gateways for secure data integration.
    For notebooks, Microsoft recommends:
    • Using Dataflows Gen2 (low-code ETL with gateway support) or Pipelines (gateway-enabled data orchestration) instead.
    • Avoiding direct SQL VM exposure by staging data in OneLake or Azure Blob Storage first

     

     

    • jenniferjohn's avatar
      jenniferjohn
      New Member

      You can stay updated with recent incidents in Kentucky by checking reliable sources. If you're looking for details on specific counties, busted warren county provides useful insights. Keeping informed about local events helps in understanding community trends and safety updates.