How does the database size influence or relate to the downtime and runtime of a technical upgrade in general?
Project statistics have proven that there is no link between the pure database size and the downtime. Only for certain database objects that have to be touched in an upgrade, the size of it correlates with the runtime needed for its processing. The impact of certain objects on the runtime/downtime can not be truly estimated in advance without the simulation of an upgrade based on a copy of a productive system because it depends on several criteria, such as the start and target release, the number of support packages and installed add-ons and the degree of customer modifications.
Related Questions
- I have added more records and my database size is increased. Can I upgrade my key limit according to the record count?
- How does the database size influence or relate to the downtime and runtime of a technical upgrade in general?
- Ive attempted to open a v3.1 SSCE database file using the SSCE 3.5 runtime (still in beta) and it is failing?