Skip to content

Commit b9901b4

Browse files
authored
added timeout information
1 parent 7ad118a commit b9901b4

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

articles/sql-database/sql-database-best-practices-data-sync.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -212,6 +212,14 @@ Instead, first remove a database from a sync group. Then, deploy the change and
212212

213213
If you attempt to remove a database and then edit a sync group without first deploying one of the changes, one or the other operation fails. The portal interface might become inconsistent. If this happens, refresh the page to restore the correct state.
214214

215+
### Avoid refresh schema timeout
216+
217+
If you have a complex schema to sync, during a refresh schema you may encounter an "operation timeout" if the sync metadata between databases has a lower SKU (example: basic).
218+
219+
#### Solution
220+
221+
To mitigate this issue, please scale up your sync metadata database to have a higher SKU, such as S3.
222+
215223
## Next steps
216224
For more information about SQL Data Sync, see:
217225

0 commit comments

Comments
 (0)