Comments on: When To Use Auto Shrink

By: Stop Shrinking Your Database Files. Seriously. Now. | Brent Ozar - SQL Server DBA

Wed, 19 Aug 2009 20:37:40 +0000

[...] Tom LaRock – “When to Use AutoShrink” [...]

By: Brant Wedel

Brant Wedel — Thu, 06 Aug 2009 06:00:17 +0000

Lol, its an option for databases storing historical data sets that other people have access to that might do a query causing a large file size jump, and maybe you have hundreds of these databases on a single server because your cheap and if they all were allowed to expand the server wouldn’t hold them all in thier ‘unshrunk’ state =P. SCADA databases are a good example of where AutoShrink might be useful im currently looking into it as we would like to continue using SqlExpress which has a 4 gig limit. And we will be doing monthly queries on the data, so performance is not a requirement.

By: SQLBatman

SQLBatman — Sat, 28 Mar 2009 02:08:08 +0000

Wow, Paul. If they would not listen to you, what hope is there for the rest of us?

By: Paul Randal

Paul Randal — Fri, 27 Mar 2009 18:44:02 +0000

Back when I was responsible for the whole Core Storage Engine at MS, I tried to have auto-shrink removed from the product – and failed. Backwards-compatibility trumped the ability for DBAs to shoot themselves in the foot. At least I managed to remove the ‘Repair minor corruptions’ options from the maintenance plan wizard… Cheers