Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

How to manage log space issue, when you have more than 1 log file for a particular database? Expand / Collapse
Author
Message
Posted Friday, January 18, 2013 6:53 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 2:23 PM
Points: 422, Visits: 2,643
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.


Regards,
SQLisAwe5oMe.
Post #1409146
Posted Friday, January 18, 2013 9:15 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:24 PM
Points: 17,807, Visits: 15,728
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.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1409157
Posted Sunday, January 20, 2013 5:21 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, October 16, 2014 6:18 PM
Points: 3,952, Visits: 7,170
SQLRNNR (1/18/2013)
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.
Is there any impact on log shipping by doing this?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1409326
Posted Sunday, January 20, 2013 10:44 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:24 PM
Points: 17,807, Visits: 15,728
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.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1409358
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse