469,962 Members | 2,184 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,962 developers. It's quick & easy.

Db2 mirror tables

Hi.

I need to mirror a set of my database data, that is create a database
which acts as a buffer in front of the real one.
We have in our DB2 database data which has been created over the last
100 years or so, and is obviously huge amount of data. All normal
operation is done though on data which has been created over the last
30 days or so.

Is it possible to create database which only holds data created over
the last 30 days. Further more all inserts, updates and deletes should
affect both the huge database and also the small one. Any suggestions
would be greatly appriciated.

Jun 27 '06 #1
2 2820
Sprellari wrote:
Hi.

I need to mirror a set of my database data, that is create a database
which acts as a buffer in front of the real one.
We have in our DB2 database data which has been created over the last
100 years or so, and is obviously huge amount of data. All normal
operation is done though on data which has been created over the last
30 days or so.

Is it possible to create database which only holds data created over
the last 30 days. Further more all inserts, updates and deletes should
affect both the huge database and also the small one. Any suggestions
would be greatly appriciated.

Well ... this is not what I would call a mirror. Best way to accommodate
this is to do it within your design schema and your application, IMHO.
There are many other questions, though, that must go into this. For
example, how much data is involved in each? Does the "historical" data
ever need to be accessed after it is inserted to? Does it ever need to
be joined with the "30-day" data?

Larry Edelstein
Jun 27 '06 #2
Ian
Sprellari wrote:
Hi.

I need to mirror a set of my database data, that is create a database
which acts as a buffer in front of the real one.
We have in our DB2 database data which has been created over the last
100 years or so, and is obviously huge amount of data. All normal
operation is done though on data which has been created over the last
30 days or so.

Is it possible to create database which only holds data created over
the last 30 days. Further more all inserts, updates and deletes should
affect both the huge database and also the small one. Any suggestions
would be greatly appriciated.

It *might* be possible to do this using an MQT, although I think there
is probably a better solution:

You could look in to using multi-dimensional clustering (MDC), or (even
better), look into range partitioning that's available in DB2 9.
Jun 27 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

5 posts views Thread by Andrew James | last post: by
reply views Thread by barbaros | last post: by
1 post views Thread by hikums | last post: by
3 posts views Thread by Dzemo | last post: by
reply views Thread by virtualadepts | last post: by
reply views Thread by CoreyWhite | last post: by
4 posts views Thread by Mark A | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.