Forum Discussion
Azure Synapse Serverless pool connection issues/ query timeout with DataLake in BR SOUTH
In the last days, my synapse dev team has noticed a problem related with the connection between serverless sql buit in pool and datalake, the problem is:
- query timeout when trying query a file stored inside datalake
- query cancelled without any response
we have noticed that this only occurs when using a private connection because in two separated synapse workspaced we have the same behavior.
creating a synapse test without private connections, everithyng is working as expected, talking with another teams that use synapse in BR SOUTH, they are relating similar problems with serverless pool.
notes:
- This is not a performance issue because it didn't work in small tables using a select top 1 without another querys running !!!
please if any know about instabilities or a way to solve this, respond this ask ! ( sorry if my english is bad)
UPDATE : This week everything is working fine, we don't know if the problem was related with instabilities inside azure or in our internal network, thanks for the replies
Private DNS records and network security group (NSG) access rules play important roles when utilising private connections to Azure SQL resources (all types.)
Of the various outcomes you can end up facing based on the various settings that control public and private endpoints, what it sounds like - to me - is that you're creating the private endpoint via the Azure portal but not creating the necessary NSG access rules between the client system and the Azure SQL private endpoint.
These access rules are not automatically created by the private endpoint creation process.
Cheers,
Lain
Hello, ismaelhenzel
Let's see if we can help you.It sounds like you are experiencing issues with the connection between your server-less SQL built-in pool and your data lake in BR SOUTH. Specifically, you are encountering query timeouts and cancellations when attempting to query a file stored within your data lake. This issue only seems to occur when using a private connection, and you have noticed similar problems among other teams that use Synapse in BR SOUTH.
One thing to note is that this is not a performance issue, as you have experienced these issues even with small tables using a select top 1 without other queries running.
Based on the information provided, it is difficult to determine the root cause of the issue. However, you may want to consider the following steps:
Verify that your network connectivity is stable and not experiencing any issues that may affect the connection between your Synapse and data lake instances.
Check if there are any known issues or outages with Synapse in your region. You can do this by checking the Azure Status page.
Consider reaching out to Azure Support for further assistance with troubleshooting this issue.
I hope this helps!
Kind Regards,
Luke Madden
"Simplifying Tech, Empowering you."Private DNS records and network security group (NSG) access rules play important roles when utilising private connections to Azure SQL resources (all types.)
Of the various outcomes you can end up facing based on the various settings that control public and private endpoints, what it sounds like - to me - is that you're creating the private endpoint via the Azure portal but not creating the necessary NSG access rules between the client system and the Azure SQL private endpoint.
These access rules are not automatically created by the private endpoint creation process.
Cheers,
Lain
