Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Native XML Web Services Concepts

This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

Beginning with SQL Server 2005, SQL Server provides native XML Web Services through the SQL Server Database Engine by using the following open standards:

  • Hypertext Transfer Protocol (HTTP)

    As the core protocol behind the World Wide Web, HTTP provides a platform-neutral Web-based exchange of data.

    Important noteImportant

    HTTP support requires the HTTP listener: Http.sys. Http.sys is available only on Windows Server 2003 and Windows XP Service Pack 2. For more information, see Configuring the HTTP Kernel-Mode Driver (Http.sys).

  • SOAP

    SOAP defines how to use XML and HTTP to access services, objects, and servers regardless of the operating system.

  • Web Services Definition Language (WSDL)

    WSDL is an XML document format that can be used to describe Web-based services.

When you use Native XML Web Services in SQL Server 2005 or later, you can send SOAP messaging requests to an instance of SQL Server over HTTP to run the following:

  • Transact-SQL batch statements, with or without parameters.

  • Stored procedures, extended stored procedures, and scalar-valued user-defined functions.

Native XML Web Services: Deprecated in SQL Server 2008

Native XML Web Services has been deprecated in SQL Server 2008, and will be removed in a future release of SQL Server.

Native XML Web Services Overview

Compares Native XML Web Services to Microsoft SQLXML, describes how Native XML Web Services works, and lists some benefits from using it.

Deploying Native XML Web Services

Provides an initial general planning and deployment checklist to refine and follow when evaluating or deploying Native XML Web Services.

Best Practices for Using Native XML Web Services

Provides information and recommendations from the SQL Server product team on best practices to follow for evaluating or deploying Native XML Web Services.

Setting the Server to Listen for Native XML Web Services Requests

Describes how to configure and provision a server computer that is running SQL Server 2005 or later to help it listen and service HTTP-based requests in a secure manner.

Using WSDL

Describes how WSDL responses are generated and used by Native XML Web Services to support publication of SQL Server programmability that you selectively expose to Web clients.

SOAP Request and Response Message Structure

Details the structure of the various XML-based messages that are used by the SOAP standard.

Working with SOAP Sessions

Describes how SOAP sessions work and can be used to extend multibatch processing to Web-based SQL Server clients.

SQL Server Authentication over SOAP

Describes the choices for how SQL Server authentication can be accommodated in SOAP-based client access scenarios.

Writing Client Applications

Provides an example Web client application in C# and Visual Basic to demonstrate how to use Native XML Web Services when you are developing with Visual Studio 2005.

Performance Counters for Native XML Web Services

Provides reference information about counters specific to Native XML Web Services that are available for you to use when you monitor performance of your Web applications by using Performance Monitor.

Data Type Mappings in Native XML Web Services

Provides reference information about mapping SQL data types to the XML Schema (XSD) data types that are defined for use in WSDL files that are returned by Native XML Web Services.

Guidelines and Limitations in Native XML Web Services

Documents usage guidelines and feature limitations for Native XML Web Services.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.