partitioning table @ sql server 2000

Question

partitioning table @ sql server 2000

muntasiriub

SSCommitted

Points: 1810
More actions
July 5, 2004 at 2:20 am

#108262

Can any one help me
on partitioning table @ sql server 2000.
I knew that oracle support partitioning table as follows:

CREATE TABLE My_table
(
Id varchar(15) not null,
…….
SavingBalace number(12,3) Default 0 not null
…
)
partition by Ranage(Saving_Balance)
(
partition BR_Save_part1 Values Less Than (50000) Tablespace ts_cb_1,
partition BR_Save_part2 Values Less Than (100000) Tablespace ts_cb_2,
partition BR_Save_part3 Values Less Than (150000) Tablespace ts_cb_3,
partition BR_Save_part4 Values Less Than (MAXVALUE) Tablespace ts_cb_4
)
Enable ROW MOVEMENT
;

Is it possible for sql server 2000?

..Better Than Before...

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

Daljit S. Saini SSC Enthusiast Points: 189 More actions · Answer 1

You design the member tables so that each table stores a horizontal slice of the original table based on a range of key values. The ranges are based on the data values in a partitioning column. The range of values in each member table is enforced by a CHECK constraint on the partitioning column, and ranges cannot overlap. For example, you cannot have one table with a range from 1 through 200000, and another with a range from 150000 through 300000 because it would not be clear which table contains the values from 150000 through 200000.

For example, you are partitioning a Customer table into three tables. The CHECK constraint for these tables is:

-- On Server1:CREATE TABLE Customer_33  (CustomerID   INTEGER PRIMARY KEY                CHECK (CustomerID BETWEEN 1 AND 32999),  ... -- Additional column definitions)-- On Server2:CREATE TABLE Customer_66  (CustomerID   INTEGER PRIMARY KEY                CHECK (CustomerID BETWEEN 33000 AND 65999),  ... -- Additional column definitions)-- On Server3:CREATE TABLE Customer_99  (CustomerID   INTEGER PRIMARY KEY                CHECK (CustomerID BETWEEN 66000 AND 99999),  ... -- Additional column definitions)

After this Create this distributed partitioned view: CREATE VIEW Customers AS   SELECT * FROM CompanyDatabase.TableOwner.Customers_33UNION ALL   SELECT * FROM Server2.CompanyDatabase.TableOwner.Customers_66UNION ALL   SELECT * FROM Server3.CompanyDatabase.TableOwner.Customers_99

muntasiriub SSCommitted Points: 1810 More actions · Answer 2

hi Daljit S. Saini,

Then it seems to be hazy...

Because, What would be my insert,delete,modify statement...

i have to check the range of my data every time before insert,delete,modify statement?

..Better Than Before...