Comments
1 comment
-
Official commentHi lilly44
Thank you for reaching out on the Redgate forums regarding your inquiry for script creation & management. I noted you have posted in an Oracle forum so assuming you are using Oracle and possibly a mix of other database types.
A good approach is to use a migrations-based workflow; so every database change is captured as a script, versioned, and deployed in a controlled way.
Redgate Flyway is designed specifically for this. It allows you to:
• Create versioned migration scripts (for example:
V1__create_tables.sql,V2__add_indexes.sql)
• Store scripts in source control (Git, Azure DevOps, etc.) alongside your application code
• Automatically track which scripts have been applied using a schema history table
• Deploy changes consistently across dev, test, and production environments
• Integrate into CI/CD pipelines to reduce manual deployment riskA typical workflow example might be similar to this:
- Developer creates a new migration script for the required change
- Script is committed to source control
- Flyway runs during build/release and applies any pending migrations
- Flyway records the change so it won’t run again
This ensures changes are traceable, repeatable, and reduces deployment errors.
You can learn more about Flyway here:
https://www.red-gate.com/products/flyway/This page includes additional information on features, supported databases (including Oracle), and the option to download a free trial so you can test it within your own environment and workflows.
Add comment
Please sign in to leave a comment.
I’m looking for guidance on creating and managing new scripts effectively using Redgate tools. While working on internal systems and project workflows at AMC Construction, we want to follow best practices for organizing scripts, managing changes, and minimizing errors during deployment. Any tips, recommended workflows, or real-world examples would be greatly appreciated.