"al" <ac*****@yahoo.com> wrote in message
news:a4*************************@posting.google.co m...
I had a problem with the transaction log size resently, where the log
would grow >5GB in 3 weeks and SQL would crush. I created a dump log
job that runs on weekends, and dumps the log. Is this a good practice,
what kind of problem I can ran into, size of DB-40mb. SQL 2000 sp3
It depends on several factors, but in general you should start by deciding
how and when you might need to recover the database. Assuming that you want
to be able to recover to a point in time, using transaction log backups,
then a typical starting point might be a full backup every night, and log
backups once an hour during the day.
It all depends on your requirements for recovery, however. If you can afford
to lose a full day's data, then you could just put the database in simple
recovery mode and do a full backup every night. You should probably read up
on recovery models in Books Online, and then decide which approach is best
for your requirements.
Simon
