Deploying Native XML Web Services

Learn about Native XML Web Services provided with SQL Server 2005.

Using Native XML Web Services in SQL Server 2005

Understand requirements for your application. For example, the following questions are helpful to ask at this step in the process:

• Is your application for high-volume OLTP or only for occasional use?
  
• Do the stored procedures contain lots of business logic?
  

Best Practices for Using Native XML Web Services

Determine which client operating system types are to be supported. For example, the following questions are helpful to ask at this step in the process:

• Is the client operating system a Windows-based or an operating system other than Windows?
  
• Do you have a heterogeneous environment?
  

Best Practices for Using Native XML Web Services

Determine whether your application will be deployed for intranet or extranet use?

Guidelines and Limitations in Native XML Web Services

Best Practices for Using Native XML Web Services

Choose the authentication type that is best suited for use with your endpoint deployment.

Endpoint Authentication Types

Decide on the correct WSDL strategy for your environment: default, simple, custom, or none.

Using WSDL

Create HTTP endpoints to allow the instance of SQL Server listen to HTTP requests.

Setting the Server to Listen for Native XML Web Services Requests

CREATE ENDPOINT (Transact-SQL)

Grant permissions to endpoints.

GRANT Endpoint Permissions (Transact-SQL)

Expose stored procedures or user-defined functions as Web methods.

Exposing SQL Programmability to the Web

Test the default WSDL response from the endpoint.

Default WSDL

Simple WSDL

(optional) Update or re-create endpoints as needed.

ALTER ENDPOINT (Transact-SQL)

DROP ENDPOINT (Transact-SQL)