> I've seen you suggest this before (logging to another device), can you explain why and specifically how I would go about doing this now that I am up an running and don't want to screw anything up.
When SQL Server does a transaction or command, it creates
a log of it. This log is used to back out if a problem
occurs, to allow for recovery, etc.
The default install of Emerald is for the log to be
on the same device as the Emerald database itself.
In this setup your database can become fragmented because
the log will be all around the data. Because of this
you can not truncate the log without dumping the whole
If the log is on its own device, you can truncate just the
log. Putting the log on its own device is pretty easy:
1) Start Enterprise manager and connect.
2) Expand the list to the database devices, righ click
over one, and select new database device.
3) Name the Device Emerlog, size 25mb, and create it.
4) Expand the Database list, and double click the Emerald
database. When the three tabs come up, click on the
5) Expand JUST the log onto the new Database device. Do this
by selecting the new Device (Emerlog) and size 25mb.
6) After Selecting OK, you can re-edit the database, and see
that you have more space free because it moved the log over
to the new device.