3. #SQLSatDenmark
What is he talking about?
About making deployments easier
removing manual tasks
Things tested in practice
starting with small steps
From multiple scripts to one script deployment
or using one/two steps in TFS
How to build your own solution
About different options and hurdles
5. #SQLSatDenmark
Bartosz Ratajczyk
SQL Server Consultant @ 7N
Speaker
SQL Saturday volunteer
Advisory Board Member in Data
Community Poland
MCSE, MCT
http://bartekr.net b.ratajczyk@gmail.com
6. #SQLSatDenmark
All deployment steps
Client side
1. Compile project
2. Deploy project
Server side
1. Create folder
2. Create environment
3. Reference environment
4. Create environment variables
5. Configure project
6. Validate project
7. Verify validation
8. Test run
Testing (NBi, LegiTest)
Naming convention compliance (ie. Jamie Thomson)
7. #SQLSatDenmark
Raising the bar
Version control
DEV, TEST, PROD branches
Different servers
DEV, TEST, QA, PREPROD, PROD
Different configurations
Drive letters, folder names
Connection strings
We have more than one project
24. #SQLSatDenmark
Configuration Manager - usage
Different parameter values for different configurations
(think: local environments)
Contained in .dtproj files
No single window to configure them all
36. #SQLSatDenmark
And how about TFS?
Custom proces for building and deployment
You can expand it with PowerShell steps to
control environments, validation, …
38. #SQLSatDenmark
So simple!
The work is still boring, but this time the computer does it
For automation use
MSBuild
Powershell
SMO
Use additional software for CI/CD process