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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-11-24 : 16:29:39
|
| Andy writes "no matter what i try ,the transaction log would not get truncated or reduced in size. i have tried the options of truncate_only and no_log options with dump transaction statements, ofcourse not both the options in the same statement. Before doing this i took a dump of the complete database. I even used the truncate option for transaction log in the enterprise manager screen. I am able to increase the size of the database datafile and transaction log file but unable to decrease the size of the transaction log file. I am running out of disk space. please kindly provide solution for this problem. Really appreciate for any kind of help.Thank you.Regards.Andy." |
|
|
MuadDBA
628 Posts |
Posted - 2001-11-26 : 12:43:34
|
| Search SWYNK.COM for the Stored procedure named SP_FORCE_SHRINK_LOG and you don't have to pay a red cent. |
 |
|
|
anastasia
Starting Member
6 Posts |
Posted - 2001-11-26 : 13:34:58
|
| If nothing is working, in 'Inside SQL Server 2000' Kalen Delaney has a quick way to shrink a log file that has become much larger that you would like. Chapter 5 Databases and database files, Detaching and reattaching a Database. use sp_detach_db procedure ( SQL Server will know that database was cleanly shut down , and log file does not have to be available to attach the database). Sp_attach _db will create new log , which will have a minimum size - less than 1MB.It will not work if the database has more than one log file. |
|
|
|
|
|
|
unable to purge the transaction log