While getting ready for the PASS Community Summit in Orlando this week (where I plan to talk about SQL Server 2005 Partitioned Tables/Indexes), I realized we were close but not quite ready to release the post-beta II whitepaper on MSDN.
So, in preparation for PASS we decided to post a pre-release of the partitioning paper here.
Enjoy!
See you in Orlando… eventually?!
One thought on “SQL Server 2005 Partitioned Tables and Indexes”
Hi,
Thanks a lot for the article. I have a question about mapping partitions to filegroups. On the following page in the Beta2 BOL,
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/24a8016b-f9ea-48a2-9e7c-bc861fbe34cd.htm, it seems to not recommanding that. Could you comment on that.
Thanks,
Wenbin Zhang
Quotes from Beta2 BOL:
"It may be tempting to map your partitions to filegroups, each accessing a different physical disk drive, simply in order to improve I/O performance. When SQL Server performs data sorting for I/O operations, it sorts the data first by partition. Under this scenario, therefore, SQL Server accesses one drive at a time, which may lower performance. A better solution, in terms of performance, is to stripe the data files of your partitions across more than one disk by setting up a RAID. This way, although SQL Server still sorts data by partition, it can access all the drives of each partition simultaneously."