﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 Administration  / How to manage log space issue, when you have more than 1 log file for a particular database? / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 22 May 2013 05:19:47 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: How to manage log space issue, when you have more than 1 log file for a particular database?</title><link>http://www.sqlservercentral.com/Forums/Topic1409146-1550-1.aspx</link><description>There is possibly an impact on logshipping.  If the primary and secondary are configured the same for files and file paths, the change will likely propagate to the secondary without problem.  If the filepaths are different then it is possible that the logshipping could be impacted.</description><pubDate>Sun, 20 Jan 2013 22:44:45 GMT</pubDate><dc:creator>SQLRNNR</dc:creator></item><item><title>RE: How to manage log space issue, when you have more than 1 log file for a particular database?</title><link>http://www.sqlservercentral.com/Forums/Topic1409146-1550-1.aspx</link><description>[quote][b]SQLRNNR (1/18/2013)[/b][hr]Somebody probably created the second file as a spillover due to the space issues.If the drive where the first log file was created is out of space, I would migrate to the second file by emptying the first file and then delete that first file.  Just use the second file on the drive that has adequate free space.[/quote]Is there any impact on log shipping by doing this?</description><pubDate>Sun, 20 Jan 2013 17:21:03 GMT</pubDate><dc:creator>MyDoggieJessie</dc:creator></item><item><title>RE: How to manage log space issue, when you have more than 1 log file for a particular database?</title><link>http://www.sqlservercentral.com/Forums/Topic1409146-1550-1.aspx</link><description>Somebody probably created the second file as a spillover due to the space issues.If the drive where the first log file was created is out of space, I would migrate to the second file by emptying the first file and then delete that first file.  Just use the second file on the drive that has adequate free space.</description><pubDate>Fri, 18 Jan 2013 21:15:27 GMT</pubDate><dc:creator>SQLRNNR</dc:creator></item><item><title>How to manage log space issue, when you have more than 1 log file for a particular database?</title><link>http://www.sqlservercentral.com/Forums/Topic1409146-1550-1.aspx</link><description>Hi All,If you encounter log space issue and if you have more than 1 log file for a database, how would you deal with it?In my scenario, I have a database which has 2 log files in 2 different drive, I am not sure who created this....I know more than 1 log file won't help performance since logs are generated sequentially..Anyway, my question is this......the second log file that host the drive has enough free space, however, the first log file drive is running out of space and this is creating the alert.  How would you deal with this situation?  Please share your experience.Thanks,SueTons.</description><pubDate>Fri, 18 Jan 2013 18:53:17 GMT</pubDate><dc:creator>SQLCrazyCertified</dc:creator></item></channel></rss>