On Fri, 11 Aug 2006, Dominic Marks wrote: > I understand that dbcheck on a big database with millons and millions > or rows like mine is going to take a long time. However, having the > database locked for days on end is not really workable.
See my posting from yesterday. I have approx 100 million entries in the database and processing was completed in a few hours once indexes were done. > So I thought I would start a discussion on possible workaround methods: > 1. Per Client/Job Catalogues No need. Appropriate indexing takes care of it, along with saner delete statements. AB ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
