Skip to content

Commit dff55c1

Browse files
authored
Update analytical-store-introduction.md
1 parent 89c7451 commit dff55c1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/analytical-store-introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -185,8 +185,8 @@ There are two types of schema representation in the analytical store. These type
185185
It is possible to use full fidelity Schema for SQL (Core) API accounts, instead of the default option, by setting the schema type when enabling Synapse Link on a Cosmos DB account for the first time. Here are the considerations about changing the default schema representation type:
186186

187187
* This option is only valid for accounts that **don't** have Synapse Link already enabled.
188-
* It is not possible to reset the schema representation type, from well-defined to full fidelity or vice-versa.
189-
* Currently Azure Cosmos DB API for MongoDB accounts are not compatible with this possibility of changing the schema representation. All MongoDB accounts will always have full fidelity schema representation type.
188+
* It isn't possible to reset the schema representation type, from well-defined to full fidelity or vice-versa.
189+
* Currently Azure Cosmos DB API for MongoDB accounts aren't compatible with this possibility of changing the schema representation. All MongoDB accounts will always have full fidelity schema representation type.
190190
* Currently this change can't be made through the Azure portal. All database accounts that have Synapse LinK enabled by the Azure portal will have the default schema representation type, well defined schema.
191191

192192
The schema representation type decision must be made at the same time that Synapse Link is enabled on the account, using Azure CLI or PowerShell.

0 commit comments

Comments
 (0)