Effect of Backup Log with Truncate_only on the automatic Checkpointing of a DB

21/05/2008, 17h33

Hi,

We are running SQL2005 SP2 build 3175, soon to be 3239, and have some
conversion jobs that use Backup Log with Truncate_Only. The analyst says
that the checkpoint task blocks the conversion job. Personally I can't wait
for SQL2008 to stop the Truncate_only option, but that's beside the point.

I believe that the checkpoint has trouble because of the Truncate_Only which
is run after a number of transactions have been applied to the database. Is
this a true argument?

Thanks

Chris

21/05/2008, 18h08

Chris Wood,

> Backup Log with Truncate_Only

That means you do not care about backing up the transaction log. If so, then
why that db is using a recovery model other than "simple"?

AMB

"Chris Wood" wrote:

> Hi,
>
> We are running SQL2005 SP2 build 3175, soon to be 3239, and have some
> conversion jobs that use Backup Log with Truncate_Only. The analyst says
> that the checkpoint task blocks the conversion job. Personally I can't wait
> for SQL2008 to stop the Truncate_only option, but that's beside the point.
>
> I believe that the checkpoint has trouble because of the Truncate_Only which
> is run after a number of transactions have been applied to the database. Is
> this a true argument?
>
> Thanks
>
> Chris
>
>
>

21/05/2008, 18h21

Alejandro,

We have programmers with SQL 6.5 mentality. I wish they would change it to
simple when this stuff runs but...

Chris

"Alejandro Mesa" <AlejandroMesa@discussions.microsoft.com> wrote in message
news:A86FB944-EF13-4213-BAD5-AAD6190FD1B1@microsoft.com...
> Chris Wood,
>
>> Backup Log with Truncate_Only
>
> That means you do not care about backing up the transaction log. If so,
> then
> why that db is using a recovery model other than "simple"?
>
>
> AMB
>
> "Chris Wood" wrote:
>
>> Hi,
>>
>> We are running SQL2005 SP2 build 3175, soon to be 3239, and have some
>> conversion jobs that use Backup Log with Truncate_Only. The analyst says
>> that the checkpoint task blocks the conversion job. Personally I can't
>> wait
>> for SQL2008 to stop the Truncate_only option, but that's beside the
>> point.
>>
>> I believe that the checkpoint has trouble because of the Truncate_Only
>> which
>> is run after a number of transactions have been applied to the database.
>> Is
>> this a true argument?
>>
>> Thanks
>>
>> Chris
>>
>>
>>

21/05/2008, 17h33	#1
Chris Wood Messages: n/a Hébergeur:	Effect of Backup Log with Truncate_only on the automatic Checkpointing of a DB Hi, We are running SQL2005 SP2 build 3175, soon to be 3239, and have some conversion jobs that use Backup Log with Truncate_Only. The analyst says that the checkpoint task blocks the conversion job. Personally I can't wait for SQL2008 to stop the Truncate_only option, but that's beside the point. I believe that the checkpoint has trouble because of the Truncate_Only which is run after a number of transactions have been applied to the database. Is this a true argument? Thanks Chris

21/05/2008, 18h08	#2
Alejandro Mesa Messages: n/a Hébergeur:	RE: Effect of Backup Log with Truncate_only on the automatic Checkpoin Chris Wood, > Backup Log with Truncate_Only That means you do not care about backing up the transaction log. If so, then why that db is using a recovery model other than "simple"? AMB "Chris Wood" wrote: > Hi, > > We are running SQL2005 SP2 build 3175, soon to be 3239, and have some > conversion jobs that use Backup Log with Truncate_Only. The analyst says > that the checkpoint task blocks the conversion job. Personally I can't wait > for SQL2008 to stop the Truncate_only option, but that's beside the point. > > I believe that the checkpoint has trouble because of the Truncate_Only which > is run after a number of transactions have been applied to the database. Is > this a true argument? > > Thanks > > Chris > > >

21/05/2008, 18h21	#3
Chris Wood Messages: n/a Hébergeur:	Re: Effect of Backup Log with Truncate_only on the automatic Checkpoin Alejandro, We have programmers with SQL 6.5 mentality. I wish they would change it to simple when this stuff runs but... Chris "Alejandro Mesa" <AlejandroMesa@discussions.microsoft.com> wrote in message news:A86FB944-EF13-4213-BAD5-AAD6190FD1B1@microsoft.com... > Chris Wood, > >> Backup Log with Truncate_Only > > That means you do not care about backing up the transaction log. If so, > then > why that db is using a recovery model other than "simple"? > > > AMB > > "Chris Wood" wrote: > >> Hi, >> >> We are running SQL2005 SP2 build 3175, soon to be 3239, and have some >> conversion jobs that use Backup Log with Truncate_Only. The analyst says >> that the checkpoint task blocks the conversion job. Personally I can't >> wait >> for SQL2008 to stop the Truncate_only option, but that's beside the >> point. >> >> I believe that the checkpoint has trouble because of the Truncate_Only >> which >> is run after a number of transactions have been applied to the database. >> Is >> this a true argument? >> >> Thanks >> >> Chris >> >> >>

Outils de la discussion
Afficher une version imprimable Envoyer un lien vers cette page par email