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 |
|
chaosclyve
Starting Member
2 Posts |
 Posted - 2005-10-26 : 16:06:07
|
| Afternoon, I have a dilemma... I have a server running SQL 2k with a handful of databases. The largest/ most used database has a log file that has grown to a point that it cannot be backed up, shrunk via SQL enterprise mgr or forced via script to be shrunk. Currently the log file is sitting around 39GB (yes folks thats gig). I was going to try doing a backup and moving it to another server to try to shrink it, but I do not have another server w/ over 40gig of freespace. Any suggestion on how to kill this log file??? Thanks ChaosclyveWar is an ugly thing, but not the ugliest of things. The decayed and degraded state of moral and patriotic feeling which thinks that nothing is worth war is much worse. The person who has nothing for which he is willing to fight, nothing which is more important than his own personal safety, is a miserable creature and has no chance of being free unless made and kept so by the exertions of better men than himself.--John Stewart Mill-- |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-10-26 : 16:10:17
|
| BACKUP LOG [DB NAME GOES HERE]WITH TRUNCATE_ONLYThen shrink the log.*** Also do complete backups & log backups more often.An alternative is to drop the database, delete the log file, and then use sp_attach_single_file_db... but I think that is dangerous and also requires you take the database offline while doing it.Daniel, MCP, A+SQL Server DBAwww.dallasteam.com |
 |
|
|
chaosclyve
Starting Member
2 Posts |
Posted - 2005-10-26 : 16:20:53
|
| TY much, after running that I ran the force shink script I have and success.Chaosclyve |
|
|
|
|
|
|
SQL log file too large