Join Brian Randell for an in-depth discussion in this video End-to-end demo, part of DevOps for the Database with TFS 2018.
- [Instructor] If you take the time to watch this entire course you'll be able to do the following. Imagine a Northwind database that has tables, views and even stored procedures. You'll be able to go into visual studio, take that database, put it under version control note the little lock icons. You'll be able to come over to a table, like products, add a new field.
Have that field added to the definition for the table. You'll be able to commit your changes to version control. In this case you'll see an example of Git but we also show you some examples of TFEC. Write a Commit message. You'll be able to have full traceability of work item tracking. With Team Foundation Server, you have the ability to track your work with a task word.
I have a work icon called End-to-end demo with a work item ID of 13. I'm going to add that as part of my commit so I get full traceability. I'll commit my changes to my local git repo and then I come over and synchronize with my team. Once that's done, I'll push it and share it up to my team so they have it. Switch back over to Team Foundation Server. I can look at my history.
And you'll see I just did that update and because I'm using the full DevOps pipeline I can come over here to my web browser switch over to queued definitions and when I see is that I've got a Build running right now. This Build is going to take the information for my solution. It's going to create an output of a dot pack project as well as deployable zip file for my web site. I'm going to have full traceability and then it's going to directly kick off for release for continuous deployment into my shared dev environment followed by test and prod and as part of doing that shared deployment it will deploy a database or run unit test in the database and then finally if that succeeds it will deploy a web site and as you're watching it here it's about to go green for the web deployment which means I can open up another tab and I can access the shared web environment and the customers view.
We can see the data from our database and if go over to SQL server management studio I now look at that shared dev database, refresh the products table. If I expand the products table you'll see I now have a classic column as well. If we come down you'll note I also have access to the test database. And if we look at products it also is there.
And finally, if the release is completed all the way through the pipeline, you'll see the classic column is there. So hold on to your hats and join us for a nice ride as we learn how to do database DevOps with Team Foundation Server 2018 and SQL server databases.
- Team Foundation Server (TFS) 2018
- SQL Server Data Tools (SSDT)
- Configuring version control of a SQL database
- Installing and importing a database
- Setting up users, team build, agents, and pipelines
- Handling changes, branching, and merging
- Making local deployments
- Building a database for SQL Server
- Continuous integration
- Continuous deployment
- Working with multiple groups and environments
- Testing databases using frameworks
- Working with static data and data motion
- Versioning a database
Skill Level Intermediate
DevOps with Visual Studio Team Services (2017)with Paul Hacker1h 12m Intermediate
Learning Visual Studio Team Serviceswith Jose Miguel Rady Allende1h 17m Intermediate
1. Tooling Overview
2. Version Control Your Database
3. Build Your Database
4. Release Your Database
5. Test Your Database
6. Real-World Issues
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.