Marc-Philip, We can't currently take advantage of the Event Dispatcher because we're only running MaxDB 7.5. But assuming it's still in there by the time we upgrade to MaxDB 7.6, we'd love to start using it.
We use HP's Data Protector software to backup our MaxDB databases. (It works great, btw.) We also have AutoLog enabled, so that MaxDB will automatically output to a local filesystem whenever our log area becomes too filled. As it exists for us today, when MaxDB produces such an AutoLog-inspired backup, the version files that get produced just sit in the local filesystem until our regularly-scheduled Data Protector backup comes along to move them to tape. It is hoped that in the future, MaxDB 7.6 would (via the use of the Event Dispatcher) call DP after such an AutoLog-inspired backup, and thus we'd prevent the possibility that our local filesystem would fill up itself. In the event you all decide to drop the Event Dispatcher, that's Ok... I mean, we could always create a little daemon that could periodically monitor this filesystem (and trigger DP accordingly), but we were hopeful that the Event Dispatcher would be able to do that for us. Thanks, ~Fred -----Original Message----- From: Werner, Marc-Philip [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 12:01 PM To: maxdb@lists.mysql.com Subject: Event Dispatcher: any feedback? Hallo Users, with MaxDB version 7.6 we introduced the feature "Event Dispatcher" (pls. check <http://dev.mysql.com/doc/maxdb/en/ab/61fe41af01c417e10000000a155106/fra meset.htm> for documentation). We have basically two questions concerning it: 1. Does it meet your requirements, in other words, can you use it? Which events are the most interesting for you? Are there any situations resp. occurences that should be provided as events to make them dispatchable? 2. We're currently discussing, if we should remove the Event Dispatcher from the client to make the software (and it's installation) less complex and the software download smaller. Is anybody using it on the client (and would be hurt by the removal)? Before you might ask: For the time being, I'm afraid, it's not planned to have something like "user defined events", that you can make the kernel fire by calling some SQL statement. T&R, Marc-Philip SAP Labs Berlin -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
