NOTE Visual Studio 2022 version 17.7 introduced native support by SSDT for Serverless SQL pool.
This repository contains a sample console application that builds DACPAC files for Synapse Serverless SQL pool from SQL source files.
The DACPAC file generated by the tool can be published to Synapse Serverless SQL pool using SqlPackage.
The tool builds a DACPAC file (also referred to as package) based on the SQL files under a specified folder (also referred to as source or root folder).
The source folder is scanned recursively and all files with .sql
extension are added to the package.
The tool processes the current folder, unless specified otherwise with the --source
option.
The name of the DACPAC file can be set using the --output
option, with a default of ./package.dacpac
.
You can also specify a name to be added to the package's metadata using the --name
option, with a default of package
.
Description:
SynapseServerlessDacpacBuilder
Usage:
SynapseServerlessDacpacBuilder [options]
Options:
-s, --source <source> Root path of the SQL source code. [default: .]
-o, --output <output> Path of the output DACPAC file. [default: ./package.dacpac]
-n, --name <name> Name of the package to be included in its metadata. [default: package]
--version Show version information
-?, -h, --help Show help and usage information
Requirements:
To build the project run:
dotnet build
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.