Sample Process Workflow - Database development and deployment with Flyway Enterprise

Starting in the bottom left:

1. Work directly against your development database in your preferred IDE.
2. In Flyway Desktop, see what has changed.  Save the object level and static data SQL scripts to disk. 
   1. Optional - If you wish to use migration scripts for deployments, generate versioned and undo migration scripts on disk.
3. Use Flyway Desktop or your own VCS client to version control these scripts.
4. Optional - Create a Pull Request (PR) so the database changes and optional migration scripts are reviewed.  Code analysis and database unit testing can be ran to catch issues early.
5. Optional - Use your CI/CD system to generate a report of changes, check for drift (changes that happened outside the pipeline, e.g., hot fix), run code analysis and other testing (unit, integration, performance, etc.).
6. Use your CI/CD system to deploy your database changes to your downstream environments (QA, UAT, Prod).  Optional - Set up a manual intervention before going to Prod, so releases can be reviewed and pushed on your time. 
7. Optional - Refresh your development database using Redgate Test Data Manager (TDM) with realistic prod-like datasets, while keeping your prod data safe. 
8. Repeat step 1.

Next steps:

• Watch our Redgate University Courses
  • Introduction to Flyway Desktop
  • Flyway Desktop - Enterprise Implementation
• Download the installers  
• Follow the Flyway Implementation Checklist