Five things SQL Server should ban forever

Here's my list of what needs to go.

Ok, everyone seems to be creating a list of five things that SQL Server should get rid of, so I'll do one of those as well.  (I already did a "five things that SQL Server needs", but apparently I jumped the gun on that one. Oh well).  Actually I'm fairly happy with everything in the product right now, and really don't have anything that's hanging around driving me crazy.  Having said that, sure here's a few that I wouldn't miss:

Model Database - Does anyone really use this thing?   The ability to make changes to it so that when you create a new database it is "modeled" after a template, so to speak,  is a good idea I guess, but I never seem to use it.

Database Diagrams - This facility is weak, so getting rid of it is no hair off of my <backside>.  Make it really slick or just trash it.

Backup Devices - I can't remember the last time I actually created a device for a backup.  Not needed.

OLE Automation - What I thought was once cool, back in my wilder and more daring days, is a garbage. This stuff needs to go. Can't believe that it's still around.  What's worse - I can't believe that it's not deprecated! I'll always appreciate that piece of ingenious code by the late, great Ken Henderson on programming the Microsoft Word API to spell-check before inserts into a table, but I'd never use something like that in a production setting.

Auto Shrink - Probably the worst 'feature' eva!  I think they leave it in just so that they can warn beginning DBA- types to go shut it off, and fill up chapters in books and articles.  It's gotta go!!!

Lee

-----------------------

"He's not a man - a machine. A Terminator. A Cyberdyne Systems Model 101"