Controlling size of database log

Hi,
Our production database log size (9 GB) is 3 times greater than size of the
actual database itself (3GB)!
Is it normal? If not how can I bring the log size down? Can someone let me
know please.
Thanks in advance,
Harish Mohanbabuback it up.
BACKUP LOG databaseName
you can even back it up just to truncate it.
BACKUP LOG databaseName WITH TRUNCATE_ONLY
Greg Jackson
PDX, Oregon|||In addition to pdxjaxon,
you can run DBCC Shrinkfile, to reduce the physical log file size to the
desired target size.
--
Thanks
Yogish
"pdxJaxon" wrote:
> back it up.
> BACKUP LOG databaseName
>
> you can even back it up just to truncate it.
> BACKUP LOG databaseName WITH TRUNCATE_ONLY
>
> Greg Jackson
> PDX, Oregon
>
>|||And also check the recovery model for the database.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Yogish" <yogishkamathg@.icqmail.com> wrote in message
news:DDB0D749-6F74-4673-993E-A5767020BFD6@.microsoft.com...
> In addition to pdxjaxon,
> you can run DBCC Shrinkfile, to reduce the physical log file size to the
> desired target size.
> --
> Thanks
> Yogish
> "pdxJaxon" wrote:
>> back it up.
>> BACKUP LOG databaseName
>>
>> you can even back it up just to truncate it.
>> BACKUP LOG databaseName WITH TRUNCATE_ONLY
>>
>> Greg Jackson
>> PDX, Oregon
>>