When software changes your database itself at the next restart, nobody knows exactly what happens until it happens. While the system stays live, that means you find out about a change only after it has already run. That is avoidable.
Every database change instead becomes its own dated script that can be read and reviewed before it runs. A change moves in a controlled way from development through test to live, and back again when needed.
What ports as-is
- What was previously generated automatically for the database stays on record and is not deleted
- Each service has its own ordered set of scripts, plus an overview of which state already runs where
- Every change checks the current database first, and only applies where it is actually needed
- A whole environment can be copied in full, or only the missing scripts pulled in
- A live database can be restored without having to stop the applications running on it
What we build for you
- The service and database names and their test and live pairs
- The database server, the login and where its password lives
- Which previous automatic changes are frozen and which never existed
