Put databases in ALM backgrounds
Alessandro Alpi
@suxstellino

Gian Maria Ricci
@alkampfer

December 13th, 2013

#sqlsat26...
Sponsors & Media Partners

December 13th, 2013

#sqlsat264
Organizers

December 13th, 2013

#sqlsat264
About us
 Both MVPs (SQL and VS ALM) 
 Both Microsoft Certified * 
 blogs:
 http://blogs.dotnethell.it/suxstellino
...
Agenda










ALM concepts
Source control manager
Database vs Code
Database ALM tools
Development solutions
Te...
ALM definition
ALM is the product lifecycle management
(governance, development, and maintenance) of
application software....
Why ALM?








Breaking the team barriers (integration)
Release high quality software
Release software in quickly...
Continuous integration





Database integrity check verification
Unit test automation
Code analysis automation
«build...
Continous delivery/deployment






Database drifts
Data sync
Deploy pipeline
Integration tests
Automated deploy from...
Task based work





Modifications vs. «reason»
Agile project  BACKLOG
Traditional project  REQUIREMENTS
Tasks devel...
ALM and database
 The database needs analysis and development
 The databases must be redistributed
 The databases must ...
Source Control Manager






Management of versions
Changes of the code (and not only those)
Shared entity during dev...
SCM – Why?







Versions of our code
Safe storage of our files
Share development lines within the team
Creation of...
SCM – Talking about database






DB can be a file «inside the application»
DB is «located on the server»
DB persist...
But without a SCM
 How can we easily manage the fix?
 How can we prevent regressions?
 How quickly can we have multiple...
DB vs. code – so different?
 The database IS code (programmability,
ddl, grant, etc.)
 The «domain» tables are like many...
DB vs. code – so different?
 The pointers to the linked servers are
configurations (as ‘app.config’)
 The login server a...
Why put the DB under SCM
 Make versions of our objects (DDL) and
our programmability on database
 Make labels including ...
And more..
 Continuous Integration (tests)
 Branch (more development lines)
 Isolated environments for geographically
l...
SCM – Here are some








TFS (on-premises and VSOnline)
Git
Mercurial
Subversion
CVS
Perforce
…

December 13th, ...
Possible actions with SCM
 Some actions are:
 Get
 Commit/Checkin
 Undo
 Save (working folder)
 Delete (working fold...
Management Tool for SCM - DB
 Visual Studio
 Database projects
 Red-Gate Source Control
 SQL Test (for CI)
 ApexSQL V...
The Team Explorer
Regardless of the tool we use, Team Exploder
allows us to:
 Improve management of the changesets
 Impr...
Solutions and tools – development/change
 Management Studio – not enough
 Visual Studio + database projects
 Third part...
Visual Studio + Database projects
 Connected database development

December 13th, 2013

#sqlsat264
Visual Studio + Database projects
 Project based development

December 13th, 2013

#sqlsat264
DEMO
VSOnline connection
Visual Studio Database Project intro
 Project template
 Connections
 Development
 Refactor
 ...
Red-Gate SQL Source Control
 Integration with SQL Server Management Studio

December 13th, 2013

#sqlsat264
Red-Gate SQL Source Control
 Integration with Visual Studio (SQLConnect)

December 13th, 2013

#sqlsat264
Red-Gate SQL Source Control
 Shared development model

 Dedicated development model (recommended)

December 13th, 2013

...
DEMO
VSOnline connection
Intro to Red-Gate SQL Source Control
 SSMS Integration
 Development type
 SCM
 Working folder...
Soluzioni e tool – Unit testing
 Visual Studio
 Database sandbox
 Database unit testing
 Backdoor manipulation

 Red-...
DEMO
Unit testing:
 Visual Studio
 Red-Gate SQL Source Control

December 13th, 2013

#sqlsat264
Soluzioni e tool – Deployment
 Visual Studio Data compare
Live database
Snapshot
Database project

 Deploy da:
Data ...
Soluzioni e tool – Deployment
 Red-Gate SQL Compare and Data Compare








Live database
Working folder
Backup
I...
DEMO
Deployment:
 Visual Studio
 Red-Gate SQL Source Control

December 13th, 2013

#sqlsat264
Conclusions




Which tools to use?
 Every tool has its own peculiarity
 SQL Source Control allows us to manage data i...
Resources



http://www.getlatestversion.it/ (ALM italian community)
http://www.getlatestversion.it/2013/11/28/la-diffic...
Q&A
 Questions?

December 13th, 2013

#sqlsat264
#sqlsat264

THANKS!

December 13th, 2013

#sqlsat264
Upcoming SlideShare
Loading in...5
×

[ENG] SQL Saturday 264 - Put databases in ALM backgrounds

704

Published on

Slides for SQL Saturday 264 in Ancona. How to put SQL Server databases in ALM backgrounds using Microsoft SSMS IDE and Third party tools

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
704
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

[ENG] SQL Saturday 264 - Put databases in ALM backgrounds

  1. 1. Put databases in ALM backgrounds Alessandro Alpi @suxstellino Gian Maria Ricci @alkampfer December 13th, 2013 #sqlsat264
  2. 2. Sponsors & Media Partners December 13th, 2013 #sqlsat264
  3. 3. Organizers December 13th, 2013 #sqlsat264
  4. 4. About us  Both MVPs (SQL and VS ALM)   Both Microsoft Certified *   blogs:  http://blogs.dotnethell.it/suxstellino  http://www.codewrecks.com/blog/  More details on:  http://www.alessandroalpi.net  http://www.getlatestversion.it/ December 13th, 2013 #sqlsat264
  5. 5. Agenda          ALM concepts Source control manager Database vs Code Database ALM tools Development solutions Testing solutions Deployment solutions Conclusions Q&A December 13th, 2013 #sqlsat264
  6. 6. ALM definition ALM is the product lifecycle management (governance, development, and maintenance) of application software. It encompasses requirements management, software architecture, computer programming, software testing, software maintenance, change management, project management, and release management. (source Wikipedia) December 13th, 2013 #sqlsat264
  7. 7. Why ALM?        Breaking the team barriers (integration) Release high quality software Release software in quickly Customer satisfaction Improved work organization Monitoring and tracking the activities Improved code (clear and easy to read) December 13th, 2013 #sqlsat264
  8. 8. Continuous integration     Database integrity check verification Unit test automation Code analysis automation «build» phases December 13th, 2013 #sqlsat264
  9. 9. Continous delivery/deployment      Database drifts Data sync Deploy pipeline Integration tests Automated deploy from a «package» December 13th, 2013 #sqlsat264
  10. 10. Task based work     Modifications vs. «reason» Agile project  BACKLOG Traditional project  REQUIREMENTS Tasks developed on iterations (sprints) December 13th, 2013 #sqlsat264
  11. 11. ALM and database  The database needs analysis and development  The databases must be redistributed  The databases must be synchronized within the development environment  The database will have «changes» associated to «activities»  The database should be tested  And, of course, it’s a good thing to deploy  December 13th, 2013 #sqlsat264
  12. 12. Source Control Manager      Management of versions Changes of the code (and not only those) Shared entity during development stages, Deploy and team management Provides an interface (also graphic) December 13th, 2013 #sqlsat264
  13. 13. SCM – Why?       Versions of our code Safe storage of our files Share development lines within the team Creation of a central point for deploying Automate build and test processes The real needs of every team.. December 13th, 2013 #sqlsat264
  14. 14. SCM – Talking about database      DB can be a file «inside the application» DB is «located on the server» DB persists user data DB is not all and only code However the changes on DB must be reflected on the whole team The Source Control seems «uncomfortable» December 13th, 2013 #sqlsat264
  15. 15. But without a SCM  How can we easily manage the fix?  How can we prevent regressions?  How quickly can we have multiple development environments?  How can we easily create a new dev branch?  How to create different versions of the DB?  How can we synchronize the DB with the latest application changes? December 13th, 2013 #sqlsat264
  16. 16. DB vs. code – so different?  The database IS code (programmability, ddl, grant, etc.)  The «domain» tables are like many enums (static data).  The DB should be changed in more development branches. December 13th, 2013 #sqlsat264
  17. 17. DB vs. code – so different?  The pointers to the linked servers are configurations (as ‘app.config’)  The login server are environment configurations  The database persist the data. It’s not a *source control* problem December 13th, 2013 #sqlsat264
  18. 18. Why put the DB under SCM  Make versions of our objects (DDL) and our programmability on database  Make labels including the database, so we can return to a previous situation  Team synchronized to the get of the version (usually the latest)  To do versioning also of the static data December 13th, 2013 #sqlsat264
  19. 19. And more..  Continuous Integration (tests)  Branch (more development lines)  Isolated environments for geographically located teams  Atomicity between application and DB  Saving documentation of the DB December 13th, 2013 #sqlsat264
  20. 20. SCM – Here are some        TFS (on-premises and VSOnline) Git Mercurial Subversion CVS Perforce … December 13th, 2013 #sqlsat264
  21. 21. Possible actions with SCM  Some actions are:  Get  Commit/Checkin  Undo  Save (working folder)  Delete (working folder)  Edit (working folder) December 13th, 2013 #sqlsat264
  22. 22. Management Tool for SCM - DB  Visual Studio  Database projects  Red-Gate Source Control  SQL Test (for CI)  ApexSQL Versions … December 13th, 2013 #sqlsat264
  23. 23. The Team Explorer Regardless of the tool we use, Team Exploder allows us to:  Improve management of the changesets  Improve association of changesets to tasks  Improve control on commit and checkin phases  Centralize management of checkin policy  Single point for management of the team project December 13th, 2013 #sqlsat264
  24. 24. Solutions and tools – development/change  Management Studio – not enough  Visual Studio + database projects  Third party add-ons with SSMS (i.e. Red-Gate SQL Source Control)  Third party stand-alone tools December 13th, 2013 #sqlsat264
  25. 25. Visual Studio + Database projects  Connected database development December 13th, 2013 #sqlsat264
  26. 26. Visual Studio + Database projects  Project based development December 13th, 2013 #sqlsat264
  27. 27. DEMO VSOnline connection Visual Studio Database Project intro  Project template  Connections  Development  Refactor  Checkin/Checkout  Changeset management December 13th, 2013 #sqlsat264
  28. 28. Red-Gate SQL Source Control  Integration with SQL Server Management Studio December 13th, 2013 #sqlsat264
  29. 29. Red-Gate SQL Source Control  Integration with Visual Studio (SQLConnect) December 13th, 2013 #sqlsat264
  30. 30. Red-Gate SQL Source Control  Shared development model  Dedicated development model (recommended) December 13th, 2013 #sqlsat264
  31. 31. DEMO VSOnline connection Intro to Red-Gate SQL Source Control  SSMS Integration  Development type  SCM  Working folder  SCM direct connection  Static data  Checkin/Save  Changeset management December 13th, 2013 #sqlsat264
  32. 32. Soluzioni e tool – Unit testing  Visual Studio  Database sandbox  Database unit testing  Backdoor manipulation  Red-Gate SQL Source Control  Framework tSQLt  SQLTest plugin  Integrated with SSMS  Builtin test classes  Naming conventions December 13th, 2013 #sqlsat264
  33. 33. DEMO Unit testing:  Visual Studio  Red-Gate SQL Source Control December 13th, 2013 #sqlsat264
  34. 34. Soluzioni e tool – Deployment  Visual Studio Data compare Live database Snapshot Database project  Deploy da: Data compare Publish F5 Data with post build script December 13th, 2013 #sqlsat264
  35. 35. Soluzioni e tool – Deployment  Red-Gate SQL Compare and Data Compare        Live database Working folder Backup Integrated with SSMS Migration scripts Compare Projects customization Two kind of projects for Data and Structures (DDL)  Deploy from:     Compare project (DDL) Compare project (Data) Script folder Nuget December 13th, 2013 #sqlsat264
  36. 36. DEMO Deployment:  Visual Studio  Red-Gate SQL Source Control December 13th, 2013 #sqlsat264
  37. 37. Conclusions   Which tools to use?  Every tool has its own peculiarity  SQL Source Control allows us to manage data in the easiest way  Visual Studio ensures the same structure of the database project  Visual Studio is more simple for the developers (or SQL Connect) Which parameters should we consider?  How is our team structured?  Which are the minimum requirements?  How much can I afford to spend?  Can I afford the learning curve if I change IDE? Last but not least, I should use the Source Control  December 13th, 2013 #sqlsat264
  38. 38. Resources   http://www.getlatestversion.it/ (ALM italian community) http://www.getlatestversion.it/2013/11/28/la-difficile-arte-della-stima/  http://www.codewrecks.com/blog/ (Gian Maria Ricci’s blog on ALM)      http://mattvsts.blogspot.it/ (Matteo Emili’s blog on ALM) http://www.codinghorror.com/blog/2006/12/is-your-database-under-version-control.html http://odetocode.com/blogs/scott/archive/2008/01/30/three-rules-for-database-work.aspx http://odetocode.com/blogs/scott/archive/2008/01/31/versioning-databases-the-baseline.aspx http://odetocode.com/blogs/scott/archive/2008/02/02/versioning-databases-changescripts.aspx http://odetocode.com/blogs/scott/archive/2008/02/02/versioning-databases-views-storedprocedures-and-the-like.aspx http://odetocode.com/blogs/scott/archive/2008/02/03/versioning-databases-branching-andmerging.aspx http://www.red-gate.com/products/sql-development/sql-source-control/ http://vsaralmassessment.codeplex.com http://it.wikipedia.org/wiki/Application_lifecycle_management      December 13th, 2013 #sqlsat264
  39. 39. Q&A  Questions? December 13th, 2013 #sqlsat264
  40. 40. #sqlsat264 THANKS! December 13th, 2013 #sqlsat264
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×