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/configure-synapse-link.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ Use `EnableAnalyticalStorage true` for both **create** or **update** operations.
77
77
78
78
## <aid="create-analytical-ttl"></a> Create an analytical store enabled container
79
79
80
-
You can turn on analytical store on an Azure Cosmos DB container while creating the container. You can use the Azure portal or configure the `analyticalTTL` property to `-1` during container creation by using the Azure Cosmos DB SDKs or command line tools.
80
+
You can turn on analytical store when creating an Azure Cosmos DB container by setting `analytical TTL` property. While Portal will implicitly set it to `-1`, that means infinite retention of the data, SDKs and command line tools allow you to also use positive integers, that represent the retention in seconds. For information on the various `analytical TTL` config options, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article. Please note that you can change `analytical TTL` to another value later.
81
81
82
82
### Azure portal
83
83
@@ -200,15 +200,19 @@ Use the options below using `-AnalyticalStorageTtl -1` to enable analytical stor
200
200
201
201
## <aid="update-analytical-ttl"></a> Enable analytical store for an existing container
202
202
203
-
You can turn analytical store on for existing containers in Cosmos DB SQL API accounts only. Please note these important information about the process.
203
+
You can turn on analytical store on an existing Azure Cosmos DB SQL API container by setting `analytical TTL` property. While Portal will implicitly set it to `-1`, that means infinite retention of the data, SDKs and command line tools allow you to also use positive integers, that represent the retention in seconds. For information on the various `analytical TTL` config options, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article. Please note that you can change `analytical TTL` to another value later.
204
+
205
+
Please note these important information about the process.
204
206
205
207
* The initial sync with analytical store total time will vary depending on your data volume and on the complexity of the documents.
206
208
* The throughput of your container or database account also influences the total sync time. Although RU/s are not used in this migration, the total RU/s available influences the performance of the sync process.
207
209
* You won't be able to query analytical store of an existing container until the end of the initial sync process.
208
210
209
211
> [!NOTE]
210
-
> Due to short-term capacity constraints, you need to register to enable Synapse Link on your existing containers. Depending on the pending requests, approving this request may take anywhere from a day to a week. Please come back here to check the status. If you have any issues or questions, please reach out to [[email protected]](mailto:[email protected]). This step is required once per subscription, and all new database accounts will also have this capability enabled.
212
+
> Currently exiosting MongoDB API collections are not supported. The alternative is to migrate the data into a new collection, created with analytical store turned on.
211
213
214
+
> [!NOTE]
215
+
> Due to short-term capacity constraints, you need to register to enable Synapse Link on your existing containers. Depending on the pending requests, approving this request may take anywhere from a day to a week. Please come back here to check the status. If you have any issues or questions, please reach out to [[email protected]](mailto:[email protected]). This step is required once per subscription, and all new database accounts will also have this capability enabled.
212
216
213
217
> [!NOTE]
214
218
> Currently it is not possible to turn off analytical store from a container. Click [here](analytical-store-introduction.md#analytical-store-pricing) for more information about analytical store pricing.
@@ -249,7 +253,7 @@ Use the options below using `-AnalyticalStorageTtl -1` to enable analytical stor
249
253
250
254
## <aid="update-analytical-ttl"></a> Optional - Update the analytical store time to live
251
255
252
-
After the analytical store is enabled with a particular TTL value, you may want to update it to a different valid value later. You can update the value by using the Azure portal, Azure CLI, PowerShell, or Cosmos DB SDKs. For information on the various Analytical TTL config options, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article.
256
+
After the analytical store is enabled with a particular TTL value, you may want to update it to a different valid value. You can update the value by using the Azure portal, Azure CLI, PowerShell, or Cosmos DB SDKs. For information on the various Analytical TTL config options, see the [analytical TTL supported values](analytical-store-introduction.md#analytical-ttl) article.
0 commit comments