New SQL Server Release Slips to 2005

Strudelkugel writes "CRN reports SQL Server 'Yukon' will slip to 2005, complicating plans for ISVs and creating opportunities for OSS and other competitors."

Comments

Meanwhile, MySQL does transactions

[ka9dgx]

Meanwhile, MySQL is now doing transactions, and VIEWs are on their way in 5.1. It's GPL, so it's free (as in speech).

--Mike--

Re:That's okay

[next1]

i think you'll find PostgreSQL is also pretty good value for money!

Past tense?

[LarsWestergren]

"Early adoption of Yukon in enterprises was quite strong due to the functions and features [..]"

How can you talk about functions and features of software that has not yet been released? How can companies "early adopt" vaporware?

Yes, they can order in advance, but to me "adoption" means running something as a part of your business. Not "planning to maybe use it once you get it and if it turns out to be as good as you was promised it would be".

Mysql, PosteGres, DB2, Oracle MSSQL

[puto]

It is really funny the level of fervor behind Mysql. So funny it makes you wonder if the zealots have ever used anything other to any real extent.

The company I work for software's backend can go Mysql, Postgres, Mssql, Db2, or Oracle.

For massivce connections, queries, reporting, reliability it is in this order.

1. Mssql, DB2, Oracle, all pretty much equal.
2, Postegres, tricky but holds its own.
3. Mysql, will work in the low end, forget reporting, forget huge db hits.

I like Mysql. But Mssql 7.0 hands its ass to it.

What happens is some company will be our product. Hand it over to some 25 year old self proclaimed web genius to install. Conversation is as follows.

1. "Can I have the Source?" No, it is closed, long discussion about how we suck cause our product isn't open source.
2. "Ewwww, Java, it sucks, you should rewrite in PHP" I explain it has been continually developed since 96, no way to stop the engine and write in PHP.
4."I decided to save the company some money and install Mysql" We say ok, explain issues, put them in an email and fax(CYA principle). I then advise to run Postegre, that it is more robust, and is FREE as well.

No one lists. Junior installs on Mysql, everything runs fine, site gets huge amount of traffic, database gets quirky. Management starts running huge queries on database reporting tool. Database is very slow to respond, then in a few weeks keels over.

We get called. Tech is yelling, my guys are smirking(but still polite on phone) Management, myself, and tech gets on conference. Tech starts berating me. Management starts berating me. I pull out magic email and fax with all my system recquirements, suggestions for optimal use. Hey, guess what I was write. Wait a minute, shouldn't I know best since I work for the company that writes and support the product?

Three times a week this happens with Mysql. We have 14000 customers and I swear 50 percent have some guy that thinks he knows best.... knows our product better, knows computers better...

This is a great example of where our community needs to clean up its act. And I thought I would never say that.

Mysql is good for what it is, but there are many things it is not. Learn this.

Puto

SQL Server 2005, Visual Studio 2005

[pmsyyz]

CNET News reported five days ago on the 10th that both Yukon and Whidbey would be delayed and their final names. They need that time if they are going to clean up the shit HTML and JS outputed by VS. Not that they will, that would allow people to use Firefox.

The company said Wednesday that it has decided to push out to the first half of 2005 the delivery of the next major edition of SQL Server, code-named Yukon, and a closely related update to Visual Studio.Net, called Whidbey. Until recently, the company had said that both products would ship by the end of this year.

The final product names for Yukon and Whidbey will be SQL Server 2005 and Visual Studio 2005, said Tom Rizzo, director of product management for SQL Server.

Microsoft delays database, tools delivery