I'm hoping that this is to become a trend with Microsoft. I have almost always worked with small to medium enterprises and selling them on a new DBMS or OS is always a hard slog. I am always keen to work with the latest release but SMEs have to see several valuable improvements before they will commit their cash. In this respect holding out for a really attractive upgrade is, in my opinion, a good move by Microsoft.
Speed
Since SQL Server's conception, it has come an awful long ways. It's nice to see that stability and good security have been taken into account within this new version of SQL Server. However, like any good development, testing environment BETA cycle, all I've seen is delays in getting this out the door (which is actually a good thing). But publicity wise, maybe wait to send new release notifications out on a new software product (or upgraded version) until it's more concrete on what's happening. I think it will keep the IT world alike more excited about something new, especially if it's an upgrade or newer version of a software that is widely used. But like everyone else, I can't wait to see YUKON (SQL Server 2005) in action. Thanks for the update. Julie
With so many new features, YUKON (Sql Sever 2005) needs to get them very stable and secure before releasing regardless of the other licensing programs Microsoft customers have purchased.
I would like to see these things sooner just like everyone else waiting for this release. But I like the new not at the risk of exposing our customers to unpleasantness approach. This delibrate approach to releasing new features is a welcomed thing from Microsoft. I remember the transition for 4.2 to 6.0 and how painful that could be on some fronts. __PETER
If all the new features live up to the hype, it sounds wonderful.
I like the idea of a Dedicated Administrator Connection. New! Improved! T-SQL sounds good too, and if the Integrated Toolset has good monitoring + management tools (ala SQLProbe) I'd be very happy.
I'd be very wary of an Online Restore and would probably avoid it as best as I could. If data was corrupted you might only discover it months later?
I'd be interested to find out more about the SQL Service Broker - the description on MS's site doesn't give much info.
Cheers
Given the importance of data in the corporate environment I think Microsoft have made a good call.
If YUKON is as big a jump forward as VS.NET then it will have been worth the wait.
Hopefully it will be stable and secure with no "buffer overrun" security glitches.
The delay is good in my opinion. I have played with Yukon Beta 1 and am very impressed but the "Not Yet Implemented" message box from the GUI was a bit annoying so I am anxiously awaiting Beta 2. It also made me wonder if they would be able to get a RTM version ready by the deadline.
Anyhow, I want and NEED a stable environment. With all the enhancements coming (DB Mirroring, .Net integration, the awesome workbench,...) I am a bit worried about the stability of the product. Also, SECURITY should be a major concern!
In my environment, I am constantly competing with another division that is set on Oracle. So far I have been able to fend them off with several factors and features and being able to integrate with them. They have seen how stable our setup is and that is helping. I don't want to lose any ground because the next version isn't stable and secure.
SJ
