Inserting across different Partitions within a Partitioned Table

All we need is an easy explanation of the problem, so here it is.

A general question surrounding Table Partionining. If you’re partitioning a table on a Date column with the RANGE being a 12 month period for each.

If you’re inserting into prior partition periods, would you expect performance to be slower compared to inserting to the current partition?

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Physically each partition is stored a separate data structure, and only the Query Optimizer knows that they make up one logical table.

So you shouldn’t expect a significant difference in inserting into one partition or another.

If your table is a clustered index it can be more expensive to insert into the "middle" than the "end", but that’s mostly unrelated to whether the clustered index is partitioned.

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply