There was a request from whomever oversees the enhancement/enlargement of
this limit, but I can't find that thread now to reply, so am starting a new
one.

Having recently bumped into this after adding 200+ users with our latest
aquisition, I've had to disable logging on one database, and will need to
disable logging on a second database before our busy season.

We've used the log files 3 times in 3 years, The first time was due to a
system crash due to a disc failure.  It worked wonderfully and saved 200
people from re-keying about 7 hours worth of data, interestingly enough
(luckily) we had implemented logging only about 3 months prior.  As a
result of that crash we implemented Mirror iX.

The second time, was to rebuild several thousand entries into a multiple
sets which had been deleted inadvertantly (by an errant program(mer).  For
this, we wrote a q&d to read and sift the log files, which gave us a nice
utility in case we need it again.

The third was to recover from a DBG DISABLED error on a master set.  The
corruption wasn't discovered until a couple of days later, and the solution
to Replace the Master using Adager and do a path fix on the 7 details (one
having over 10 million records) couldn't be done timely enough, so we
restored the DB root and dataset file from backups until we reached the
point where examine path turned up clean, and then restored the entire DB
and applied all log files going forward.

My point is that Image Logging is more than an unused security blanket, it
has bailed us out a couple of times, even though we have mirrored disks.

I will be able to log my most critical DB's through this season, but
possibly not next, which is why I'm looking for a work around.  I hope to
implement Quest's product and begin shadowing (budget allowing) before next
season, and then we can log the shadow box.

My SR to have it increased is 500345121

Steve Weber
[log in to unmask]