We should expect to see a new version of SQL Server every 2-3 years ( "We are very committed to delivering SQL Server releases in 24 to 36 months." - ComputerWorld).
OK, I can understand that. They want to compete with Oracle and DB2. I'll still pi**ed off about the way they've handled SQL Server 2008 and think some of those marketing folks should be reassigned to the corporate gym where they can hand out free towels. Or maybe they can help move some terra firma in the ongoing campus expansion.
So if they're going to shoot for a new release every 2-3 years to get people into Software Assurance and provide steady revenue, what should they do? I hate to critize, as I've done recently, without offering any solutions to make things better. Well, here are a few suggestions.
Stop the CTP Madness - It seems that we used to have alphas and betas, then Microsoft decided not to build big betas, though we still have betas, but instead release CTPs every so often as they get closer to being finished. But then this post makes it seem like CTPs are between alphas and betas. Don't release alphas; we don't have time for stuff that doesn't work. Release CTPs early as you want to preview something, but then go through betas until you're feature complete, at which time, send out RCs that people can test against. Betas don't have to be huge, they just have to install.
Guarentee Service Packs - I liked the idea of the every other month rollups, but I don't stress them enough and I've seen enough complaints and issues with the various patches, that I think I'm wrong here. Give me 2 service packs a year, EVERY SINGLE YEAR, for SQL Server that roll up the patches. Release them on Mar 1 and Aug 1, avoiding any holiday hangovers, and give me 12 for each version. That's your 6 year life cycle until the next 2 versions launch.
Hire Testers - I know there are a lot of people testing things, and there are millions of tests run on each build. Thanks, I appreciate the efforts and I'm sure they're a good thing. But hire some real people to check for the stupid errors we encounter. Have someone LOOK at every UI change, like the maintenance plans, and be sure that nothing incredibly stupid is done.
Make Features Separate - I realize this is tricky, and I might be asking for a lot, but we pay you a lot of money to hire people and test things. Make things optional that are new "features". Just like Reporting Services was for SQL Server 2000. Make the vardecimal optional rather than being in a service pack. Make them downloads and roll them into the next version if you wish, but don't force them on me to get my server patched.
Use R2s - I don't agree with the 2-3 year life cycle, but I think the Windows 2003, R2, 2008 plan hasn't been too bad. If you must go to this cycle, then go with R2s for the interim releases and make it a "x.5" version that's more stable, more patched, more secure, but enough features to be worth buying. Save the big splashes for every 6 years.
Release every November - Just make is steady. Whatever's in by April is what goes, whatever isn't waits until it can be a "feature pack" download or gets dropped into the next version. There's always stuff that is close or isn't quite working, like database mirroring. If you release in November, then you can enable things or patch them quickly in the March Service Pack (see above).
Lock the Doors - Get the marketing folks out of the way until the next version is feature complete. Don't even let them look at what's in the product. Let the customer advisory team get feedback from people about what they need, use PSS, consultants, anything but the marketing folks. They don't need early knowledge, themes to target, or even input into the process. They're marketing. If they can plan a "launch" event when the product isn't feature complete, they can handle spinning whatever you build.
Steve Jones
The Voice of the DBA Podcasts
The podcast feeds are now available at sqlservercentral.podshow.com to get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.
or now on iTunes!
- Windows Media Podcast - 54.5MB WMV
- iPod Video Podcast - 46.2MB MP4
- MP3 Audio Podcast - 11.8MB
Today's podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.
I really appreciate and value feedback on the podcasts. Let us know what you like, don't like, or even send in ideas for the show. If you'd like to comment, post something here. The boss will be sure to read it.