RE: [Emerald] SQL 6.5

John Roman ( jroman@toua.net )
Thu, 20 May 1999 04:56:35 -0700

The problem was that when the database was setup it was configured to
have the database and the log file write to the same hdd space so when
the log file filled up it took the master database with it. I had to
manually dump the log file using SQL from the command prompt.

-----Original Message-----
From: david leigh [mailto:vorlon@arach.net.au]
Sent: Wednesday, May 19, 1999 4:49 PM
To: emerald@iea-software.com
Subject: Re: [Emerald] SQL 6.5

Did you learn anything which might be worthwhile for the rest of us to
know?
Ie was the problem with your database what Microsoft considered to be a
common one?

Cheers
David Leigh

-----Original Message-----
From: John Roman <jroman@toua.net>
To: emerald@iea-software.com <emerald@iea-software.com>
Date: Thursday, May 20, 1999 4:52 AM
Subject: RE: [Emerald] SQL 6.5

>Actually rebooting the machine is what caused SQL to die in the first
>place.
>I just got off the phone with microsoft tech support at $195 and they
>helped me repair the master database which had gotten damaged.
>Thanks for everyones suggestions though.