Prev: Version Control of Database
Next: Question about MS newsgroups posting
From: Bob McClellan on 15 Feb 2010 15:42
Is there a general consensus on what the best practice is for
setting up a job to keep the log file as small as it can be?

thanks in advance,
bob.
From: Jay on 15 Feb 2010 15:55
This is pretty much it.

http://www.karaszi.com/sqlserver/info_dont_shrink.asp

The summary basically is: back up your logs regularly and all will be fine.

I will say that you probably need a bigger file than many think they do.
Things in nightly maintenance generate more log records than most realize.

"Bob McClellan" <bobmcc777(a)gmail.com> wrote in message
news:D49BE0B7-F6E9-4C08-BC70-F8C581310AF2(a)microsoft.com...
> Is there a general consensus on what the best practice is for
> setting up a job to keep the log file as small as it can be?
>
> thanks in advance,
> bob.


From: Bob McClellan on 15 Feb 2010 16:07
Heading there now. Thanks for the quick reply Jay.
I appreciate it.
...bob

"Jay" <spam(a)nospam.org> wrote in message
news:eCEMrEorKHA.1352(a)TK2MSFTNGP06.phx.gbl...
> This is pretty much it.
>
> http://www.karaszi.com/sqlserver/info_dont_shrink.asp
>
> The summary basically is: back up your logs regularly and all will be
> fine.
>
> I will say that you probably need a bigger file than many think they do.
> Things in nightly maintenance generate more log records than most realize.
>
> "Bob McClellan" <bobmcc777(a)gmail.com> wrote in message
> news:D49BE0B7-F6E9-4C08-BC70-F8C581310AF2(a)microsoft.com...
>> Is there a general consensus on what the best practice is for
>> setting up a job to keep the log file as small as it can be?
>>
>> thanks in advance,
>> bob.
>
>

 | 
Pages: 1
Prev: Version Control of Database
Next: Question about MS newsgroups posting