Microsoft showed off some of the forthcoming programmability features of “Yukon,” the next version of its SQL Server database, here at the VSLive! developer conference on Thursday. Yukon won’t be an XML database, but will rather integrate support for XML data types into the relational SQL Server database.
SQL Server “Yukon” Details Revealed
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
This worries me on the security front. Traditional n’ tier network systems should place the data store in the secure internal network zone and place external application servers in the DMZ, accessable from the public networks. This ACC thing sounds like another hyperintegrated M$ product that will spawn the next generation of Slammer type worms. I see this as likely opening too many “paths” into the database that information could leak out of or malitious code could get in by.
Then again its dificult to draw any conclutions from some of these almost contentless tech “news” sites.
Does it come with Slammer support?
MS-SQL server is a no-starter for several reasons. First it’s locked into the Windows platform, which makes it a liability in the server room for maintenance, security and stability. Second, it itself is the focus of several http://www.npaci.edu/Press/03/020403_SAPHHIRE.html“>security . Lastly, it lags far behind other SQL servers other areas as well, and is severely
http://www.eweek.com/article2/0,3959,293,00.asp“>outperformed .
Well MS-SQL is actually quite a competant database.
There has been a pathch for the Slammer worm for a long time and while Microsoft have to take some of the blame for making the patch hard to apply they have fixed the bug. Security holes are hardly limited to MS-SQL after all Oracle made them selves look silly with their whole our DB is uncrackable campain
.
As for performance you should reread that benchmark and you would see that it was done with BETA!!! jdbc drivers. The jdbc drivers were very bad and probably still are. You can buy fast jdbc drivers for sql server but you are better off using a diferent database if you want to connect to java as microsoft isn’t that java friendly. If you look at how that benchmarking pacge you will see that the asp version that uses the proper SQL server drivers outperforms the lot of them not that that proves anything as it is hardly a fair test!!. Plus a benchmark that shows that MySQL performs at a similar rate to Oracle is clearly using very very simple queries and doesn’t really stress the database properly.
If you look at the proper industory TPC-C benchmarks you will see that SQL server is beating Oracle on similar systems so you could argue that MS-SQL is the fastest DB out there.
Using MS-SQL does lock you into windows but windows is starting to become an acceptable (I am not going to claim it is a good server OS but .NET server looks to be a good step in the right direction) server OS and if you have two clustered boxes with shared storage you can get very good uptime and performance for a much cheeper price than the equiverlent Sun box. It is clearly not going replace very large sun boxes running Oracle within the near future but it is a good DB for most Mid Range applications. For small range applications like that bench mark seems to be running then you would be best of useing a free DB like Postgresql and save your $s.
Read the article. The JDBC Drivers are the issue. Microsoft has sinced released near drivers that have better performance.
And like previously mentioned, you can buy 3rd party drivers that most likely outpeform the MS drivers.
SQL Server 2K is a very reliable DBMS. I have to say that it’s the best server product Microsoft has to offer.