You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/analytical-store-introduction.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -409,16 +409,17 @@ Although analytical store has built-in protection against physical failures, bac
409
409
> [!NOTE]
410
410
> Currently analytical store isn't backuped and can't be restored, and your backup policy can't be planned relying on that.
411
411
412
-
Synapse Link, and analytical store by consequence, has different compatibility level with Azure Cosmos DB backup modes:
412
+
Synapse Link, and analytical store by consequence, has different compatibility levels with Azure Cosmos DB backup modes:
413
413
414
414
* Periodic backup mode is fully compatible with Synapse Link and these 2 features can be used in the same database account without any restriction.
415
-
* Currently continuous backup mode isn't supported in database accounts with Synapse Link enabled.
416
-
* Currently database accounts with continuous backup mode enabled can enable Synapse Link through a support case.
417
-
* Currently new database accounts can be created with continous backup mode and Synapse Link enabled, using Azure CLI or PowerShell. Those two features must be turned on at the same time, in the exact same command that creates the database account.
* Currently continuous backup mode can't be used in database accounts with Synapse Link enabled.
417
+
* Currently database accounts with continuous backup mode enabled can enable Synapse Link through a support case.
418
+
* Currently new database accounts can be created with continous backup mode and Synapse Link enabled, using Azure CLI or PowerShell. Those two features must be turned on at the same time, in the exact same command that creates the database account.
418
419
419
420
### Backup Polices
420
421
421
-
There two possible backup polices and to understand how it works, two details about Cosmos DB backups are very important:
422
+
There two possible backup polices and to understand how to use them, two details about Cosmos DB backups are very important:
422
423
423
424
* The original container is restored without analytical store in both backup modes.
424
425
* Cosmos DB doesn't support containers overwrite from a restore.
0 commit comments