[MS-SSDPWP]:
Database Publishing Wizard Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
§ Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.
§ Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.
§ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
§ Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
§ Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.
Revision Summary
Date / Revision History / Revision Class / Comments /08/07/2009 / 0.1 / Major / First release.
11/06/2009 / 0.1.1 / Editorial / Revised and edited the technical content.
03/05/2010 / 0.2 / Minor / Updated the technical content.
04/21/2010 / 0.3 / Minor / Updated the technical content.
06/04/2010 / 0.3.1 / Editorial / Revised and edited the technical content.
09/03/2010 / 0.3.1 / No change / No changes to the meaning, language, or formatting of the technical content.
02/09/2011 / 0.3.1 / No change / No changes to the meaning, language, or formatting of the technical content.
07/07/2011 / 0.3.1 / No change / No changes to the meaning, language, or formatting of the technical content.
11/03/2011 / 0.3.1 / No change / No changes to the meaning, language, or formatting of the technical content.
01/19/2012 / 0.3.1 / No change / No changes to the meaning, language, or formatting of the technical content.
02/23/2012 / 4.0 / Major / Significantly changed the technical content.
03/27/2012 / 4.0 / No change / No changes to the meaning, language, or formatting of the technical content.
05/24/2012 / 4.0 / No change / No changes to the meaning, language, or formatting of the technical content.
06/29/2012 / 4.0 / No change / No changes to the meaning, language, or formatting of the technical content.
07/16/2012 / 4.0 / No change / No changes to the meaning, language, or formatting of the technical content.
10/08/2012 / 5.0 / Major / Significantly changed the technical content.
10/23/2012 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
03/26/2013 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
06/11/2013 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
08/08/2013 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
12/05/2013 / 5.0 / No change / No changes to the meaning, language, or formatting of the technical content.
02/11/2014 / 6.0 / Major / Significantly changed the technical content.
2/2
[MS-SSDPWP] — v20140211
Database Publishing Wizard Protocol
Copyright © 2014 Microsoft Corporation.
Release: Tuesday, February 11, 2014
Contents
1 Introduction 6
1.1 Glossary 6
1.2 References 6
1.2.1 Normative References 6
1.2.2 Informative References 7
1.3 Overview 7
1.4 Relationship to Other Protocols 7
1.5 Prerequisites/Preconditions 8
1.6 Applicability Statement 8
1.7 Versioning and Capability Negotiation 8
1.8 Vendor-Extensible Fields 8
1.9 Standards Assignments 9
2 Messages 10
2.1 Transport 10
2.2 Common Message Syntax 10
2.2.1 Namespaces 10
2.2.2 Messages 10
2.2.3 Elements 10
2.2.4 Complex Types 10
2.2.5 Simple Types 10
2.2.6 Attributes 10
2.2.7 Groups 11
2.2.8 Attribute Groups 11
2.3 Directory Service Schema Elements 11
3 Protocol Details 12
3.1 PublishServiceSoap Server Details 12
3.1.1 Abstract Data Model 12
3.1.2 Timers 12
3.1.3 Initialization 12
3.1.4 Message Processing Events and Sequencing Rules 13
3.1.4.1 BeginPublish 13
3.1.4.1.1 Messages 14
3.1.4.1.1.1 BeginPublishSoapIn 14
3.1.4.1.1.2 BeginPublishSoapOut 14
3.1.4.1.2 Elements 14
3.1.4.1.2.1 BeginPublish 14
3.1.4.1.2.2 BeginPublishResponse 15
3.1.4.2 CancelPublish 15
3.1.4.2.1 Messages 15
3.1.4.2.1.1 CancelPublishSoapIn 15
3.1.4.2.1.2 CancelPublishSoapOut 16
3.1.4.2.2 Elements 16
3.1.4.2.2.1 CancelPublish 16
3.1.4.2.2.2 CancelPublishResponse 16
3.1.4.3 EndPublish 16
3.1.4.3.1 Messages 17
3.1.4.3.1.1 EndPublishSoapIn 17
3.1.4.3.1.2 EndPublishSoapOut 17
3.1.4.3.2 Elements 17
3.1.4.3.2.1 EndPublish 17
3.1.4.3.2.2 EndPublishResponse 17
3.1.4.4 GetServiceOptions 17
3.1.4.4.1 Messages 18
3.1.4.4.1.1 GetServiceOptionsSoapIn 18
3.1.4.4.1.2 GetServiceOptionsSoapOut 18
3.1.4.4.2 Elements 18
3.1.4.4.2.1 GetServiceOptions 18
3.1.4.4.2.2 GetServiceOptionsResponse 18
3.1.4.5 PublishData 19
3.1.4.5.1 Messages 19
3.1.4.5.1.1 PublishDataSoapIn 19
3.1.4.5.1.2 PublishDataSoapOut 19
3.1.4.5.2 Elements 19
3.1.4.5.2.1 PublishData 20
3.1.4.5.2.2 PublishDataResponse 20
3.1.4.6 PublishScript 20
3.1.4.6.1 Messages 20
3.1.4.6.1.1 PublishScriptSoapIn 20
3.1.4.6.1.2 PublishScriptSoapOut 21
3.1.4.6.2 Elements 21
3.1.4.6.2.1 PublishScript 21
3.1.4.6.2.2 PublishScriptResponse 21
3.1.5 Timer Events 21
3.1.6 Other Local Events 21
4 Protocol Examples 22
5 Security 25
5.1 Security Considerations for Implementers 25
5.2 Index of Security Parameters 25
6 Appendix A: Full WSDL 26
7 Appendix B: Product Behavior 32
8 Change Tracking 33
9 Index 35
2/2
[MS-SSDPWP] — v20140211
Database Publishing Wizard Protocol
Copyright © 2014 Microsoft Corporation.
Release: Tuesday, February 11, 2014
1 Introduction
The Database Publishing Wizard Protocol is a format that enables communication with an instance of Microsoft SQLServer by using open, industry-standard protocols. By using this format, a publishing session can be initiated, data can be published, and scripts can be executed against an instance of SQLServer.
Sections 1.8, 2, and 3 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. Sections 1.5 and 1.9 are also normative but cannot contain those terms. All other sections and examples in this specification are informative.
1.1 Glossary
The following terms are defined in [MS-GLOS]:
Web Services Description Language (WSDL)
WSDL message
XML
XML namespace
XML schema
The following terms are specific to this document:
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
References to Microsoft Open Specifications documentation do not include a publishing year because links are to the latest version of the documents, which are updated frequently. References to other documents include a publishing year when one is available.
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc-editor.org/rfc/rfc2119.txt
[SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", May 2000, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[SOAP1.2-1/2003] Gudgin, M., Hadley, M., Mendelsohn, N., et al., Eds., "SOAP Version 1.2 Part 1: Messaging Framework", W3C Recommendation, June 2003, http://www.w3.org/TR/2003/REC-soap12-part1-20030624
[WSDL] Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S., "Web Services Description Language (WSDL) 1.1", W3C Note, March 2001, http://www.w3.org/TR/2001/NOTE-wsdl-20010315
[WSDLSOAP] Angelov, D., Ballinger, K., Butek, R., et al., "WSDL 1.1 Binding Extension for SOAP 1.2", W3C Member Submission, April 2006, http://www.w3.org/Submission/2006/SUBM-wsdl11soap12-20060405/
[XMLNS3] World Wide Web Consortium, "Namespaces in XML1.0 (Third Edition)", December2009, http://www.w3.org/TR/2009/REC-xml-names-20091208/
[XMLSCHEMA1] Thompson, H.S., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
[XMLSCHEMA2] Biron, P.V., and Malhotra, A., Eds., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
1.2.2 Informative References
[DPS] Microsoft Corporation, "SQL Server Hosting Web Service (and toolkit): Database Publishing Services", http://sqlhost.codeplex.com/Wiki/View.aspx?title=Database%20Publishing%20Services&referringTitle=Home
[MS-GLOS] Microsoft Corporation, "Windows Protocols Master Glossary".
[MSDN-CRED] Microsoft Corporation, "Credentials (Database Engine)", http://msdn.microsoft.com/en-us/library/ms161950.aspx
[MSDN-Transact-SQLRef] Microsoft Corporation, "Transact-SQL Reference (Database Engine)", http://msdn.microsoft.com/en-us/library/bb510741.aspx
1.3 Overview
The Database Publishing Wizard Protocol enables a user to publish an existing database to a remote server via a web service. This enables database deployment in hosted scenarios without requiring direct access to the database server.
1.4 Relationship to Other Protocols
The Database Publishing Wizard Protocol uses SOAP over HTTP as shown in the following layering diagram.
Figure 1: SOAP over HTTP
The Database Publishing Wizard Protocol uses SOAP over HTTPS as shown in the following layering diagram.
Figure 2: SOAP over HTTPS
1.5 Prerequisites/Preconditions
Before using the Database Publishing Wizard Protocol, it is necessary to install and configure an instance of the Database Publishing Services web service. For more information about how to do this, see [DPS].
1.6 Applicability Statement
The Database Publishing Wizard Protocol is applicable whenever a user wants to deploy a database but the target instance of Microsoft SQLServer is not accessible by using the typical SQLServer client tools, such as SQL Server Management Studio, SQL Server Management Objects (SMO), or Microsoft ADO.NET. The Database Publishing Wizard Protocol allows the deployment to occur via a proxy web service that does have direct access to the target instance of SQLServer.
1.7 Versioning and Capability Negotiation
This document covers versioning issues in the following areas:
§ Supported Transports: This protocol uses multiple transports with SOAP, as specified in section2.1.
§ Protocol Versions: This protocol has a separate Web Services Description Language (WSDL) port type for each version of the protocol. The operations that are available through each port are identical. The two ports support clients using SOAP1.1 and SOAP1.2, respectively.
§ Localization: This protocol includes text strings in various messages. Localization considerations for such strings are specified in sections2.2 and 3.1.4.
§ Capability Negotiation: This protocol does explicit negotiation.
There is currently only one version of the protocol (version1.1). However, clients may confirm that they are communicating with version1.1 by invoking the GetServiceOptions method and then checking the service_version return value.
1.8 Vendor-Extensible Fields
This protocol does not include any vendor-extensible fields.
1.9 Standards Assignments
None.
2 Messages
2.1 Transport
The web service message protocols SOAP1.1, as specified in [SOAP1.1], and SOAP1.2, as specified in [SOAP1.2-1/2003], are supported.
2.2 Common Message Syntax
This section contains common definitions used by this protocol. The syntax of the definitions uses XML schema as defined in [XMLSCHEMA1] and [XMLSCHEMA2] and Web Services Description Language (WSDL) as defined in [WSDL].
2.2.1 Namespaces
This specification defines and references various XML namespaces by using the mechanisms that are specified in [XMLNS3], as listed in the following table. Although this specification associates a specific XML namespace prefix for each XML namespace that is used, the choice of any particular XML namespace prefix is implementation-specific and not significant for interoperability.
Prefix / Namespace URI / Reference /soap / http://schemas.xmlsoap.org/wsdl/soap / [SOAP1.1]
tns / http://schemas.microsoft.com/sqlserver/2006/12/publishing / Appendix A
s / http://www.w3.org/2001/XMLSchema / [XMLSCHEMA1]
soap12 / http://schemas.xmlsoap.org/wsdl/soap12/ / [WSDLSOAP]
targetNamespace / http://schemas.microsoft.com/sqlserver/2006/12/publishing / Appendix A
wsdl / http://schemas.xmlsoap.org/wsdl / [WSDL]
2.2.2 Messages
This specification does not contain any common WSDL messages.
2.2.3 Elements
This specification does not define any common XML schema element definitions.
2.2.4 Complex Types
This specification does not define any common XML schema complex type definitions.
2.2.5 Simple Types
This specification does not define any common XML schema simple type definitions.
2.2.6 Attributes
This specification does not define any common XML schema attribute definitions.
2.2.7 Groups
This specification does not define any common XML schema group definitions.
2.2.8 Attribute Groups
This specification does not define any common XML schema attribute group definitions.
2.3 Directory Service Schema Elements
None.
3 Protocol Details
The client side of this protocol is simply a pass-through. That is, no additional timers or other states are required on the client side of this protocol. Calls made by the higher-layer protocol or application are passed directly to the transport, and the results returned by the transport are passed directly back to the higher-layer protocol or application.