Azure Database unable to update Datasync config & Datastudio timeout

Question

Azure Database unable to update Datasync config & Datastudio timeout

John Tsui 0

We seem to be having 2x issues with an Azure SQL database.

Datasync keeps failing sync data & reconfiguring of tables to sync.
The database is timing out populating the tree of table in both SQL Management Studio & Azure Data Studio.

The Majority of errors are similar to this:

Database re-provisioning failed with the exception "SqlException ID: b69a17fb-091d-4ab9-923a-e6f6f31de755, 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 ‘65871053-2d9b-48b9-b0b2-d4f28b4b41d8’ to customer support."

Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-04T09:35:02.4066667+00:00
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.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-04T21:28:41.18+00:00

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?
John Tsui 0 Reputation points

2025-06-05T01:23:20.55+00:00

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.
John Tsui 0 Reputation points

2025-06-05T01:33:08.5966667+00:00

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."
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-05T21:01:25.14+00:00

It starts to sound to me like this is a blocking issue. Like there is an uncommitted DDL operation. Can you run DBCC OPENTRAN to see if it returns anything?
John Tsui 0 Reputation points

2025-06-10T08:32:24.3666667+00:00

We didn't get anything from DBCC OPENTRAN.

Started executing query at Line 1 No active open transactions. DBCC execution completed. If DBCC printed error messages, contact your system administrator. Total execution time: 00:00:00.003
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-10T21:09:20.9266667+00:00
Without access to the system it is difficult to diagnose, but here is one more shot in the dark. Run:

SELECT 'UPDATE STATISTICS sys.' + name FROM sys.objects WHERE type = 'S'

And the copy and paste the result into a query window and execute it. The idea here is that the statistics on some system table is not in good shape.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-11T16:16:22.5466667+00:00
Hi John Tsui

Azure SQL Data Sync can leave behind orphaned or stale provisioning metadata.

Try:

Remove the sync group completely (not just reconfigure).

Recreate sync group from scratch, preferably starting with a single table, then scaling up.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-12T14:39:54.7866667+00:00

Hi John Tsui

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-13T13:56:45.34+00:00

Hi John Tsui

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
John Tsui 0 Reputation points

2025-06-15T23:10:44.74+00:00

Thanks everyone, we still aren't unsure of what the issues was, but it is resolved after the Azure Region Maintenance was complete and we could browse in SSMS, we added back some tables to sync, it took around 6 hours to sync (3x small tables at most 300 rows).

After this initial sync every other table added back only had a very short sync time, no more than 15mins max.

1 answer

Your answer

Vijayalaxmi Kattimani 3,250 Reputation points Microsoft External Staff Moderator

2025-06-04T09:35:02.4066667+00:00

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.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-04T21:28:41.18+00:00

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?
John Tsui 0 Reputation points

2025-06-05T01:23:20.55+00:00

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.
John Tsui 0 Reputation points

2025-06-05T01:33:08.5966667+00:00

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."
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-05T21:01:25.14+00:00

It starts to sound to me like this is a blocking issue. Like there is an uncommitted DDL operation. Can you run DBCC OPENTRAN to see if it returns anything?
John Tsui 0 Reputation points

2025-06-10T08:32:24.3666667+00:00

We didn't get anything from DBCC OPENTRAN.

Started executing query at Line 1 No active open transactions. DBCC execution completed. If DBCC printed error messages, contact your system administrator. Total execution time: 00:00:00.003
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2025-06-10T21:09:20.9266667+00:00

Without access to the system it is difficult to diagnose, but here is one more shot in the dark. Run:

SELECT 'UPDATE STATISTICS sys.' + name FROM sys.objects WHERE type = 'S'

And the copy and paste the result into a query window and execute it. The idea here is that the statistics on some system table is not in good shape.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-11T16:16:22.5466667+00:00

Hi John Tsui

Azure SQL Data Sync can leave behind orphaned or stale provisioning metadata.

Try:

Remove the sync group completely (not just reconfigure).

Recreate sync group from scratch, preferably starting with a single table, then scaling up.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-12T14:39:54.7866667+00:00

Hi John Tsui

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
PratikLad 1,825 Reputation points Microsoft External Staff Moderator

2025-06-13T13:56:45.34+00:00

Hi John Tsui

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.

In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
John Tsui 0 Reputation points

2025-06-15T23:10:44.74+00:00

Thanks everyone, we still aren't unsure of what the issues was, but it is resolved after the Azure Region Maintenance was complete and we could browse in SSMS, we added back some tables to sync, it took around 6 hours to sync (3x small tables at most 300 rows).

After this initial sync every other table added back only had a very short sync time, no more than 15mins max.

Answer 1

Hi John Tsui

Glad to know John Tsui you have solved it. I am collating the data in one place for anyone in the QnA forum to refer to it

It’s likely that underlying infrastructure issues affected your logical server or specific database instance. Regional platform-level updates or issues can cause "invisible" performance degradation.

Azure SQL Data Sync can leave behind orphaned or stale provisioning metadata.

Remove the sync group completely (not just reconfigure).
Recreate sync group from scratch, preferably starting with a single table, then scaling up.

Letting the initial (potentially bloated) sync finish, which cleared whatever bottleneck was blocking further provisioning.

Share via

Azure Database unable to update Datasync config & Datastudio timeout

1 answer

Your answer