ࡱ > a Z bjbj͚ I\I\ @ @ D | x =) @ F F F
l 8 D( F( F( F( F( F( F( $ , . * j( j( F F H ( 4 F F D( D( : F F ˿# . 2 ` 0(
) 0 =) . " p . R ` . t j( j( =) . @ > ~ : [MS-ISPAC]: Integration Services Project Deployment File Format
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, IDLs, 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 HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214445" Open Specification Promise or the HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214448" 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 HYPERLINK "mailto:iplg@microsoft.com" iplg@microsoft.com.
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 HYPERLINK "http://www.microsoft.com/trademarks" 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
DateRevision HistoryRevision ClassComments09/03/20100.1NewReleased new document.02/09/20110.1No changeNo changes to the meaning, language, or formatting of the technical content.07/07/20111.0MajorSignificantly changed the technical content.11/03/20111.0No changeNo changes to the meaning, language, or formatting of the technical content.01/19/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.02/23/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.03/27/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.05/24/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.06/29/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.07/16/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.10/08/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.10/23/20121.0No changeNo changes to the meaning, language, or formatting of the technical content.03/26/20131.0No changeNo changes to the meaning, language, or formatting of the technical content.06/11/20131.0No changeNo changes to the meaning, language, or formatting of the technical content.
Contents
TOC \f \h \t "DSTOC1-1,1,DSTOC1-2,2,DSTOC1-3,3,DSTOC1-4,4,DSTOC1-5,5,DSTOC1-6,6,DSTOC1-7,7,DSTOC1-8,8,DSTOC1-9,9,DSTOC2-2,2,DSTOC2-3,3,DSTOC2-4,4,DSTOC2-5,5,DSTOC2-6,6,DSTOC2-7,7,DSTOC2-8,8,DSTOC2-9,9,DSTOC3-3,3,DSTOC3-4,4,DSTOC3-5,5,DSTOC3-6,6,DSTOC3-7,7,DST HYPERLINK \l "_Toc358702062" 1 Introduction PAGEREF _Toc358702062 \h 4
HYPERLINK \l "_Toc358702063" 1.1 Glossary PAGEREF _Toc358702063 \h 4
HYPERLINK \l "_Toc358702064" 1.2 References PAGEREF _Toc358702064 \h 4
HYPERLINK \l "_Toc358702065" 1.2.1 Normative References PAGEREF _Toc358702065 \h 4
HYPERLINK \l "_Toc358702066" 1.2.2 Informative References PAGEREF _Toc358702066 \h 5
HYPERLINK \l "_Toc358702067" 1.3 Overview PAGEREF _Toc358702067 \h 5
HYPERLINK \l "_Toc358702068" 1.4 Relationship to Protocols and Other Structures PAGEREF _Toc358702068 \h 5
HYPERLINK \l "_Toc358702069" 1.5 Applicability Statement PAGEREF _Toc358702069 \h 5
HYPERLINK \l "_Toc358702070" 1.6 Versioning and Localization PAGEREF _Toc358702070 \h 5
HYPERLINK \l "_Toc358702071" 1.7 Vendor-Extensible Fields PAGEREF _Toc358702071 \h 5
HYPERLINK \l "_Toc358702072" 2 Structures PAGEREF _Toc358702072 \h 6
HYPERLINK \l "_Toc358702073" 2.1 Project Deployment File PAGEREF _Toc358702073 \h 6
HYPERLINK \l "_Toc358702074" 2.2 IS Package PAGEREF _Toc358702074 \h 6
HYPERLINK \l "_Toc358702075" 2.3 Project Manifest PAGEREF _Toc358702075 \h 6
HYPERLINK \l "_Toc358702076" 2.3.1 XML Namespace PAGEREF _Toc358702076 \h 6
HYPERLINK \l "_Toc358702077" 2.3.2 Properties PAGEREF _Toc358702077 \h 6
HYPERLINK \l "_Toc358702078" 2.3.3 Property PAGEREF _Toc358702078 \h 7
HYPERLINK \l "_Toc358702079" 2.3.4 Project PAGEREF _Toc358702079 \h 7
HYPERLINK \l "_Toc358702080" 2.3.5 Packages PAGEREF _Toc358702080 \h 9
HYPERLINK \l "_Toc358702081" 2.3.6 Package PAGEREF _Toc358702081 \h 9
HYPERLINK \l "_Toc358702082" 2.3.7 ConnectionManagers PAGEREF _Toc358702082 \h 9
HYPERLINK \l "_Toc358702083" 2.3.8 ConnectionManager PAGEREF _Toc358702083 \h 10
HYPERLINK \l "_Toc358702084" 2.3.9 DeploymentInfo PAGEREF _Toc358702084 \h 10
HYPERLINK \l "_Toc358702085" 2.3.10 PackageInfo PAGEREF _Toc358702085 \h 11
HYPERLINK \l "_Toc358702086" 2.3.11 PackageMetadata PAGEREF _Toc358702086 \h 11
HYPERLINK \l "_Toc358702087" 2.3.12 Parameters PAGEREF _Toc358702087 \h 12
HYPERLINK \l "_Toc358702088" 2.3.13 Parameter PAGEREF _Toc358702088 \h 13
HYPERLINK \l "_Toc358702089" 3 Structure Examples PAGEREF _Toc358702089 \h 15
HYPERLINK \l "_Toc358702090" 4 Security PAGEREF _Toc358702090 \h 19
HYPERLINK \l "_Toc358702091" 4.1 Security Considerations for Implementers PAGEREF _Toc358702091 \h 19
HYPERLINK \l "_Toc358702092" 4.2 Index of Security Fields PAGEREF _Toc358702092 \h 19
HYPERLINK \l "_Toc358702093" 5 Appendix A: XML Schema Definition PAGEREF _Toc358702093 \h 20
HYPERLINK \l "_Toc358702094" 6 Appendix B: Product Behavior PAGEREF _Toc358702094 \h 22
HYPERLINK \l "_Toc358702095" 7 Change Tracking PAGEREF _Toc358702095 \h 23
HYPERLINK \l "_Toc358702096" 8 Index PAGEREF _Toc358702096 \h 24
1 Introduction
This document specifies the file format for the Microsoft SQLServer Integration Services project deployment file, which is a file type that is used to represent the packaged metadata of a data integration HYPERLINK \l "z1" project.
Sections 1.7 and 2 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. All other sections and examples in this specification are informative.
1.1 Glossary
The following terms are defined in HYPERLINK "[MS-GLOS].pdf" [MS-GLOS]:
globally unique identifier (GUID)XML namespace
The following terms are specific to this document:
Integration Services (IS) package: A module of a project. The module contains control flow and data flow, as specified in HYPERLINK "[MS-DTSX].pdf" [MS-DTSX].
Open Packaging Conventions (OPC) package: A logical entity that holds a collection of parts, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=150883" [ISO/IEC 29500-2:2008].
part: A stream of bytes with a MIME content type and associated common properties, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=150883" [ISO/IEC 29500-2:2008].
project: A collection of IS packages that are developed and deployed as a unit.
project manifest: The metadata that describes the properties of a project as well as its contents.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=145494" [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 HYPERLINK "mailto:dochelp@microsoft.com" dochelp@microsoft.com. We will assist you in finding the relevant information. Please check the archive site, HYPERLINK "http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624" http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624, as an additional source.
[FIPS46-2] National Institute of Standards and Technology, "Federal Information Processing Standards Publication 46-2: Data Encryption Standard (DES)", December 1993, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=89871" http://www.itl.nist.gov/fipspubs/fip46-2.htm
[ISO/IEC 29500-2:2008] Information technology -- Document description and processing languages -- Office Open XML File Formats -- Part 2: Open Packaging Conventions, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=150883" http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=51459
[MS-DTSX] Microsoft Corporation, " HYPERLINK "[MS-DTSX].pdf" Data Transformation Services Package XML File Format".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" http://www.ietf.org/rfc/rfc2119.txt
1.2.2 Informative References
[MS-GLOS] Microsoft Corporation, " HYPERLINK "[MS-GLOS].pdf" Windows Protocols Master Glossary".
1.3 Overview
This document specifies the file format for the Microsoft SQLServer Integration Services project deployment file, a file type that is used to represent the packaged metadata of a data integration project.
The project deployment file is an implementation of Open Packaging Conventions (OPC). The project deployment file contains one or more HYPERLINK \l "z2" Integration Services (IS) packages and one HYPERLINK \l "z5" project manifest.
Each IS package is represented as one OPC HYPERLINK \l "z4" part. The part is uniquely identified by a URI formatter part name. The part contains an IS package file in the .dtsx file format that is specified in HYPERLINK "[MS-DTSX].pdf" [MS-DTSX]. The content type of the part is text/xml.
The project manifest is an OPC part of content type text/xml. A project deployment file must have a part that contains the project manifest. The project manifest contains metadata that describes the project properties, project parameter, and deployment metadata for each of the contained IS packages.
1.4 Relationship to Protocols and Other Structures
The project deployment file format can be used as a payload in protocols that support the transport of binary data.
1.5 Applicability Statement
The project deployment file format is applicable for use in a standalone representation of project metadata, for deploying a project from a client to a server, or for extracting a project from a server to a client.
1.6 Versioning and Localization
This document describes version1.0 of the project deployment file format. There are no localization-dependent structures in the project deployment file format.
1.7 Vendor-Extensible Fields
Extensions to the file format that is specified in this document are not allowed. Tools that process this format do not have to preserve unrecognized structures when loading or persisting.
2 Structures
2.1 Project Deployment File
A project deployment file is an implementation of an Open Packaging Conventions (OPC) package. The file MUST contain the following parts:
O n e p a r t t h a t c o n t a i n s a p r o j e c t m a n i f e s t .
Z e r o o r m o r e p a r t s t h a t c o n t a i n a n I S p a c k a g e .
2 . 2 I S P a c k a g e
A n I S p a c k a g e i s s t o r e d a s o n e O P C p a r t i n t h e p r o j e c t d e p l o y m e n t f i l e . T h e f o l l o w i n g r u l e s a p p l y t o t h e p a c k a g e :
T h e c o n t e n t t y p e o f t h e p a r t M U S T b e t e x t / x m l .
T h e p a r t d a t a s t r e a m M U S T c o n t a i n e x a c t l y o n e i n s t a n c e o f a f i l e i n . d t s x f o r m a t H Y P E R L I N K " [ M S - D T S X ] . p d f " [ M S - D T S X ] r e p r e s e n t i n g o n e I S p a c k a g e .
T h e p a r t M U S T h a v e a u n i q u e p a r t n a m e w i t h i n t h e H Y P E R L I N K \ l " z 3 " O P C p a c k a g e .
T h e p a r t n a m e U R I M U S T N O T c o n t a i n t h e a t s i g n ( @ ) .
T h e p a r t n a m e U R I M U S T b e a r o o t U R I ; s u b f o l d e r s a r e n o t a l l o w e d .
T h e p a r t n a m e f i l e n a m e e x t e n s i o n M U S T b e . d t s x .
2 . 3 P r o j e c t M a n i f e s t
T h e p r o j e c t m a n i f e s t s p e c i f i e s t h e p r o p e r t i e s , p a r a m e t e r s , a n d d e p l o y m e n t i n f o r m a t i o n f o r a p r o j e c t . T h e p r o j e c t m a n i f e s t i s s t o r e d a s a d a t a s t r e a m i n a n O P C p a r t o f t h e p r o j e c t d e p l o y m e n t f i l e . T h e f o l l o w i n g r u l e s a p p l y t o t h e p r o j e c t m a n i f e s t :
T h e p a r t n a m e M U S T b e @ P r o j e c t . m a n i f e s t .
T h e c o n t e n t t y p e o f the part MUST be text/xml.
2.3.1 XML Namespace
The project manifest part contains an XML structure. The namespace URI for the project manifest XML structure is www.microsoft.com/SqlServer/SSIS.
2.3.2 Properties
The Properties element specifies a list of the HYPERLINK \l "zebd177d88a8b436db2343b4a8c3c55b1" Property elements.
The following is the child element of the Properties element.
Child elements HYPERLINK \l "zebd177d88a8b436db2343b4a8c3c55b1" PropertyThe Properties element schema is specified by the PropertiesType type. The following is the XML schema definition of the PropertiesType type.
2.3.3 Property
The Property element specifies the value of one property of an object such as a project, an IS package, or a parameter.
The Property element has a Name attribute of type string that specifies the name of the property.
The Property element schema is defined by the PropertyType type. The following is the XML schema definition of the PropertyType type.
2.3.4 Project
The Project element is the root element of the project manifest.
The Project element MUST have the following attribute.
AttributeTypeDescriptionProtectionLevelStringSpecifies the protection level of the project. The protection level MUST be one of the following values:
EncryptAllWithUserKey
EncryptAllWithPassword
EncryptSensitiveWithUserKey
EncryptSensitiveWithPassword
DontSaveSensitive
ServerStorage
All IS packages in the project MUST be serialized by using the same protection level as specified for the project. The following child elements MUST be specified in the Project element.
Child elements HYPERLINK \l "z374b47f9afdd48f68764aa7d2b99f80e" Properties HYPERLINK \l "z075ee26b388944da96c2d23d8cc37baf" Parameters HYPERLINK \l "za83cd6714dac4ec1b66ae37b024e3430" Packages HYPERLINK \l "z833c6617c86842b69fe97031464b609a" ConnectionManagers HYPERLINK \l "z734af1c58a8b405daa3aad5c9cd72a56" DeploymentInfoThe following is the XML schema definition of the Project element.
The Project element MUST contain a Properties child element. The Properties child element, in turn, MUST contain a list of HYPERLINK \l "zebd177d88a8b436db2343b4a8c3c55b1" Property elements for each Project property that is listed in the following table.
PropertyValueDescriptionIDGuidSpecifies the GUID that is assigned to the project.NameStringSpecifies the name of the project.DescriptionStringSpecifies the description of the project.VersionMajorPositive integerSpecifies the major version of the project.VersionMinorPositive integerSpecifies the minor version of the project.VersionBuildPositive integerSpecifies the build version of the project.VersionCommentsStringSpecifies comments for the version of the project.VersionGUIDGuidSpecifies the GUID of the version of the project.CreationDateDateTimeOffsetSpecifies the date, time, and time zone offset of the time when the project was created.2.3.5 Packages
The Packages element specifies an ordered list of HYPERLINK \l "z6f59094db692429bb86741b957672789" Package elements. The Packages element MUST contain a child Package element for each IS package in the project deployment file.
The following is the child element of the Packages element.
Child elements HYPERLINK \l "z6f59094db692429bb86741b957672789" PackageThe Packages element schema is specified by the PackagesType type. The following is the XML schema definition of the PackagesType type.
2.3.6 Package
The Package element specifies an IS package that is included in the project deployment file.
The Package element MUST have the following attributes.
AttributeTypeDescriptionEntryPointBooleanSpecifies whether the IS package is a project entry point for execution. Possible values are:
1 The IS package is an entry point.
0 The IS package is not an entry point.NameStringSpecifies the name of the IS package. This name MUST match the part name of the corresponding OPC part.The Package element schema is specified by the PackageType type. The following is the XML schema definition of the PackageType type.
2.3.7 ConnectionManagers
The ConnectionManagers element specifies an ordered list of HYPERLINK \l "z008637cab6fc45e6b50466fda5c1a5c8" ConnectionManager elements. A ConnectionManager element MUST exist for each connection manager (.conmgr) file that exists in the project deployment file.
The following is the child element of the ConnectionManagers element.
Child elementsConnectionManagerThe ConnectionManagers element schema is specified by the ConnectionManagersType type. The following is the XML schema definition of the ConnectionManagersType type.
2.3.8 ConnectionManager
The ConnectionManager element specifies an IS connection manager that is included in the project deployment file.
The ConnectionManager element MUST have the following attributes.
AttributeTypeDescriptionNameStringSpecifies the name of the IS connection manager. This name MUST match the part name of the corresponding OPC part.
2.3.9 DeploymentInfo
The DeploymentInfo element is an ordered list of HYPERLINK \l "zb683bee93e014be3a125b4402e0ab6aa" PackageInfo elements. A PackageInfo element MUST be specified for each IS package that is included in the project.
The following is the child element of the DeploymentInfo element.
Child elements HYPERLINK \l "zb683bee93e014be3a125b4402e0ab6aa" PackageInfoThe DeploymentInfo element schema is specified by the DeploymentInfoType type. The following is the XML schema definition of the DeploymentInfoType type.
2.3.10 PackageInfo
The PackageInfo element contains the metadata for an IS package that is contained in a project. The PackageInfo element MUST specify exactly one HYPERLINK \l "za3a0375871e14c7bb8cbf4d125de7bb8" PackageMetadata element.
The following is the child element of the PackageInfo element.
Child elements HYPERLINK \l "za3a0375871e14c7bb8cbf4d125de7bb8" PackageMetadataThe PackageInfo element schema is specified by the PackageInfoType type. The following is the XML schema definition of the PackageInfoType type.
2.3.11 PackageMetadata
The PackageMetadata element contains the metadata for an IS package contained in the project, including the core IS package properties and the IS package parameters.
The PackageMetadata element MUST specify the following attribute.
AttributeTypeDescriptionNameStringSpecifies the name of the IS package. This name MUST match the part name of the corresponding OPC part.The PackageMetadata element MUST specify the following child elements.
Child elements HYPERLINK \l "z374b47f9afdd48f68764aa7d2b99f80e" Properties HYPERLINK \l "z075ee26b388944da96c2d23d8cc37baf" ParametersThe PackageMetadata element schema is specified by the PackageMetadataType type. The following is the XML schema definition of the PackageMetadataType type.
The PackageMetadata element MUST contain a Properties child element. The Properties child element, in turn, MUST contain a list of HYPERLINK \l "zebd177d88a8b436db2343b4a8c3c55b1" Property elements for each PackageMetadata property that is listed in the following table.
PropertyValueDescriptionIDGuidSpecifies the GUID that is assigned to the IS package.NameStringSpecifies the name of the IS package.DescriptionStringSpecifies the description of the IS package.ProtectionLevelIntegerSpecifies an integer value. The value MUST be one of the following:
0 DontSaveSensitive
1 EncryptAllWithPassword
2 EncryptAllWithUserKey
3 EncryptSensitiveWithPassword
4 EncryptSensitiveWithUserKey
5 ServerStorageVersionMajorPositive integerSpecifies the major version of the IS package.VersionMinorPositive integerSpecifies the minor version of the IS package.VersionBuildPositive integerSpecifies the build version of the IS package.VersionCommentsStringSpecifies comments of the version of the IS package.VersionGUIDGuidSpecifies the GUID of the version of the IS package.2.3.12 Parameters
The Parameters element specifies an ordered list of HYPERLINK \l "zca535c432df942189c0963dd6f233fdd" Parameter elements that declare the parameters of a project or an IS package.
The following is the child element of the Parameters element.
Child elements HYPERLINK \l "zca535c432df942189c0963dd6f233fdd" ParameterThe Parameters element schema is specified by the ParametersType type. The following is the XML schema definition of the ParametersType type.
2.3.13 Parameter
The Parameter element specifies one parameter of a project or an IS package.
The Parameter element MUST have the following attribute.
AttributeTypeDescriptionNameStringSpecifies the name of the parameter. The following is the child element of the Parameter element.
Child elements HYPERLINK \l "z374b47f9afdd48f68764aa7d2b99f80e" PropertiesThe Parameter element schema is specified by the ParameterType type. The following is the XML schema definition of the ParameterType type.
The Parameter element MUST contain a Properties child element. The Properties child element, in turn, MUST contain a list of HYPERLINK \l "zebd177d88a8b436db2343b4a8c3c55b1" Property elements for each Parameter property that is listed in the following table.
PropertyValueDescriptionIDGuidSpecifies the GUID that is assigned to the parameter.DescriptionStringSpecifies the description of the parameter.RequiredBooleanSpecifies whether the value is required.
T r u e s p e c i f i e s t h a t t h e p a r a m e t e r i s r e q u i r e d .
F a l s e s p e c i f i e s t h a t t h e p a r a m e t e r i s n o t r e q u i r e d . S e n s i t i v e B o o l e a n S p e c i f i e s w h e t h e r t h e v a l u e i s s e n s i t i v e .
T r u e s p e c i f i e s t h a t t h e p a r a m e t e r i s s e n s i t i v e .
F a l s e s p e c i f i e s t h a t t h e p a r a m e t e r i s n ot sensitive.DefaultValueStringSpecifies the serialized value of the parameter.
If the project protection level is EncryptSensitiveWithPassword or EncryptSensitiveWithUserKey, the value MUST be encrypted by using a triple Data Encryption Standard (DES) encryption algorithm HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=89871" [FIPS46-2] that uses the corresponding encryption key. The encrypted value then MUST be encoded by using base64 encoding. DataTypeIntegerSpecifies that the value MUST be one of the following:
3 Boolean
5 SByte
6 - Byte
9 Int32
10 Uint32
11 Int64
12 Uint64
13 Single
14 Double
16 DateTime
18 String 3 Structure Examples
The following is an example of a typical project manifest for a project deployment file, including all the mandatory elements and examples of property, parameter, and connection manager declarations.
{dd0733bd-0382-4511-91d3-ed34210d5469}
DWLoad
1
0
1
06/22/2010 01:13:02 -07:00
MYDOMAIN\user1
MyServer
0
{169F8551-25AA-4D90-B9FD-39C8F1A0E363}
MasterControl
1
0
3
{D95E1FD4-E1BC-4BD3-84BD-7ECE2C48C2EF}
4
1
{21B7E59E-62B5-44E8-AF1C-FF7A8A78B225}
0
1
1
AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAT1admM5G+EmCVt6OOLna+QAAAAACAAAAAAADZgAAwAAAABAAAACyXjYXsjUrMnUPBsjleDKAAAAAAASAAACgAAAAEAAAADZUUCbG8oqLjVx1OamH8CJAAAAAmDJujhbCxEtBq6FiRAvzq3BGVACvLGW3OPkgIDkSv5woRpotOhXZyCkMZsP6kJvt/FKVdIXwF/qDfY//ijG/ahQAAAAimi6gMlFu1RSRzUFMK2WSodk75w==
18
{1D86BA36-9FAC-43BA-9784-CCF54C502E8A}
0
1
0
DevDWSRV
18
{76C82FBC-B4A7-4FE7-9CDA-DAF2446DF85A}
0
1
0
DevAcct
18
{9E54B3C5-F3CF-42A6-8427-994D15C5B6E8}
0
0
0
0
9
{7CDBB704-93D6-43B8-B2BD-EBEA57862072}
LoadCustomerDim
1
0
1
{7962C979-1C76-4EE1-BD90-B33A12687A67}
4
1
{A502C05C-A08A-4A76-A960-15F37F070DA5}
LoadProductDim
1
0
1
{B3DF69C4-309F-400B-8850-87FFE481AD95}
4
1
{D6794D56-2A03-43C0-B47E-69F43DA13C42}
LoadSalesFact
1
0
1
{9E2587D4-765C-44D5-B9FD-1C0BD4C3E2CC}
4
1
{D30FBC74-FD46-4918-8908-D33707426F30}
Cleanup
1
0
2
{A18DA090-0A36-4289-85F8-FD5E5C6B3E66}
4
1
{A4A0E563-A0F3-4C82-8378-5785E9F142E6}
0
0
0
1899-12-30T00:00:00-08:00
16
{65E8AE90-50EB-495F-BED3-67CF648372BC}
0
0
0
false
3
4 Security
4.1 Security Considerations for Implementers
The project deployment file can contain sensitive information, such as deployment configurations that define user names and passwords that are used to access data sources.
When sensitive values are present in a project or its IS packages, the user should use the appropriate protection level for serialization, as described in this document and in HYPERLINK "[MS-DTSX].pdf" [MS-DTSX].
4.2 Index of Security Fields
None.
5 Appendix A: XML Schema Definition
The following is the complete XML schema definition for the project deployment file format.
6 Appendix B: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:
M i c r o s o f t S Q L S e r v e r 2 0 1 2
E x c e p t i o n s , i f a n y , a r e n o t e d b e l o w . I f a s e r v i c e p a c k o r Q u i c k F i x E n g i n e e r i n g ( Q F E ) n u m b e r a p p e a r s w i t h t h e p r o d u c t v e r s i o n , b e h a v i o r c h a n g e d i n t h a t s e r v i c e p a c k o r Q F E . T h e n e w b e h a v i o r a l s o a p p l i e s t o s u b s e q u e n t s e r v i c e p a c ks of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
7 Change Tracking
B X c ' 8
! \ ] n o X Y 0 F / 0 Z [ k l 9 : n o < =
q r } ~ hE h9` h9` 5j h.:b h9` 0J U
h9` 0J j h9` U
h9` 0Jh h9` M A B X ' 0 & / $If gd~a gd9` [ gd9` gd9` gd9` gd9` / 0 ; ? , # # $If gd~a kd $$If V 4 \
oE#
t ( 0 (#6 4 4
a p( yt9` ? C Z [ f j t ? kd$ $$If V \
oE#
t 0 (#6 4 4
a p( yt9` $If gd~a H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` k H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` k l w { H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` 9 H ? ? ? ? $If gd~a kdH $$If V \
oE#
t 0 (#6 4 4
a p( yt9` 9 : E I S H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` ! n H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9` n o z ~ H ? ? ? ? $If gd~a kdl $$If V \
oE#
t 0 (#6 4 4
a p( yt9` < H ? ? ? ? $If gd~a kd5 $$If V \
oE#
t 0 (#6 4 4
a p( yt9` < = H L V H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9`
H ? ? ? ? $If gd~a kd $$If V \
oE#
t 0 (#6 4 4
a p( yt9`
$ q H ? ? ? ? $If gd~a kd
$$If V \
oE#
t 0 (#6 4 4
a p( yt9` q r s t } ( H C > > <