Hi everyone, I have had this problem only a few times in my 7 years as a DBA. I notice that the transaction log file grew to a large amount usually over 5 gigs, truncates after the backup processes runs for the database and log. But it leaves the file size very large. Usually the shrinkfile in Enterprise Manager works fine, but when it doesn't work it is frustrating. I have tried everything using TSQL, EM, and the only thing that will force MSSQL to give up that file size is to change the recovery option to simple then back again to Full. I know this is dangerous since it is altering or wipping out the transaction log. This is not a typical problem I have but seems like when I make some index changes or defrag the index it blows up the transaction log from 2G to 15G. The database size is 5G. I am using SQL server 2000 Standard. Oh yes and plenty of diskspace. Has anyone ever had this problem before? Thanks for your help. Steven.