You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
This is important in large scale enterprise deployments. Although development teams can and should develop solely using migrations and making their own choices over whether to have local or shared development databases, it is vital that at the end of a sprint or as part of a release, a single packaged "upgrade" script can be provided to a DBA group to apply to staging and production systems.
It may be that eventually there is no requirement for this within a company, but certainly whilst migrating to more agile methods (including automatically run migrations) it is important to be able to build confidence with and interoperate with existing DBA requirements.
The text was updated successfully, but these errors were encountered:
This is important in large scale enterprise deployments. Although development teams can and should develop solely using migrations and making their own choices over whether to have local or shared development databases, it is vital that at the end of a sprint or as part of a release, a single packaged "upgrade" script can be provided to a DBA group to apply to staging and production systems.
It may be that eventually there is no requirement for this within a company, but certainly whilst migrating to more agile methods (including automatically run migrations) it is important to be able to build confidence with and interoperate with existing DBA requirements.
The text was updated successfully, but these errors were encountered: