SQL SERVER – White Paper – Partitioned Table and Index Strategies Using SQL Server 2008

Partitioned Table and Index Strategies Using SQL Server 2008
Writer: Ron Talmage, Solid Quality Mentors
Technical Reviewer: Denny Lee, Wey Guy, Kevin Cox, Lubor Kollar, Susan Price – Microsoft
Greg Low, Herbert Albert – Solid Quality Mentors

When a database table grows in size to the hundreds of gigabytes or more, it can become more difficult to load new data, remove old data, and maintain indexes. Just the sheer size of the table causes such operations to take much longer. Even the data that must be loaded or removed can be very sizable, making INSERT and DELETE operations on the table impractical. The Microsoft SQL Server 2008 database software provides table partitioning to make such operations more manageable.

Partitioning a large table divides the table and its indexes into smaller partitions, so that maintenance operations can be applied on a partition-by-partition basis, rather than on the entire table. In addition, the SQL Server optimizer can direct properly filtered queries to appropriate partitions rather than the entire table.

This paper covers strategies and best practices for using partitioned tables and indexes in SQL Server 2008. It is intended for database architects, developers, and administrators of both data warehouse and OLTP systems, and the material is presented at an intermediate to advanced level.

Download “Partitioned Table and Index Strategies Using SQL Server 2008″ white paper

Abstract courtesy : Microsoft

Reference: Pinal Dave (http://blog.SQLAuthority.com)

About these ads

6 thoughts on “SQL SERVER – White Paper – Partitioned Table and Index Strategies Using SQL Server 2008

  1. I have a huge table with millions records and have problem for retrieve data from it.I Partitioned table by integer column and create a clustered index on this column on partition scheme and use it in my query but i have no change.please help me

    Like

      • no,but i have to join my table to itself to select correct data . let me explain:
        table Example:
        OrderNumber OrderElement
        1 0
        1 1
        1 2
        2 0
        3 0
        3 1
        I don’t want to see fourth record in my select. so i wrote:
        select * from Example as E inner join Example az E_elemnt on
        E.ordernumber = E_element.ordernumber and
        E_element.orderelement > 0

        Like

  2. no,but i have to join my table to itself to select correct data . let me explain:
    table Example:
    OrderNumber OrderElement
    1 0
    1 1
    1 2
    2 0
    3 0
    3 1
    I don’t want to see fourth record in my select. so i wrote:
    select * from Example as E inner join Example az E_elemnt on
    E.ordernumber = E_element.ordernumber and
    E_element.orderelement > 0

    Like

  3. Pingback: SQL SERVER – Advantages of Partitioning – Quiz – Puzzle – 30 of 31 « SQL Server Journey with SQL Authority

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s