"Daniel" wrote:

> Is there any suggestions on what we can do to help prevent our logs from
> getting out of hand...
>
> Maybe a purge process or settings to keep only certain amount of data before
> it starts overwriting...
>
> Current settings:
>
> Initial Size: 21991MB
> Enable AutoGrowth is checked
> File Growth: 40%
> Maximum File Size: 2,097,152
>
> Current Size: 22,518,272
>
> Question we have is if we turn off the autogrowth and leave the current
> settings, what happens when the logs reach the maximum size?
>
> --
> ASP, SQL2005, DW8 VBScript
>
>
>

"Ben Nevarez" <BenNeva***@discussions.microsoft.com> wrote in message
news:3C166AB1-3029-4674-8F76-0EC9BC5CA4FC@microsoft.com...
>
> Hi Daniel,
>
> Just schedule transaction log backups (minimum daily).
>
> You can also change the recovery model to SIMPLE but need to see the
> documentation (BOL) to understand better the prons and cons.
>
> After doing the transaction log backup you can manually shrink the
> transaction log (but do not schedule maintenance plans to shrink it
> periodically).
>
> Hope this helps,
>
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
>
>
> "Daniel" wrote:
>
>> Is there any suggestions on what we can do to help prevent our logs from
>> getting out of hand...
>>
>> Maybe a purge process or settings to keep only certain amount of data
>> before
>> it starts overwriting...
>>
>> Current settings:
>>
>> Initial Size: 21991MB
>> Enable AutoGrowth is checked
>> File Growth: 40%
>> Maximum File Size: 2,097,152
>>
>> Current Size: 22,518,272
>>
>> Question we have is if we turn off the autogrowth and leave the current
>> settings, what happens when the logs reach the maximum size?
>>
>> --
>> ASP, SQL2005, DW8 VBScript
>>
>>
>>