Hi, > The specific need is: to capture the complete and orded list of > transactions (DML & DDL) that a frontend db has commited between two > specific points in time ( Check Points) in a portable format of retained > transaction log fragment. That can be SQL batch script or any other > replay-able form.
I would like to understand what is the problem you want to solve. It's always interesting to know how you would solve the problem, but for me it's more important to know the problem currently. Maybe there are other ways to solve it. Example (I just made that up): "I write a web-based backup application that backs up all files to the internet. A competitor to 'Dropbox'. To do that, I want to use Amazon EC2 instances, and plan to use H2 to store the backup meta data. The meta data needs to be 100% fail safe, so I plan to implement some sort of clustering so data is not stored just in one place but in at least two places, not only on Amazon but also on my own server." > The use case is any scenario where it's needed to efficiently capture > some workload with the purpose of: > - propagate to others databases > - Incremental backup implementation (checkpoint with full backup + > transaction log retention // restore full backup + transaction log replay ) > - audit or stats workload That's still quite abstract. H2 already supports "clustering". From your description I don't know why you can't use that, or what features are missing. An alternative is a replicating file system implementation that stores all changes not just in the local files but also sends the changes to a remote system. But first I would like to know the concrete use case. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
