Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
divesheik
Starting Member
3 Posts |
 Posted - 2007-07-17 : 19:53:06
|
| I have got transaction log files that are approaching 25gb in size. I need to delete them and associate new .ldf files with my .mdf files. Have tried detaching database, deleting orig .ldf files and reattaching database, but didn't work. I've also tried renaming orig dbase, creating a new dbase with same orig name so a new .ldf file would be created, then renaming the orig database to orig name. that didn't work either. Any knowledgeable advise out there? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-17 : 23:08:58
|
| Do log backup with truncate only option, set db to simple recovery model then shrink log file. Reset db recovery model afterwards. |
 |
|
|
mattyblah
Starting Member
49 Posts |
Posted - 2007-07-18 : 00:11:01
|
| have you checked to make sure there are no outstanding transactions? that could cause the log file to balloon... |
|
|
|
divesheik
Starting Member
3 Posts |
Posted - 2007-07-18 : 19:24:09
|
| Doing that now. I do not see a "truncate only" option when backing up t log file. will try it anyway and post results. thxMS |
|
|
|
divesheik
Starting Member
3 Posts |
Posted - 2007-07-18 : 19:36:01
|
This worked like a charm!! Thank you all for the feedback!quote:
Originally posted by rmiao
Do log backup with truncate only option, set db to simple recovery model then shrink log file. Reset db recovery model afterwards.
MS |
|
|
|
|
|
|
Excessively large .ldf files