[dba-SQLServer] Log file reuse

One of those generic "second chance error" thingies.  No meaningful
interpretation provided. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: dba-sqlserver-bounces at databaseadvisors.com
[mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Francisco
Tapia
Sent: Saturday, December 08, 2007 3:58 PM
To: dba-sqlserver at databaseadvisors.com
Subject: Re: [dba-SQLServer] Log file reuse

It will reuse space if you are clearing the data at the check points.
One of the many reasons I have auto backups when the log hits > 60%.
You can choose juse to runt the truncate log backup command that just simply
flushes out committed transactions, in my environment I cannot do that but
should not be too bad for you if you so need this functionality.

Btw out of curiosity what was the error you received?




On 12/8/07, jwcolby <jwcolby at colbyconsulting.com> wrote:
> Well, the log file on another drive failed with errors.  No time to 
> troubleshoot, I am just moving the log back to the same drive.
>
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of 
> jwcolby
> Sent: Saturday, December 08, 2007 11:20 AM
> To: dba-sqlserver at databaseadvisors.com
> Subject: [dba-SQLServer] Log file reuse
>
> If a SQL Server action query completes, does SQL server reuse the now 
> empty log file?
>
> I have a raid array that is huge and I use to hold these large 
> databases.  I have another single drive sitting on a SATA channel.  I 
> am experimenting by placing the log file onto that single SATA drive 
> and the data file on the raid.  I am running about 660 more action 
> queries to move data from fields in a 50 million record 680 field wide 
> table to a 3 field wide table.  The source table and the destination 
> table both sit on the raid, with the log file out on the non-raid.  I 
> am hoping that because of IO issues, placing the log file on a 
> different physical drive will speed things up.  I have no way to really
know however.
>
> I am hoping that once the log file is expanded (it is about 13 g now) 
> that unless the data in the subsequent fields requires more log file 
> room, the "cost" of expanding the log file will go away and the log 
> file empty space will be reused for each subsequent action query.
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>


--
-Francisco
http://sqlthis.blogspot.com | Tsql and More...
_______________________________________________
dba-SQLServer mailing list
dba-SQLServer at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
http://www.databaseadvisors.com