The log has nothing to do with Emerald itself. Everything
that happens in SQL Server creates an entry in the applicable
transaction log. Its designed so that you can back out of
transactions that go bad, or dump the database, and then
several transaction logs, to be able to re-create the database
from the dump and the transaction logs.
Typically, you just do a dump per night and that should be
suffice. Advanced users setup transction log dumps on a spcific
basis so that they can re-create the database and it will be no
more than x hours old.
The transaction log can really grow fast during consolidation,
because it has to log hundreds of thousands transactions (one
for every insert/delete operation).
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com