We can apply the CI\/CD methodology to Azure SQL Database change management by giving developers personal environments to work in, repositories for a common code base, detailed and thorough automated testing, and a feedback process that encourages good coding standards. While a very lofty goal, this series of articles will help guide you in creating these conditions for development success.<\/span><\/p>\n The next few articles will cover:<\/p>\n What does the development environment look like and how do you start with Azure SQL CICD? Your Operating System really does not matter too much but just so we can have a consistent story here, let’s use Windows 11 as our base. What else do we need? Here is a checklist:<\/p>\n According to the Stack Overflow 2022 Developer Survey<\/a>, many of these tools are very popular with developers and you probably have them installed already.<\/p>\n <\/i>Complete before moving on<\/strong><\/p>These posts will be using GitHub. Please ensure that you have set up a connection to GitHub using either SSH or 2FA (Two Factor Authentication) after you have created an account or with your existing account.<\/div><\/p>\n Now that we have everything we need, it’s time to start putting the Azure SQL CICD pieces together. The first step is to create a GitHub repository that we will use for our database code.<\/p>\n Once you have the GitHub account, simply click the New<\/strong> button on the GitHub home page<\/p>\n Or click on your profile picture in the upper right of the page and select Your repositories<\/strong>.<\/p>\n Then, on the repository page, click the New<\/strong> button in the upper right.<\/p>\n On the Create a new repository<\/strong> page, select your GitHub user as the owner and name the repository AzureCICD<\/strong>.<\/p>\n I usually also add a README<\/strong> file as well, so check the box next to Add a README file.<\/p>\n Then on the bottom of the page, click Create repository<\/strong>. That’s it! You have a new GitHub repository ready to go for our Azure Database CICD journey.<\/p>\n Last step is to clone this repository to your local computer so that we can put our work in there and push it up to the repository. On the new repository page, click the <> Code<\/strong> green button.<\/p>\n Now, in the code box, select the Local<\/strong> tab if not already selected and then the SSH<\/strong> option.<\/p>\n Then click the copy icon<\/strong> to the right of the git@github command.<\/p>\n We now need to clone this repository from GitHub to our local environment. Yes, you can use a command prompt\/terminal shell\/etc but we are going to see why everyone loves Visual Studio Code so much. Open Visual Studio Code<\/strong> and on the bottom, click the Terminal<\/strong> tab (If the tabs are not at the bottom of Visual Studio Code, you can use the Terminal Menu on the top and choose New Terminal).<\/p>\n I have a directory at the top level of my C: drive for git repositories. You can use any directory you wish here but which ever one you use, enter that directory and run the following code (The git@github section will be the code you just copied from the GitHub UI with the copy icon And the project is now cloned to your local environment.<\/p>\n <\/p>\n Next is setting up Visual Studio Code for Azure SQL CICD. With Visual Studio Code still open from using the terminal, go to the extensions tab on the left.<\/p>\n Using the Search Extensions in Marketplace<\/strong> bar, search for mssql<\/strong>. Once you find the SQL Server (mssql) extension, click the install<\/strong> blue button.<\/p>\n This will install a few extensions, most importantly the SQL Database Projects extension. You can see the new extensions on the left of the Visual Studio Code window.<\/p>\n We are going to start with Database Projects. Just simply click the extension to bring up the Database Projects panel. Here, click the Create New button.<\/p>\n This will start the dialog boxes for creating a Database Project in the middle top of the Visual Studio Code window. The first question is Select Database Project Type<\/strong>. Select Azure SQL Database<\/strong>.<\/p>\n Next we can enter the projects name. Let’s use Employee App<\/strong>.<\/p>\n When asked to Select Project Locatio<\/strong>n, use the Browse<\/strong> option to find our GitHub repository folder we previously cloned.<\/p>\n Choose Yes<\/strong> for SDK-style projects<\/strong>.<\/p>\n And if you get a warning about trusting the files in the folder, select Yes<\/strong>.<\/p>\n\n
Where Do I Start?<\/h2>\n
\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/bigPic1-scaled.jpg\")
<\/a><\/p>\nCreate a GitHub Repository<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git1-copy.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git2.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git3.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git4.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git5.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git6.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git7.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git8.png\")
<\/a><\/figure>\nClone the Repository<\/h3>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/gitTerm1.png\")
<\/a><\/figure>\n<\/a><\/strong>):<\/p>\ngit clone git@github.com:YOUR_GITHUB_USERNAME\/AzureCICD.git<\/pre>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git9.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/git10.png\")
<\/a><\/figure>\nSetting up Visual Studio Code<\/h2>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext1.png\")
<\/a><\/figure>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext2.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext3.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext4.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext5.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext6.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext7.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext8.png\")
<\/a><\/p>\n
![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext9.png\")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/azure-sql\/wp-content\/uploads\/sites\/56\/2022\/10\/ext10.png\")
<\/a><\/figure>\n