Setting up the production database – considerations
We typically create users and databases in the production environment, then create other objects (such as tables and views) and also populate some data before going live. The kind of cleaned and verified master data to be populated in the production environment depends on the system. Country and city master data, currencies and exchange rate master data, geoip data, domain-specific master data (such as product lists, warehouse lists, airports, and so on) all may need to be populated with scope for changes to the data in future.
The volume of data to be moved will also vary. It's possible that the new system, running on PostgreSQL, will replace a system that uses Oracle or MySQL. In such scenarios, data from the existing system should be migrated to the new system. These situations have a few added complexities:
Data volume: The existing system has been live for a few years and most of the data needs to be migrated.
Database code rewrite: The...
