I was discussing some of the missing features with one of the SQL Server product managers a couple weeks ago, and he said something that I hadn't really thought about before. I asked him how some of these things could have made it out of beta, and he said that beta cycles are very good at shaking out usability issues. He's right too. Think about how you look at beta software. You always judge it for major featur I was discussing some of the missing features with one of the SQL Server product managers a couple weeks ago, and he said something that I hadn’t really thought about before. I asked him how some of these things could have made it out of beta, and he said that beta cycles are very good at shaking out usability issues. He’s right too. Think about how you look at beta software. You always judge it for major features, and if something’s missing from the GUI, you always just assume it’ll be added for the final release. I’ve said that many times myself… “oh well, they’ll get around to it. This is just the beta.” The problem is that everyone says that and you can’t test against everything. So things get overlooked. The thing to do is complain about every little thing as early as you can. On more than one occasion MS has told me that every single issue gets a developer assigned to it and you can see the progress of your issues. Personally, I love that. Not only will you get some really good ideas, but you’re making your customers part of the cycle and if they know their issues are actually going to be addressed in one way or another, they’re more likely to submit them. Everyone wins. So go to the website they’ve setup to track these issues and complain about whatever you like. They can take it. Be very liberal with the amount you use this service too. Use it as much as you like. The only way they’re gonna shut us up about it is to actually fix the issue. Here’s the link: https://connect.microsoft.com Databases