Skip to content

Commit 6c2df60

Browse files
committed
relative links corrected
1 parent f26d423 commit 6c2df60

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/cosmos-db/nosql/change-pk.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,12 @@ ms.topic: conceptual
99
---
1010
# Changing the Partition Key in Azure Cosmos DB (Preview)
1111

12-
[!INCLUDE[NoSQL](includes/appliesto-nosql.md)]
12+
[!INCLUDE[NoSQL](../includes/appliesto-nosql.md)]
1313

1414
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:
1515

16-
- [Cross partition queries](https://learn.microsoft.com/azure/cosmos-db/nosql/how-to-query-container#avoid-cross-partition-queries)
17-
- [Hot partitions](https://learn.microsoft.com/azure/cosmos-db/nosql/troubleshoot-request-rate-too-large?tabs=resource-specific#how-to-identify-the-hot-partition)
16+
- [Cross partition queries](how-to-query-container.md#avoid-cross-partition-queries)
17+
- [Hot partitions](troubleshoot-request-rate-too-large.md?tabs=resource-specific#how-to-identify-the-hot-partition)
1818

1919
To address these issues, Azure Cosmos DB offers the ability to seamlessly change the partition key using the Azure portal.
2020

@@ -36,7 +36,7 @@ If creating a new container using the Azure portal while changing the partition
3636

3737
![Screenshot of create or select destination container screen while changing partition key in an Azure Cosmos DB account.](media/change-pk/cosmosdb-change-pk-create-container.png)
3838

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.
39+
Then, data is copied from the source container to the destination container in an offline manner utilizing the [Intra-account container copy](../container-copy.md#how-does-container-copy-work) job.
4040

4141
>[!Note]
4242
> 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.
@@ -45,5 +45,5 @@ Once the copy is complete, you can start using the new container with desired pa
4545

4646
## Next Steps
4747

48-
- Explore more about [container copy jobs](https://learn.microsoft.com/azure/cosmos-db/container-copy).
49-
- Learn further about [how to choose a partition key](https://learn.microsoft.com/azure/cosmos-db/partitioning-overview#choose-partitionkey).
48+
- Explore more about [container copy jobs](../container-copy.md).
49+
- Learn further about [how to choose a partition key](../partitioning-overview.md#choose-partitionkey).

0 commit comments

Comments
 (0)