|
|
|
Valued Member
      
Group: General Forum Members
Last Login: 2 days ago @ 2:52 PM
Points: 60,
Visits: 310
|
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 3:01 AM
Points: 266,
Visits: 1,023
|
|
Hi Brandon
How often do you run this stored procedure, and why?
I'm just trying to understand under what scenario you would want to shrink all transaction logs.
It would be a good idea to indicate in the article that regularly shrinking log files is not a recommended practice. I can see a newcomer to SQL Server reading the article and interpreting it as meaning that regularly shrinking log files is a good idea.
Chris
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: 2 days ago @ 4:00 PM
Points: 1,910,
Visits: 1,602
|
|
Hear, hear. As is, this article is terrible. You don't explain any of the reasons for doing this (or more importantly, not doing it).
You also say you must take a full backup to reestablish the log backup chain - not true - you can take a differential backup instead - potentially smaller and faster. You just need something to bridge the missing LSN gap.
Paul Randal CEO, SQLskills.com: Check out SQLskills online training! Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
|
|
|
|