Microsoft Rinses SOAP Out of SQL Server 2008

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."

Comments

Lather, Rinse, Repeat

[Jeremiah Cornelius]

Maybe because SOAP (Simple Object Access Protocol) has proven to be a dead-end, particularly for structured data storage, and especially in the pursuit of "cloud" services.

No one is turning back on XML or serialized application interfaces over HTTP. The storage interfaces will be accessible using some REST oriented API.

Re:Lather, Rinse, Repeat

[AKAImBatman]

which probably explains why it was so enthusiastically adopted by Java

Actually, SOAP was pushed heavily by Microsoft as part of .NET. Java took a more holistic approach and created APIs for SOAP, XML-RPC, REST, and many other services. There are about 3-4 different ways you can do each of them, with two of them being official or semi-official. (The reason for the break is that the methodology for providing such services was greatly enhanced by the attribute tags added in Java 1.6.)

If you're doing SOAP services, I'd blame the market for slurping up Microsoft's push rather than blaming your tools which happen to support the standard.

What's the old saying? "It's a poor craftsman who blames his tools?" ;-)

Re:Lather, Rinse, Repeat

[Simon (S2)]

SOAP (Simple Object Access Protocol)

Actually no: since SOAP version 1.2 SOAP is not an acronym anymore because it has nothing that is "simple".

Re:Lather, Rinse, Repeat

[rishistar]

My girlfriend keeps insisting on me using SOAP before we interface - now I know its Microsofts fault.

Re:Lather, Rinse, Repeat

[BillAtHRST]

"There are about 3-4 different ways you can do each of them, with two of them being official or semi-official."

Isn't that the whole problem with Java in a nutshell? I like the language OK, but all the framework stuff bolted on to it, combined with "deprecated"-this and "deprecated"-that, really cause a geometric explosion in what one needs to understand and/or support in that environment.

Re:Lather, Rinse, Repeat

[AKAImBatman]

Isn't that the whole problem with Java in a nutshell?

Only if you consider choice to be a bug. Personally, I like the fact that I don't have to use the officially sanctioned method if I don't want to. And the older official methods do not deprecate with the introduction of the newer methods. Both can still be used.

In fact, there is very little deprecated overall in Java. It's just that there is often more than one way to skin a cat. Choose the one that works best for you.

it won't be missed

[inmate]

as a developer on sql2005, i found very little use for it. the xml parsing and displaying functionality will remain in 2008, only the native xml webservices are being pulled. it made no sense anyway, it had nothing of the richness that asp.net web services offer and made most administrators nervous about its security (and rightly so!) why anyone in their right minds would have used it...i don't know!

Use a web server

[truthsearch]

No more SOAP-based Web services for your SQL Server database?

Not exactly. It means no more SOAP-based Web services directly served from your SQL Server. Now you have to go back to using a web server application like god intended.

Confucius say

[Profane MuthaFucka]

Confucius say "Microsoft wrong again. Computer programmers need more soap, not less."

Poster's comment misleading

[code addict]

I think that poster's comment is a little misleading. From the article and linked materials it would appear that only integrated SOAP web services are deprecated, and not native XML as the poster implies.

Details of deprecated features here: http://technet.microsoft.com/en-us/library/ms143729.aspx

Why was this even included in the first place?

[Tridus]

I don't get why Microsoft ever thought this was a good idea. Regardless of your opinion on SOAP (and I don't hate it nearly as much as some other folks here), having the SQL Server dishing it out directly was always kind of silly. Thats what a Web Server is for.

Removing silly code that just creates more places for security holes to hide is a good thing. Not doing it at all would have been better, but at least Microsoft is fixing that mistake now.

Once positioned as Java competitor

[Visoblast]

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:oh great

[Just Some Guy]

Dude, take it back. There are some things that just aren't said in polite society.

Re:SOAP

[coryking]

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.

There is quite a bit of deprecation in javax.swing

[Gazzonyx]

This hurts, but I've gotta' say it.

While I generally agree with you, AKAImBatman, I think you've missed the mark on this one. The Serializable interface has been deprecated and will not be forward compatible. Unfortunately, this affects (effects? I always get them mixed up...) just about everything in the javax.swing package.

Granted, swing is somewhat ugly, single threaded (discounting worker threads - you still only have one dispatcher to do painting, anyways... although I want to choke everyone who tries to do everything on the dispatcher and wonders why nothing is responsive), and a generally over engineered toolkit; but it's also been around since like version 1.0 and is still effective for consistent cross platform GUIs. LookAndFeel aside, Solaris, Windows, Linux (X11R6 and R7) and, I would presume, Macs all render the same under Swing. As a bonus, about five lines of code will make a Swing app an applet in any browser with a java plugin, and it still renders exactly the same.

I have no idea why something so proven would be deprecated after all this time, considering how many legacy apps could break. Unless I'm not understanding the rational, which is more than likely considering I've never bothered to follow up on it after reading the deprecation notice in the JavaDocs. If so, feel free to flame me for being so loud about something I was too lazy to look up before opening my mouth.