The database that I just started to work with has a simple recovery model.
The actual production database is 5 gigs while the transaction log table is
98 gigs. I can not figure out how the transaction log became so large. There
has never been a backup taken of the transaction log. How can the transaction
log keep growing if the transaction log is never used by the recovery model?

Thanks!

Wendy;

I ran into a similar problem a while back, what ended up causing it was a
maintenance plan that ran and the server ran out of disk space as the maint
plan was running. It made my DB unaccesible and it left the t-log file very
large because backing it up was part of the maint plan. I simply deleted the
t-log file and let SQL create a new one. Just like you I didn't have a recent
backup of the t-log file so this was my only option, and it all worked out
okay.

I hope this was helpful.

Bryan

"Wendy Elizabeth" wrote:

> The database that I just started to work with has a simple recovery model.
> The actual production database is 5 gigs while the transaction log table is
> 98 gigs. I can not figure out how the transaction log became so large. There
> has never been a backup taken of the transaction log. How can the transaction
> log keep growing if the transaction log is never used by the recovery model?
>
> Thanks!
>