Makes sense.
Too bad you can't do
CREATE TABLE ROB/MYREALLYBIGTABLENAME
(MYBIGHONKINGCOLUMN CHAR (5 ),
SOMENUMBER INT)
PARTITION BY RANGE
(SOMENUMBER)
(PARTITION BIGTABLE
STARTING FROM 1 INCLUSIVE
ENDING AT 9999999 INCLUSIVE)
without having DB2 Multisystem installed and functioning. That would have
named the member BIGTABLE.
I can see requiring DB2 Multisystem if you were doing stuff like
partitioning by state and storing each state partition (aka member) on a
server in that state. But I'm not! However I don't see a way to declare
which system to store where in this SQL statement so I reckon that it
can't tell whether or not you're single system or multiple system unless
that's installed to tell you so.
There just has to be some sort of work around.
Since they have a workaround by requiring DB2 Multisystem, do you think
there's a chance of getting a requirement passed to specify a member name
like we can with RCDFMT for record format?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.