SQL Server File Formats Technical Documents
This section provides information about the file format technical documents that are contained in the Microsoft SQL Server Data Portability documentation set.
Note The inter-document links in a PDF version of a technical document are functional only if all the cross-referenced documents are saved to the same local directory folder. An error message appears if you click a link that references a PDF document that is not located in the same folder (when viewing via your local hard drive) or is part of a different download (when viewing online). To save a complete set of PDF files to the same folder, download the SQL Server Data Portability .zip file.
|
Specification |
Description |
|---|---|
|
Specifies the Bulk Copy (BCP) Format, a data structure format that specifies how different database data type values are stored in a data file for the purpose of exporting and importing large sets of values. |
|
|
[MS-CONNMGR]: Integration Services Connection Manager File Format |
Specifies the SQL Server Integration Services connection manager file, which is a file type that is used to store the metadata for a project connection manager. |
|
[MS-CSDLBI]: Conceptual Schema Definition File Format with Business Intelligence Annotations |
Specifies the structure and semantics of conceptual schema definition language (CSDL) annotations that are used in business intelligence (BI) applications. |
|
Specifies the file format of XML parts in a data-tier application (DAC) package (a .dacpac file) by using XML schema definitions. |
|
|
Specifies the Data Transformation Services (DTS) package file format, which is the file format that is used to write to and read from a DTS package file. The DTS package file format is used to persist DTS packages in the Windows file system. |
|
|
[MS-DTSX]: Data Transformation Services Package XML File Format |
Specifies the Data Transformation Services Package File Format (DTSX), which is an XML-based file format that stores the instructions for the processing of a data flow from its points of origin to its points of destination, including transformations and optional processing steps between the origin and destination points. |
|
[MS-DTSX2]: Data Transformation Services Package XML Version 2 File Format |
Specifies version 2 of the Data Transformation Services Package File Format (DTSX), which is an XML-based file format that stores the instructions for the processing of a data flow from its points of origin to its points of destination, including transformations and optional processing steps between the origin and destination points. |
|
[MS-ISPAC]: Integration Services Project Deployment File Format |
Specifies the file format for the SQL Server Integration Services project deployment file, which is a file type that is used to represent the packaged metadata of a data integration project. |
|
Specifies the file format of the mapping specification language (MSL) for the Entity Data Model (EDM) version 2.0. MSL is an XML-based language that can be used to define mapping between a conceptual schema and a store schema. |
|
|
[MS-RDLRS]: Report Definition Language Report State File Format |
Specifies the file format for Report State. A Report State document represents the metadata for defining filters in a report that is in Report Definition Language (RDL) file format and storing information about interactions with those filters. |
|
Specifies the file format for SQL Server Semantic Model Definition Language (SMDL), a file type that is used to represent the metadata for defining a semantic model. |
|
|
Specifies the structure and semantics of the store schema definition language (SSDL) for the Entity Data Model (EDM). SSDL is a language based on XML that can be used for defining storage models by using the EDM. |
|
|
[MS-SSISPARAMS]: Integration Services Project Parameter File Format |
Specifies the SQL Server Integration Services project parameter file, which is a file type that is used to store the metadata for a project connection manager. |
Preview Versions
From time to time, Microsoft may publish a preview, or pre-release, version of an Open Specifications technical document for community review and feedback. To provide feedback for a preview version of a technical document, please follow the instructions for that document, if provided. Otherwise, you can provide feedback by using the Open Specification Forums.
The preview period for a technical document varies. Additionally, not every technical document will be published for preview.
After the preview period, the technical document is published to the appropriate location in the Open Specifications Library.