Reason for removing Native XML Web Services (SOAP/HTTP endpoints):

Question

Hi,

Can anybody please let me know the reason for removing the feature "Native XML Web Services (SOAP/HTTP endpoints)"  in SQL Server 2012 Release Candidate0?

The other deprecated features related to database engine are mentioned here:

http://msdn.microsoft.com/en-us/library/cc707789%28v=sql.110%29.aspx

Thanks,

Santosh

Answer 1

I don't have all details, but from what I understand adding SOAP to SQL Server was a big mistake. You should implement your web services in .Net, not in SQL Server.

Normally, when Microsoft deprecates something, they keep it for three releases, so SOAP should have been in SQL 12 as well and dropped by SQL 13. The fact that it was dropped so quickly indicates that it was very painful to keep it, for instance security issues. But I am just speculating.

---

Erland Sommarskog, SQL Server MVP, [e-mail]

Answer 2

Thank you very much Erland for the response. I wanted to know more descriptive reason for deprecating as even I'm wondering why it was removed so quickly by Microsoft. Pls revert back if anybody knows the same.

Thanks,

Santosh

Answer 3

Hi, I think the major reason for removing Native XML Web Services (SOAP/HTTP endpoints) in SQL Server 2012 is that it is not being used, by many customers.

David Schwartz

SQL Server Documentation

 

---

David Schwartz [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights

Answer 4

The primary motivation for removing SOAP is that adoption for this feature dropped off significantly after WCF and it did not provide access to many of the best practices needed to build a robust, scalable and secure web service. Instead, our guidance is to leverage technologies such as .net/WCF that provide a much more robust way to build services. This is especially the case for best practices and features related to scalability and security. We apologize for any inconvenience this may have caused but know that our focus was on encouraging developers to build high quality services in every respect vs. providing a low barrier to entry option that was lacking in many ways. Feel free to ping me offline with questions: [first].[last]@microsoft.com/

Regards,

Sean Kelley

 

 

 

 

 

 

---

Sean Kelley
Senior Program Manager
Microsoft