krupini
asked on
How does SQL Server 2005 know which partition to use?
Most examples for SQL Server 2005 involve a sales table that you split based on date, i.e. sales records prior to 2000 go to this partition, and the ones after that go to another one. Nice and simple.
Say I have a sales table:
id Amount Date
1 10 1/1/1999
2 9.99 1/1/2007
Now then, I put all the records prior to 2000 in it's own partition.
So when I do something like this: SELECT * FROM Sales WHERE DATE = 1/1/1999
the SQL server will know which partition to look at. Very nice.
Now then, if I do this: SELECT * FROM Sales WHERE id = 1
How will the SQL server know which partition to look at?
Thank You!
Say I have a sales table:
id Amount Date
1 10 1/1/1999
2 9.99 1/1/2007
Now then, I put all the records prior to 2000 in it's own partition.
So when I do something like this: SELECT * FROM Sales WHERE DATE = 1/1/1999
the SQL server will know which partition to look at. Very nice.
Now then, if I do this: SELECT * FROM Sales WHERE id = 1
How will the SQL server know which partition to look at?
Thank You!
remeber your partitioning key doesn't have to be unique within the table... and you'll still need a primary key
which is unique for performance / validity reasons.
which is unique for performance / validity reasons.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So from what I understand, if the date is not specified, which is a partition key, the SQL server will look in all partitions, one by one.
Is there any specific order which the SQL server will use to look at partitions? For example, will it look at the most recent partition first (the one for 2000 - Now) records, and if it's not there it will look at (<2000) partition?
Thanks.
Is there any specific order which the SQL server will use to look at partitions? For example, will it look at the most recent partition first (the one for 2000 - Now) records, and if it's not there it will look at (<2000) partition?
Thanks.
It will look in all partitions in parallel, 1 thread per partition. (Unless DOP prevents the parallelism)
Oh no fair, the cookie should so go to lowfat - concidering it is a diet cookie that is
ASKER
drydenhogg explanation was more clear and to the point. I should have split the points, I wish I could edit the decision ....
Eh, he would have needed a low fat one anyway and where is the joy in sugar-free cookies!
so tableA is the only 1 which could contain pre 2000 data...
if you don't specify the partition key in your query each partition/table/view will be searched for rows matching your criteria... it only if a specific partition key criteria is available that only the matching object will be searched...
hth