The idea behind this article is to discuss the importance and the implication of SQL Partition and understand the truncate command partitioning enhancements in SQL 2016
One of the biggest challenges for a DBA is to identify the right candidate for table partitioning, as it requires expertise in design and implementation.
The following are the various truncating options available in SQL 2016
- Truncate individual partitions
- Truncate multiple individual partitions
- Truncate a Range of partitions
- Truncate a Range with multiple individual partitions
- Define the importance and the implication of SQL table partitioning
- Identify the right candidate for table partitioning
- Provide inline comparison of features available in the different editions of SQL 2016
- Discuss the truncate partition enhancements in SQL 2016
- Demonstrate the truncate table partition use cases
Let’s understand the objective of SQL partitioning, why we need partitioning and the factors that are vital to deciding on a Table Partitioning Strategy.
Partitions are a logical mapping of the physical data. A well-designed partition gives us an option to scale out the data. It optimizes the performance and simplifies the management of data by partitioning each table into multiple separate partitions. Although, not all tables are good candidates for partitioning. If the answer is ‘yes’ to all or most of the following questions, table partitioning may be a viable database design strategy; if the answer is ‘no’ to most of the following questions, table partitioning may not be the right solution for that table.