#AZURE DATA STUDIO GITHUB CODE#
However, I find code committed all the time that a developer hasn't tested well, so this mimics what you'll find in the real world. Note: This isn't a good flow, as the code isn't really ready to go. In this case, when I started this article, I was in the middle of explaining some changes to another person and needed to save those changes. I haven't explained much, but this is the flow of changing code and then including those change in your repository.
I'll enter a commit message in the upper right edit box and click the check mark above this to commit the change. I added and ORDER BY to this script (using pseudo code). I can click the file name and I get a diff view in the main code space that shows me the changes. In this case, I see that the file, GlennBerry_2017Diagnostic_5.sql, is in the staged status. If I click the source control icon in the right menu, I'll get that blade open and I can see the change that's uncommitted. I still see the main screen, but as the screen show below shows, I have an uncommitted change in my Git repository. When I click Open, the shell reloads this folder and the server connections blade opens. I'll click the button and then select a folder that contains a Git repository with a number of scripts. The way to open a repository to work with it is to use the File | Open Folder link or use the button on the main screen that appears when you start ADS. I've written a getting started article you can read to understand a bit more about Git. Git provides capabilities to help you track and audit script changes over time. This seems like an extra step to many DBAs, but it really isn't. This is where I can work with any of the changes I've made to code and commit them to my git repository. You can see it in the image below, the second from the bottom icon with the pointer hovering over it.
If we look at the ADS sidebar, there is a VCS icon, which looks like a git branch graph, two connected curved lines with circles at the ends. This is unlike SSMS, which is based on Visual Studio, but doesn't have a lot of the VS capabilities, including version control features.
Git support was built into VS Code, and it wasn't disabled in ADS. A Dedicated PaneĪDS is built on Visual Studio Code, which is a tool I use often for non-SQL work. This post continues my look at Azure Data Studio (ADS) with an examination of the version control features built into the product. This is important to protect code, allow us to undo problem changes by finding old code, and ensuring that all changes made by a team are captured in a central place.
#AZURE DATA STUDIO GITHUB SOFTWARE#
One of the more important things that I think we should be doing as software developers is maintaining our changes in some sort of version control system (VCS).
0 kommentar(er)
