• “SQL Server 2005 Express Edition doesn’t support HTTP endpoints, so you must license the Workgroup Edition or better to enable these features for production. Only Windows XP Service Pack 2 (SP2) and Windows 2003 Server install Http.sys; thus, you can't deploy native Web services to Windows 2000 servers.”

• “The SQL Server team's design goal was twofold: Provide cross-platform data access that delivers parity with the Windows-only Tabular Data Stream (TDS) protocol, and move the SOAP stack from the IIS middle tier to the database engine's process.”

From Wikipedia.org: “Tabular Data Stream (TDS) is a protocol, to transfer data between a database server and client. Initially designed and developed by Sybase Inc. for their Sybase SQL Server relational database engine in 1984, and later by Microsoft in Microsoft SQL Server.” (http://en.wikipedia.org/wiki/Tabular_Data_Stream)

• “You also can take advantage of C# or VB CLR stored procedures to customize the service’s WSDL document for use by non-Microsoft SOAP toolkits, such as Borland’s JBuilder 9.0 or webMethods’ Glue 5.0.1.”

This is the first recognition of “non-Microsoft SOAP” but only proprietary “toolkits” are recognized.

• “Setting SCHEMA = NONE removes the inline XML schema; most non-Microsoft SOAP toolkits won't process SOAP response messages with inline schemas.”

• “WSDL = DEFAULT generates a dynamic WSDL document with complex or simple (xsd:any) data typing. Data typing depends on the service URL that you use to generate the Web service proxy, which I’ll discuss shortly. …Substituting ?wsdlsimple for ?wsdl in the WSDL document’s URL query string replaces proprietary SQL Server–specific types with XML schema simple datatypes and sqlresultstream:SqlResultStream with the XML schema xsd:any datatype wildcard.”

The ?wsdlsimple query string option is very important!