Partitioning allows you to manage large amounts of data much easier to split into small pieces of physical disk. The intention is that the activity of I/O.
Adopted reduce, you have a table with 10 million rows and want to read a million lines in which to submit an analytical report. If the table is divided into 10 divisions, and contain a million rows in a partition is, then say to one million lines in front of 10 million lines. This scale can be very serious in a difference of E / S from a single report.
SQL Server 2005 allows the partition table and partitions of the index. This means that you create a table as a partition table, especially if each is physically part of the table or index.
SQL Server 2000 manually particular partition partition with multiple tables, in addition to SQL Server. Keep an eye (partition order) was to overlay the tables from the server created. In other words, an application, access to a profile with a query, no data. SQL Server 2005 contains the lines of the real physical partition table.
Physically have partition tables and indexes a number of benefits:
- Data can be read in a time of one partition, greatly reducing power bow I / O
- Data can be accessed from multiple partitions in parallel, which makes things twice the speed, depending on how many do you have a processor server platform.
- Different partitions separately, without the entire table will be maintained
Post a Comment