Who is this article for?

IT Personnel planning an upgrade to Please Review 7.0.0.

IT access is required.

Important: This article is part of a series of articles covering the upgrade process. Please visit  Performing a Please Review 7.0.0 Upgrade to view the entire process.

As part of the Please Review upgrade it is essential that the database is also upgraded to match the application.

This article outlines the steps required to perform the database upgrade. The steps you need to follow will vary based on the database platform you have chosen to host your Please Review database and so this article is split into the following sections:

1. Microsoft SQL Server

1. Backup the database.
2. Open the installation media.
3. Navigate to the runtime\config\migration folder.
4. Open the SQL script for the version immediately above your current one (e.g., if upgrading from v6.5, start with v6.6).
5. Launch Microsoft SQL Management Studio and log in as the user specified in runtime\config\config.xml.
6. Right-click the Please Review database and select New Query.
7. Paste the script into the query window.
8. Execute the script.
9. Repeat steps 3–7 for each version up to your target version, running scripts in chronological order (e.g., from 6.6 to 7.4).
10. If unsure or if errors occur, contact support before proceeding. You may need to restore the backup from step 1 or revert to the older version temporarily.

2. Oracle

1. Backup the database
2. Open the installation media.
3. Browse to the runtime/config/migration directory.
4. Open the Oracle script file relevant to the version of Please Review you are upgrading to.
5. Open a Microsoft Windows Command Prompt in the runtime/config/migration directory.
6. Enter the following command:

 sqlplus <user>/<password> <script>

Example: sqlplus admin/abc@123 v7.1.oracle.txt

Note: The user used in the upgrade query must own the Please Review tables.

7. Repeat steps 3-6 for each version:
   When migrating the database, run all migration scripts from your current version up to the target version in chronological order. For example, upgrading from 6.5 to 7.4 requires running scripts for 6.6, 6.7, 7.0, 7.1, 7.2, 7.3, and 7.4 in sequence.
   
   If unsure about the upgrade process or if errors occur, contact support before continuing. If urgent, consider rolling back to the backup from step 1 or reverting to the previous version temporarily.

What Next?

With the database upgraded you are now ready to begin testing. Please see Testing the Upgrade Was Successful for 7.0.0 for the next steps or Performing a Please Review 7.0.0 Upgrade to review the whole process.

3. Further reading

• Performing a Please Review 7.0.0 Upgrade
• Preparing for a Please Review 7.0.0 Upgrade