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/nosql/change-pk.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,16 +11,16 @@ ms.topic: conceptual
11
11
12
12
[!INCLUDE[NoSQL](includes/appliesto-nosql.md)]
13
13
14
-
In the realm of database management, it is not uncommon for the initially chosen partition key for a container to become inadequate as applications evolve. This can result in suboptimal performance and increased costs for the container. Several factors contributing to this situation include:
14
+
In the realm of database management, it isn't uncommon for the initially chosen partition key for a container to become inadequate as applications evolve. It can result in suboptimal performance and increased costs for the container. Several factors contributing to this situation include:
To address these issues, Azure Cosmos DB offers the ability to seamlessly change the partition key using the Azure Portal.
19
+
To address these issues, Azure Cosmos DB offers the ability to seamlessly change the partition key using the Azure portal.
20
20
21
21
## Getting Started
22
22
23
-
To change the partition key of a container in Azure Cosmos DB for the NoSQL API using the Azure Portal, follow these steps:
23
+
To change the partition key of a container in Azure Cosmos DB for the NoSQL API using the Azure portal, follow these steps:
24
24
25
25
1. Navigate to the **Data Explorer** in the Azure Cosmos DB portal and select the container for which you need to change the partition key.
26
26
2. Proceed to the **Scale & Settings** option and choose the **Partition Keys** tab.
@@ -36,7 +36,7 @@ If creating a new container using the Azure portal while changing the partition
36
36
37
37

38
38
39
-
Subsequently, data is copied from the source container to the destination container in an offline manner utilizing the [Intra-account container copy](https://learn.microsoft.com/azure/cosmos-db/container-copy#how-does-container-copy-work) job.
39
+
Then, data is copied from the source container to the destination container in an offline manner utilizing the [Intra-account container copy](https://learn.microsoft.com/azure/cosmos-db/container-copy#how-does-container-copy-work) job.
40
40
41
41
>[!Note]
42
42
> It is recommended to stop all updates on the source container before proceeding to change the partition key of the container for entire duration of copy process to maintain data integrity.
0 commit comments