SQL Server 2 method to start hardware acceleration (partitioning) for an index

Background knowledge:

If you want to see the "Three Kingdoms" This TV show it has assumed that it is 400G so big, now you have two friends they have saved the play on their hard drive.

A with a hard drive to save the play, B with two hard disk to save a bit, if you do not pursue the speed of replication, a hard drive will be more convenient, but

is if you are chasing speed 2 hard drives faster (assuming the parameters of these three drives are the same). This allows the IO capability of two hard disks to be used at the same time. I'm picking up.

is how to use the IO capability of multiple hard drives.

Method 1, working with filegroups

Save the data and index on a different hard disk. To improve IO capabilities.

Resolved using the specified filegroup. Here to use some of the file and file group knowledge can read my article http://www.cnblogs.com/JiangLe/p/4005904.html

Resolves the issue in one step and specifies the filegroup when the index is created.

CREATE INDEX index_name on table_name (columnlist) on [FileGroupName];

Create INDEX ix_nums_x on Nums (X) on [FG2];

Method 2,

Using partitioning schemes This approach is much more specific than using filegroups.

CREATE INDEX index_name on table_name (cloumnname) on Shemename (Clomnsname);

SQL Server 2 method to start hardware acceleration (partitioning) for an index