Want to make a difference in the next version of SQL Server?
SQL Server 2008 is out, and I'm sure you are either learning about or already enjoying some of the new features. And while the dev team probably doesn't wholeheartedly agree with me at this very moment, I think that it can never be too early to start thinking about the next version.
As you surely know, not all of the features we have requested over time, and certainly not all of the bugs we have reported, have been delivered or fixed to date. This is certainly no discredit to the SQL Server team… they have added many exciting new features, and fixed a lot of bugs, over the past three years. But they could only do so much. Part of the problem is sheer volume… even a company the size of Microsoft has limits on how much they can allocate to a three year product cycle. Never mind that three years is not as long as it sounds, and there is a threshold of the number of talented minds you can throw at a project before you start experiencing diminishing returns. Another part of the problem is that it is very tough for them to get decent direction, when a surge in feedback comes too late into the process (or after an irreversible decision has been made). Take #341872 for example… while they said that they would gauge customer feedback, one of the most popular Connect items ever was not vocal enough to make Management Studio 2008's IntelliSense feature support downlevel servers. This probably makes Red-Gate very happy, but not the rest of us.
So like I said, it is never too early to start thinking about version 11. And with that in mind, fellow MVP Erland Sommarskog compiled a wish list of his "greatest hits"… the Connect items for which he would like to strum up support. I urge you to take a look through them, as he has made a significant effort to justify the items beyond the descriptions and comments in the items themselves. But the point of the exercise is deeper than that. Hopefully it will make you think of the things about SQL Server that you think are missing or flawed, and use Connect the way it was designed… to provide meaningful feedback and to give customer direction to the SQL Server team. You can see Erland's list here: