SQL Server Partitioning, best practices for creating partition scheme's and functions

Question

I'm implementing Partitioning for the first time in SQL Server 2008r2. I've several large tables that I am partitioning.

My main question is should I use the same Partition Scheme and Function for all these tables, or should I create multiple Partition Scheme's and Functions?

When I move older data to an different file group will having separate Scheme's and Functions make moving the data easier?

And what are some things that should consider when making this decision?

consider posting your question to serverfault's sister site for database-related stuff http://dba.stackexchange.com — the-wabbit, Jan 05 '12 at 22:38
Thanks, I have posted it there at: http://dba.stackexchange.com/questions/1023 — David Youngberg, Jan 05 '12 at 23:09
You probably mistyped your link - it should be http://dba.stackexchange.com/questions/10239 — the-wabbit, Jan 05 '12 at 23:37

score 0 · Answer 1 · answered Jan 06 '12 at 00:34

0

If you have a single schema and function and you alter that to move data around all the tables will be moved in a single shot instead of having to change all of them.

answered Jan 06 '12 at 00:34

mrdenny

27,074
4
40
68

SQL Server Partitioning, best practices for creating partition scheme's and functions

1 Answers1