Mike,
Shall we assume the relationship is one-to-many from parent to child? What
kind of application is this; transactional or reporting?
Andy Hauger
-----Original Message-----
From: ERWin-DB-Modeling@xxxxxxxxxxxxxxx
[mailto:ERWin-DB-Modeling@xxxxxxxxxxxxxxx]
Sent: Wednesday, March 19, 2003 4:21 AM
To: ERWin-DB-Modeling@xxxxxxxxxxxxxxx
Subject: [ERWin-DB-Modeling] Digest Number 50
To subscribe, send an email to:
ERWin-DB-Modeling-subscribe@xxxxxxxxxxxxxxx
To unsubscribe, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
Archives: http://groups.yahoo.com/group/ERWin-DB-Modeling/messages
------------------------------------------------------------------------
There is 1 message in this issue.
Topics in this digest:
1. designing partition keys
From: "Mike Ryder" <mike.ryder@xxxxxxxxxxx>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 18 Mar 2003 23:35:36 -0000
From: "Mike Ryder" <mike.ryder@xxxxxxxxxxx>
Subject: designing partition keys
Has anyone come across any ideas on strategies for incorporating
physical partition key columns into a data model?
The situation I refer to is thus: Due to large volumes of data there
is a desire to physically partition tables based on some date, making
it far more efficient to purge old data. The tricky part is that the
purge date column is currently held in the parent table and not the
child tables.
Obviously we can cascade delete the parent - but that will be very
inefficient at the cild level as these tables would not be partitioned
based on that date.
To make the design efficient wuld require the same date column used
for purging to be added to each of the child tables.
It offends me to store functonal data merely for physical performance
reasons and even worse - to store it redundantly all over the place.
Anyone have ideas on how this might be addressed without throwing good
data modelling practises out the window?
btw the DBMS is Oracle 8i, and the tables in question are up to 8GB
(not sure of the row counts).
Thanks
Mike Ryder
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/xaxhjB/hdqFAA/xGHJAA/VzvwlB/TM
---------------------------------------------------------------------~->
To subscribe, send an email to:
ERWin-DB-Modeling-subscribe@xxxxxxxxxxxxxxx
To unsubscribe, send an email to:
ERWin-DB-Modeling-unsubscribe@xxxxxxxxxxxxxxx
Archives: http://groups.yahoo.com/group/ERWin-DB-Modeling/messages
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
