My company has provided me only with SQL Server 2005 Enterprise Edition and I have some tables with large amounts of data Wanted to split. I have around 5 or 6 tables which would be a good fit to divide by date time.
Some questions will require 2 of these tables during the same question.
I was thinking that I should use the same split plan for all the tables, or if I should copy the partition plan and put separate tables on each one.
Thanks for any help in advance.
You should define your partition which is understandable for your domain. That is, if you work mainly in the quarters of the year, then create 5 divisions (4 quarters + 1 overpill).
You should also take physical file placement in the account. From the MSDN article:
The first step in the partition table and index is to define the data on which the partition has been closed. In the table, the partition key should be present in the form of a single column and some criteria must be met. The partition function defines the data type on which the key (also known as logical partitions of data) is based. The function defines this key but there is no physical location of data on the disk. The placement of data is determined by the partition plan. In other words, this plan maps data to one or more file groups, which map specific files (files) and hence the disk. This plan always uses a function to do so: If the function defines five partitions , The plan should use five file groups. File groups do not need to be different; However, if you have many disks and will get better performance better, preferably, multiple CPUs when the scheme is used with a table, you will define the column that is used as a logic for the partitioning function is done.
These two articles can be useful:
Comments
Post a Comment