Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Restore Faills Expand / Collapse
Posted Tuesday, September 4, 2012 8:38 AM


Group: General Forum Members
Last Login: Wednesday, October 12, 2016 1:16 PM
Points: 128, Visits: 394

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.

Post #1353946
Posted Wednesday, September 5, 2012 1:48 AM



Group: General Forum Members
Last Login: Thursday, September 1, 2016 2:56 AM
Points: 5,969, Visits: 6,067
Managing Transaction Logs -
Accidental DBA Guide - Chapter 8 -

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?

Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
When a question, really isn't a question - Jeff Smith
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1354363
Posted Wednesday, September 5, 2012 2:03 AM



Group: General Forum Members
Last Login: Saturday, December 3, 2016 5:18 AM
Points: 45,619, Visits: 44,147
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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1354369
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse