There are extra steps to take into consideration when intending to upgrade a Ketura system that has been configured to use a Microsoft SQL Server database. When a Ketura system that has been configured to use a Microsoft SQL Server database is upgraded to a newer version of Ketura, it will revert back to using the built-in Ketura database. To switch back to using Microsoft SQL Server, the Ketura system will be required to be migrated to Microsoft SQL Server again, as described in Using Microsoft SQL Server 2005 Instead of Ketura’s Built-In Database, and the data from the previous installation restored into the new database.
These steps should only be attempted by someone thoroughly familiar with system and
database administration. Please ensure that you have the privileges to create the new Microsoft SQL Server database that you
will
be creating to replace your existing Ketura database.
To upgrade a Ketura installation that uses Microsoft SQL Server:
-
Make a backup of Ketura’s Microsoft SQL Server database using your preferred Microsoft SQL Server tools. This is a precautionary measure, enabling you to revert back to your current database if you encounter problems with later steps.
-
In Ketura, make a backup of the database, as described in Backing Up a Ketura System. Keep a record of the location of the backup file.
-
Install the newer version of Ketura, as described in the ‘Installing the new vesion of Ketura’ section of Upgrading to a Newer Version of Ketura.
-
Follow steps 1, 2, 3, 5, 6, 7 and 8 of Using Microsoft SQL Server 2005 Instead of Ketura’s Built-In Database. This should result in your new Ketura installation running with a new database in Microsoft SQL Server.
Please note that if you choose a name for the new database that is the same as an existing Microsoft SQL Server database, the database will be overwritten. Please ensure that this your intention, before running the CreateSqlDb command. If you do not wish to overwrite a database, please specify a new name for the database when running the command.
-
In Ketura, restore the backup of the database that you made earlier. For more information see Restoring a Ketura System from a Backup.
-
Follow the advice given in the ‘Important step for all users, following an upgrade’ section of Upgrading to a Newer Version of Ketura.
All being well, you will have successfully upgraded your Ketura installation. You may wish to remove the Microsoft SQL Server database of your previous Ketura installation if its name differs from the newly created database, as the old database will no longer be required by the new Ketura installation.
Be sure that the SQL Server 2005 compatibility level for the Ketura database is set to SQL Server 2005 (90). Ketura does not support other levels.