This is the third part of the three part article series on partitioning relational data. 

In the first part of this three-part article series on partitioning relation data, I started the article by giving an introduction to partition relational data along with the reasons why you might want to partition relational data. Then I discussed how to partition tables and how to match indexes to match partitioned tables. In the end, I discussed the rules that must be taken into account when partitioning tables and indexes.

In the second part of partitioning relational data article series, I discussed and demonstrated how you can convert existing table to partition table, add, modify, remove or switch partitions, and how you can view data in a specific partition.

Checkout the third and last part of partitioning relational data article series here. In this part, I discussed why one might want to partition multidimensional data, overview of SQL Server partitioning architecture, and guidelines for partitioning relational and multidimensional data.

This article is published on SSWUG.org.