1: Using this repository

o use this repository you can first import it into Azure DevOps.

There are a number of ways you can do this. For example, you can import the repository directly into Azure Repos within Azure DevOps.

Once done, you can either of the YAML files in the AzureDevOpsTemplates folder as a new pipeline. In fact, it is perfectly feasible to add both as different pipelines as they are both currently set to be triggered manually.

I cover in another blog post how to connect a Database Project in Azure Repos to Azure Pipelines.

If you are going to use either of the pipelines for testing then you will need to create at least one variable group. Ideally two variable groups, with the sensitive values stored in Azure Key Vault.

At the very least you will need the below variables configured:

• BuildConfiguration - Configuration for build (Dev, Test, Release, etc)
• SQLDBartifactname - A name for the created artifact
• AzureSubscription - A reference to an Azure subscription is required for the task to work, can be any one as will not be used
• DestSQLConnString - The connection string for the destination SQL Database in Fabric (including the credentials, as per the post)
• DestinationDB - The name of the SQL Database in Fabric
• Targetfile - Name of the dacpac file created (default is same name as .sqlproj file)

Optional variable:

• agentpool - The name of the agent pool you want to use (ideally a self-hosted pool with latest sqlpackage installed)