Azure Database unable to update Datasync config & Datastudio timeout

Hi John Tsui

Greetings!

As we understand that, you are dealing with two issues—Azure SQL Data Sync failures and database timeouts in SQL Management Studio & Azure Data Studio. The error code -2 typically indicates a timeout issue, which can be caused by high resource utilization, network latency, or contention within the database.

Here are a few troubleshooting steps you can try:

Regarding Data Sync failures:

We would like to inform you that, a common resolution is to check the sync job history for any failed changes and resolve those. In some cases, if a sync group has an "Out-of-Date" status, it might be necessary to delete and re-create that sync group.

I would also suggest that you check the following items as well.

• Make sure that sync group configuration is correct.
• Make sure that, the tables being synced don’t have unsupported data types or constraints.
• Make sure that the sync agent is running properly.

Regarding Timeout in Azure Data Studio & SQL Management Studio:

• Increase the timeout settings in SQL Management Studio or Azure Data Studio.
• Review and optimize your SQL queries to enhance performance.
• If your database is running at a high DTU percentage, consider scaling up to a higher tier to improve performance.
• If the issue is sporadic, it could be related to network instability.
• Implement a retry policy in your application to handle intermittent failures.

If the issue still persists, could you please share the requested details via private message as it will help us conduct a more thorough investigation.

I hope this information helps. Please do let us know if you have any further queries.

Which version of SSMS are you using? When I test to list the tables for a database where I have an uncommitted DDL statement on a table, SSMS 21 seems to wait forever.

The error code -2 is not an error from SQL Server, but from SSMS itself, or more precisely the underlying client API, which is where the timeout elapses. The timeout is controllable as such, but I can't see a setting for Object Explorer.

On the other hand, the default timeout is 30 second, and that is quite long time to get tables listed, so it's unbearable anyway. What service tier do you have for your database?

Hi Erland,

We are using both 18 and 2x versions.. we have been seeing that 2x version are slower than 18 for some time.. our issues seem to be related to just this specific SQL database, other Database in the same Share Pool do not experience this issue currently.

We are actually having this issue from any Query editor (Preview) from the Azure portal itself and Azure Data Studio... we can Execute SQL queries it just seems to be related to the browsing functions that feed the UI.. so it also affects other things like IntelliSense as well.

Vijayalaxmi Kattimani

We considered the load, but could not find any sustained issues with resources Monitoring shows <30% the majority of the time.

We tried to reconfigure the Sync Group and re-add tables one at a time, but now we get re-provisioning errors.

Some of the tables are very small with only 8x rows to 150x rows.

Database re-provisioning failed with the exception "SqlException ID: d865a0d2-eb59-4e09-a963-502ca2ef1ddb, Error Code: -2146232060 - SqlError Number:-2, Message: SQL error with code -2 Inner exception: The wait operation timed out For more information, provide tracing ID ‘52c1f193-086b-400a-9cad-efd83474e7a9’ to customer support."