Archive. Posts from 2004 to 2016, kept as they were written. My current blog is at dariuszparys.com.

With the February CTP of SQL Server 2005 some changes occured in custom WSDL generation for native web services out of SQL Server 2005. Of course, since the product is still in development. Unfortunately the demos are not up to date with the CTP releases therefore you have to figure out yourself in some areas how things work correctly. In the case of custom WSDL generation an additional parameter came into play: UserAgent. How did I find the missing one? The out-of-box WSDL generation is based on two system stored procedures named sp_http_generate_wsdl_defaultcomplexorsimple and sp_http_generate_wsdl_defaultsimpleorcomplex (based on Feb. CTP). So the only thing I just needed to know is what parameters I need to implement in my own stored procedure to make custom WSDL generation work. So I just took a look and viola, I got it.

[Image not archived]

@UserAgent was expected and this parameter was missing in my current implementations.