For version 5.0.0, plan the Process Engine SQL Server database upgrade. Plan carefully to determine whether there are prerequisites for doing the Process Engine upgrade.
The following requirements are in addition to the requirements discussed in Database administrator planning .
The recommended upgrade scenario is to make a test copy of the Process Engine database. Complete the upgrade on that copy. Doing the upgrade with a database copy also lets you to determine how long the upgrades take.
READ_COMMITTED_SNAPSHOT must be enabled for the SQL Server database where the Process Engine schema is installed. You
can enable READ_COMMITTED_SNAPSHOT before or after you upgrade the
database. To enable READ_COMMITTED_SNAPSHOT for the object store,
see the instructions in Creating a Microsoft SQL Server database
for an object store.
Process Engine string fields are modified for all Process Engine user tables by increasing the length by an expansion factor. This expansion value is to allow for the additional space requirements for character-based string fields. String fields are modified by increasing the length by the defined factor.
Record the value to indicate
your choice to expand string fields by a size factor in your customized Installation and Upgrade Worksheet. Set the value between
three and six. To find this property, filter on peupgrade and
search the worksheet for instances of the Database Column
Size Factor parameter.
After the upgrade, use the pedconvert tool to make the following changes:
Use of the pedconvert tool is recommended for workflow systems that support multi-byte characters in an international global environment. Customers who do not have multi-byte systems also run the pedconvert tool, but it can be run after the upgrade. See techdoc 7036559 for information. The technote is applicable to all upgrades from 4.5.1 and also to 5.0 systems that previously upgraded from earlier releases but have not run the 5.0 advanced upgrade tool, techdoc 7019393.