Log file size

Hi there,
I have a SQL Server 2000 database running on a Windows 2000 Server. The data
file is about 1GB large. The size of the log file is allways about 2GB. When
it reaches this size, I run 'BACKUP LOG <database> WITH TRUNCATE_ONLY' to
empty the file. Then, the file keeps growing again until 2GB.
My question is, it is normal that the log file grows like this way?
I can also tell that there is an application that runs over the database,
and it's installed in 10/15 workstations. There are allways 8/9+
workstations working.
I would appreciate any commentary...
Regards..
Marco Pais> My question is, it is normal that the log file grows like this way?
Well, what is your recovery model? If you don't backup your database then
the log will continue to grow until you either backup the database or backup
the log. If you are not bothering to backup your database then switch to
simple recovery model and the effect on the log won't be so great (but of
course your recovery options become more limited).
In our environment, we leave enough room for the log files to grow as they
need to. If you are fretting over 1 GB now what's going to happen when you
have a real data store.
A|||Hello Aaron,
First of all, thanks for the answer.
The database is backuped once a day, every days of week.
Can the log file growing be caused by something else? Can it affect
performance?
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ea7ka03PFHA.1388@.TK2MSFTNGP09.phx.gbl...
> Well, what is your recovery model? If you don't backup your database then
> the log will continue to grow until you either backup the database or
> backup the log. If you are not bothering to backup your database then
> switch to simple recovery model and the effect on the log won't be so
> great (but of course your recovery options become more limited).
> In our environment, we leave enough room for the log files to grow as they
> need to. If you are fretting over 1 GB now what's going to happen when
> you have a real data store.
> A
>|||Apart from long running transactions in the application or badly configured
replication the most common cause of T-log becoming excessive is the
optimization job. This will make copies of existing data while rebuilding
and if you have particularly large tables this will cause a long running
transaction.
Providing the used part of the log stays reasonable small (say <100MB)
during your busy times you should not suffer performance degredation.
Regards,
Tim G-J
Professional Database Solutions Ltd.
www.pdbsolutions.co.uk
"Marco Pais" wrote:

> Hello Aaron,
> First of all, thanks for the answer.
> The database is backuped once a day, every days of week.
> Can the log file growing be caused by something else? Can it affect
> performance?
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ea7ka03PFHA.1388@.TK2MSFTNGP09.phx.gbl...
>
>