February 21, 2013 at 3:28 am
Create table Table1 (ID INT P.K, OrderDate Date))
1. The table has clustered index on ID.
Afterwards we have partitioned the table based on OrderDate. What it will do is the specified rage data keep in mentioned FG.
Is there any difference in partioned / non-partitioned tables Clustered index architecture.
🙂
February 21, 2013 at 3:34 am
from BOL
Although partitioned indexes can be implemented independently from their base tables, it generally makes sense to design a partitioned table and then create an index on the table. When you do this, SQL Server automatically partitions the index by using the same partition scheme and partitioning column as the table. As a result, the index is partitioned in essentially the same manner as the table. This makes the index aligned with the table.
SQL Server does not align the index with the table if you specify a different partition scheme or a separate filegroup on which to put the index at creation time.
Aligning an index with a partitioned table is particularly important if you anticipate that it will expand by taking on additional partitions, or that it will be involved in frequent partition switches.
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply