Re: AW: Building a logical file with 1 member over a physical file withmanymembers -- MIDRANGE-L

Subject: Re: AW: Building a logical file with 1 member over a physical file withmanymembers
From: rob@xxxxxxxxx
Date: Mon, 17 Sep 2007 09:34:32 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Just now. I understand that partitioned tables are recommended only for
particular solutions. One to get around file size limitations. Two for
bulk data operations like this example of dropping a whole years data or
plants data.

I also understand there are numerous limitations, like no referential
constraints. So truly I would only recommend it for historical records.

I also understand there are performance hits for querying the data.

I also understand that external keys on the data will probably need to be
rebuild if one does do a RMVM.

And so on and so forth.

So why limit this to only those systems that have DB2 Multi System?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: AW: Building a logical file with 1 member over a physical file withmanymembers , CRPence

This mailing list archive is Copyright 1997-2025 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.