This is one of many reasons to do all reading and writing to the database by using subroutines built on the database.
-----Original Message----- From: Hona, David S [mailto:[EMAIL PROTECTED] Sent: Thursday, July 05, 2007 8:49 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? If you want incomplete updates in your database backup, then continue without pausing your database updates... :) Since BASIC applications don't timeout in database read/write operations, it's not really an issue. As for being a 'feature' it is sort of like the scenairo you get with a record update lock contention issue, except with no clause to handle the 'pause'.. Therefore you application would just wait until it's update is serviced...external applications using APIs are a different kettle of fish. So the 'feature' bit being it's transparent to your application. It is what you want with legacy applications of all sorts of vintage. Regards David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Friday, July 06, 2007 10:41 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? Stephen: Is this kind of bogus or kind of a feature. Considering all the different ways connections can be made to the dbms, all kinds of software would/could be failing if backups are done during a "dbpause" timeframe. :-( So it really does mean backups have to be very complex with RAID configurations and implementations. Bill ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
