.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links


Posted By:      Posted Date: September 18, 2010    Points: 0   Category :Sql Server
I would just like to ask more of a survey question versus a real problem: Why did Microsoft feel it necessary to strip out TRUNCATEONLY???? Don't they know we're all big kids and know not to play with fire? I just think it's really annoying. I know I'll get the arguement that "if you're going to TRUNCATE a log, just put the database in SIMPLE mode to begin with". Well if that's the case, why weren't the same people who pose that arguement posing that arguement years ago when that option WAS available?!?! Also, any database person knows that there are times when a TRUNCATEONLY is just plain necessary. I've inherited a system with literally hundreds of databases that are running in FULL mode, but have NEVER had a transaction log backup performed - we're talking almost a terabyte of logs. So now, I haev to write a script to 1.) put them all into SIMPLE mode, 2.) SHRINK the file, 3.) put them all back into FULL. Oh joy...A. M. Robinson

View Complete Post

More Related Resource Links

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend