When that finishes, I get the Setup tab, which shows me the configuration and gives me some options.
#Toad for sql server source control code#
I like a subdirectory as this allows me to place other code in the repo if I need it (like notes, readme, etc.) and keep the database code from SQL Source Control clean. I’ll select git and browse to the location where I created the repo. We click Next and get a dialog that asks which VCS and where is our repo. We set up a git repo already, so we’ll leave the top item checked. This shows my database name at the top, and since this database hasn’t been linked, we’ll start with the wizard for linking. This will open the SQL Source Control tab in SSMS. From there, I can right click on the database name and select “Link database to source control”.
If you don’t have that, download an eval and run the setup. I’m going to assume you have SQL Source Control installed already. Now I’ll set up a git repo, which I do with “git init” in the folder. I’ll create a folder under this to store my actual code. I find it easy to keep the folder name the same as my project, which in this case is the database. I’ll then create a folder, called “SQLSourceControlPoC”. I’ll change to those in the command line. On Windows machines, under your use account, you have a Source, and then a Repos set of folders. You can get a client tool, like SourceTree or Github Desktop for Windows, but I like the command line and I’ll use that. The first step is to get a repository set up.
The script for that database is here: SOCPoC_Create.sql. I’ve got a test database set up on a SQL Server 2017 instance, called SQLSourceControlPoC. In a future post, we’ll see a CI build taking place from our Bitbucket repo.
I’ll then connect that to Bitbucket and move changes around.
#Toad for sql server source control how to#
I’m going to start showing how to get a git repo set up locally and connect a database to it with SQL Source Control in this post. Instead, this is part of a series that looks at getting a CI build working. I’m going to assume people can set up an account at Bitbucket and won’t cover that. This is in response to someone asking about getting started with their database in SQL Source Control and then hosting at BitBucket.
0 kommentar(er)
