September 4, 2012 at 8:38 am
Hello
i need your best suggestion.
Here is scenario.
I have a Production server and we backup that server and restore to DAYB server everyday.
Right now Production server's Transaction log is growing to 20 GB and we are running out of space on DAYB server. we have only 17 GB free space on it.
so my manager is suggests me,
truncate Transaction log for temporary fix on Production server. The Data File on Production is 95 GB so is that worth to truncate Transactional log file only for restore purpose on DayB?
Whats Your Suggestion, Please reply me.
Thanks in Advance.
September 5, 2012 at 1:48 am
Managing Transaction Logs - http://www.sqlservercentral.com/articles/Administration/64582/
Accidental DBA Guide - Chapter 8 - http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
The only way to "truncate" your data file would be to delete data, shirnk the file then rebuild all your indexes which could created a bigger file that what you already had so I would leave that alone.
As for the log, I take it the recovery model of the database is in FULL, do you use logshipping or backup the transaction log regular for restoring purposes?
September 5, 2012 at 2:03 am
Add more drive space to server B.
Seriously, if the DB is growing, it's growing. Unless you decide to archive data and hence free up space in the data file, the DB will keep on growing.
Shrinking a DB that's going to soon fill the drive because of data growth is a futile approach. The data volumes are still growing, shrink doesn't compress or remove data
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply