Microsoft Rinses SOAP Out of SQL Server 2008 109
Julie188 writes "A Microsoft SQL Server 2005 fan toppled over in surprise when he got this error message from SQL Server 2008 (he was running the SQL Server 2008 Upgrade Advisor tool): 'In SQL Server 2008, SQL Server native SOAP has been deprecated and will be removed in a future SQL Server release ... Avoid use of SQL server native SOAP in new development work, and plan to modify applications that currently use it.' No more SOAP-based Web services for your SQL Server database? Native XML was only added in v.2005 and was much ballyhooed at that time."
Properly Layer Your Architecture (Score:2, Interesting)
No more SOAP-based Web services for your SQL Server database?
Of course you can have SOAP-based Web Services for your SQL Server Database. Make your application server handle them. Or your XML middleware if you use it. I don't know if SQL Server supports WDSL's, but if they do and your own SOAP interface is compatible, this ought not be terribly painful at all.
If one were to fall over, it ought to be because Microsoft is making their database a bit more secure by removing extraneous code that doesn't need to be there. That's surprising, but welcome.
I suppose it's one less shortcut for developers, but one ought to expect there'd be a SOAP interface generator tool for sale to replace it for those who don't wish to do any coding. And if it exists, somebody out there is exposing their database directly to the Internet to save some effort. They've probably forgotten about SQLSlammer.
Once positioned as Java competitor (Score:3, Interesting)
I went to some MS conference years ago for a previous employer. The MS speaker who went over SOAP actually made it out to be a direct competitor to Java, which has never made any sense to me. But a lot of stuff from MS doesn't make a huge amount of sense to me.
Re:SOAP (Score:4, Interesting)
You can even create single purpose ssh keys which execute one command each
Close, but it is still not part of the specification itself.
Does javascript handle this? Can I use it in an AJAX call? Does it work out of the box from the CPAN libraries? Can you do it in PHP with a normal set of compile-time flags? Can you have anonymous clients authenticate themselves using a login/password (i.e. a flickr like web service?)
Want the ultimate proof that SOAP and XML-RPC is a failed specification? Every single javascript libraray (Prototype, jQuery, mooTools) doesn't support either one, yet every virtually every single XHttpRequest made is pretty much an RPC call.