November 16, 2011 at 5:29 am
Hi All,
While shrinking log the file from 250 GB to 10 GB, will prformance of the database will be slow.
Regards
Sudheer.K
November 16, 2011 at 5:36 am
Why shrink it down so much?
If you only release space back to the os it's fast. You can shrink in 1-5 GB increment to lessen the load.
Option B if you have that window (bit extreme). Shrink down to 0 and then expand to 10 GB based on those articles (a few links inside it).
http://www.sqlskills.com/blogs/kimberly/post/8-Steps-to-better-Transaction-Log-throughput.aspx
November 17, 2011 at 12:00 am
due disk space problem...Due to that much shrinking any Delay in data retriving ...
November 17, 2011 at 4:31 am
kollisudheer27 (11/17/2011)
due disk space problem...Due to that much shrinking any Delay in data retriving ...
It can have effects. That's why it's better to do it in smaller chunks like 5 GB. Try with 1 GB at first then increase up to the max time you feel confortable with.
November 17, 2011 at 5:24 am
Doesn't matter if you shrink in chunks or once off (except in the time it takes the shrink to run). If you shrink below the size required, the log will grow again and that growth will take time and, if the autogrow settings aren't sensible, will cause log fragmentation.
Does it have to go to 10GB? Does the DB only need a 10GB log file?
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 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply