The original article describing this approach recommends copying the extension's BuildDirectory folder somewhere to make your scripts independent of the extension, which might be necessary for build servers where no ADS is present. This folder contains the ingredients which allows msbuild to cope with. On macOS this folder is usually /Users//.azuredatastudio/extensions/microsoft.sql-database-projects-0.4.1/BuildDirectory.

The one interesting part is the /p:NETCoreTargetsPath parameter, which points to the SQL Database Projects extension folder from the last section. NET 5.0 if you not already have as we're going to facilitate the dotnet CLI.Ī database project build is now just a few keystrokes away:Įnter fullscreen mode Exit fullscreen mode If you want to automate things, or if you prefer to work in the shell, or like to run a local MSSQL instance for developing purposes read ahead.ĭownload and install. That's all required for working with MSSQL database projects in macOS (and Linux) from the safety of an IDE with publishing targets somewhere in the cloud. Once installed open the extensions view, search for SQL Database Projects (preview version 0.4.1 at time of writing) and install it as well. If you're already familiar with VS Code, then you'll quickly feel at home with ADS too. Its recent SQL Database Projects extension turns it into a full IDE for MSSQL database projects including build and deployment capabilities.ĭownload and install ADS.

Until recently developing MSSQL database projects was only possible with Visual Studio in conjunction with the SQL Server Data Tools (SSDT).Īzure Data Studio (ADS) is a cross-platform SQL Server Management Studio (SSMS) replacement and provides a similar set of features. Requirements: Basic knowledge of SSDT, dotnet CLI, and docker.ĭevelop, Build & Publish Database Projects in ADS This post summarizes the steps required to prepare the tools for macOS. Thanks to a curiosity-driven investigation of one of my colleagues it turns out that the complete toolchain is available now cross-platform which enables us to build and deploy DACPACs on Linux and macOS alike. Our team successfully applied the target-state deployment approach for quite a while and never saw the need for an alternative migration script-based approach (which would not have the Windows platform limitation). The reason for the latter is the lack (so far) of cross-platform tooling for building Visual Studio database projects and deploying the resulting DACPACs. In my day to day work as a consultant on customer projects the typical tech stack involves having a Microsoft SQL Server (MSSQL) for persistence with several ASP.NET Core web APIs on top, and a web-based UI, which nowadays I like writing in React.īeing in home office mode for several months now, I am developing on my personal MacBook Pro - in a Parallels Windows VM.

Microsoft sql server data tools for mac