November 6, 2008 at 8:29 am
I am trying to implement table partitioning in a new design. The database will grow very quickly once it goes live. The table will contain records from several different companies. In many of the tables, I have an identity column as the primary key. The problem I am running into is that the column I want to partition on is the company id and not the identity column. I want to partition on the company id because all work will be performed on a per company basis and never span across multiple companies in the same query.. From what I know about table partitioning, this should help speed things up once the database gets large. I could make the company id part of the primary key so I can partition the table but does that introduce any potential problems? Is there a better way to partition the tables?
January 11, 2011 at 4:05 am
Your case looks like list partitioning.
http://msdn.microsoft.com/en-us/library/ms345146%28SQL.90%29.aspx#sql2k5parti_topic25
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply