Understand the process for upgrading a PI AF collective

Beginning with PI AF 2.7 (2015), the PI AF upgrade process requires that you disassemble the collective before you upgrade it. All PI AF servers in a PI AF collective must use the same PI AF version.

Note: You must have the db_owner privilege to upgrade the PI AF SQL database.

To minimize the amount of time when your PI AF users are unable to write to the PI AF SQL database, and to maximize the availability of the PI AF data as read-only to your PI AF users, upgrade the primary PI AF server first. Then upgrade the secondary PI AF servers.

The PI AF collective process is as follows:

1. Stop replication.

2. Disassemble the PI AF collective.

3. Upgrade the former primary collective server.

4. Upgrade the former secondary collective servers.

5. Rebuild the PI AF collective.