Hi,

I've got an architectual question about archiving data and I was wondering if anybody from the LLBLGen community had done that before and how that was implemented.

What I'm trying to accomplish is creating a subset database which contains the necessary tables that need to be archived (like transactions, documents, logs, etc) and they share the exact same schema as the original tables so data can easily be transferred from production to archive.

But how can one use these archive tables in the exact same LLBLGen-manner (query-wise) as some vital referential data is not available in the archive database. E.g. an Orders table is in the archive database, but the Clients table is not. What I don't want is replicating referential data to the archive database as well, so I would like to be able to join the archive Orders table to the production Clients table in a seamless way.

Am I making sense ? I know that you can add an extra schema to your solution where you can map the archive tables, but you then would have to use different Entity names for the archive tables which also means you have to create new queries (fields/predicates) to fetch data from these tables.

Anybody got ideas about a situation like this ? thanks in advance !

grtz, Danny

I'd say you should archive the clients table too, and any table you need tolink too from the archived data.

Yes, sure....but then I would have to maintain (replicate to) this table as well in the archive database and all of its related tables to make everything work.

Perhaps (and it looks like it) is that the only way to get this on the road, but I was hoping for someone to come up with a real smart idea..... as the LLBLGen community is by nature...!

Thanks for your answer btw !

grtz, Danny