1) What is contained in the Emerald Log to make it so large?
2) Is there anything we can do other than clearing the transaction log to
reduce its size?
3) What symptoms would one experience on a server where the Emerald
database was reaching its maximum size? After recovering the database, it
appears that it had actually exceeded its maximum size by 2 MB. Our
machine with SQL server has been spontaneously rebooting over the last
week, and I am wondering if there is a connection.
Direct NET Communications