From the course: DevOps for the Database with TFS 2018
Unlock the full course today
Join today to access over 22,400 courses taught by industry experts or purchase this course individually.
Local deployments
From the course: DevOps for the Database with TFS 2018
Local deployments
- [Instructor] At this point, we've worked with our database project very quickly offline. But one of the things we noticed is that we were making changes to some text files on our hard drive. It wasn't changing SQL Server. What we want to be able to do then is take our changes and get 'em into SQL Server and see the results of our work. To do that, we're going to do an F5. F5 being the default shortcut key of Visual Studio to build and run. With SSDT, that effectively means doing a deployment or publishing our project into an SQL Server instance. This allows up to deploy and validate our work and possibly do tests. I typically recommend that people use a local SQL Server Developer Edition copy for their private F5 deployments. And then later, we're going to do deployments again in a shared dev environment, but we're going to do it with Team Build. So let's take a look at how we can do F5 deployments to a local copy of SQL Server.
Contents
-
-
-
-
Why version control?1m 45s
-
Tracking your work49s
-
Team project setup: Demo5m 6s
-
Backlog: Demo7m 20s
-
Team Foundation Version Control (TFVC) vs. Git3m 24s
-
Version control your SQL Server database1m 42s
-
Sample database installation2m 28s
-
Version control your SQL DB with Git: Demo set up6m 38s
-
Version control your SQL DB with Git: Demo import database9m 49s
-
Version control your SQL DB with Git: Demo set up another user2m 35s
-
Version control your SQL DB with Git: Demo share changes5m 4s
-
Version control your SQL DB with TFVC: Demo set up and import7m 49s
-
Version control your SQL DB with TFVC: Share changes5m 29s
-
Branching and merging1m 2s
-
Local deployments1m 8s
-
Local deployments: Demo5m
-
Dealing with drift1m
-
Dealing with drift: Demo4m 40s
-
-
-
-
-
-