Sachin Nandanwar (3/22/2011)
I was able to shrink successfully.
Here are the steps i followed.
Change the DB back to Simple If it is in Full mode.
Change it back to Full mode.
DBCC Shrinkfile(logfilename,Size you want to Shrink to)
But didnt the OP mentioned that his recovery mode was already in simple.
Yes, Sanchin, (s)he did. Which means changing recovery modes isn't just a bad idea because of log chain breakage, but because it has nothing to do with the existing problem.
mail.pnreddy, I understand that some people think that changing from FULL to SIMPLE will instantly truncate the transaction log (it doesn't quite work that way, BTW), but not only does it take time for the db engine to effect this change, but it takes disk space (which is at a premium), breaks the log chain, and causes a whole host of other problems, especially if this is a production environment during business hours.
Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.