Business Process Services installation routines are capable of upgrading from any previous version. During setup, transaction boundaries are placed around each version upgrade so that if any problems are encountered during the
upgrade, the database is left in a consistent and known state. During some version upgrades, transactions can become very large and take a long time to complete. In addition, these large transaction boundaries consume
resources when attributes are added to existing types that already have a large number of
instantiated objects. These and other related database operations can consume so many system resources that the setup may fail or take an unacceptably long time to complete.