You can partition on a composite key. Pick another column or two and place it after TBL_ID. You should pick columns that are frequently used in a join, in my experience to facilitate co-located joins (i.e. joining two partitioned tables node by node).

Hal

-----Original Message-----
From: Grace <db2udbdba-ezmlmshield-x11864458.[Email address protected]
To: LazyDBA Discussion <[Email address protected]
Sent: Thu, 23 Mar 2006 10:12:31 -0500
Subject: Re: DB2 Partitioning question


This is not a good candidate column for partitioning. Columns with unevenly
distributed data, and columns with a small number of
distinct values should not be chosen as a partitioning key. The number of
distinct values must be great enough to ensure an even distribution of
rows across all database partitions in the database partition group.

DB2 Viper provides range partitioning, but it really depends on your data
distribution and the nature of your applications.

Hope it helps.






"Ramon Santiago "
<db2udbdba-ezmlmshield-x15087375.[Email address protected]
03/23/2006 10:07 AM


To: "LazyDBA Discussion" <[Email address protected]
cc:
Subject: DB2 Partitioning question



How do I code the DDL to partition on a field (TBL_ID) containing two
different IDs such as "H3" and "TS"?




---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html





---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html

DB2 & UDB email list listserv db2-l LazyDBA home page