Aurora Systems Manager – Release Notes – Current #
| Detail | Description |
|---|---|
| Application Name | Aurora Systems Manager |
| Version | 4.9.19 |
| Release date | 19th September 2014 |
| Type of Release code per feature | (E=Enhancement, B=Bug fix, M=Major release) |
| Developed by | DC |
| QA’d by | DC , MF, TG |
| When to apply change | Before implementing User Profiles. Database version 163 schema update is not trivial and affects every table in the database so a database backup immediately beforehand is essential. WebOPAC access should be disabled during the upgrade.The multi-step process requires the deletion of text retrieval indexes, a full schema update, truncation of the log file and recreation of the text retrieval indexes using this application (not the older now obsolete Aurora Text Retrieval application). It is highly recommended that a trial run be done on a test database. Please refer to the accompanying documentation document How to upgrade Aurora SQLServer to schema version 165. (the process is the same for upward movement through version 170) |
| Files distributed | AuroraSystemsManagerSetup install set |
| AWS Version required | Specific AWS version is not critical |
| Who should perform the installation | Customer |
| Download from | Please contact Ait directly. |
| Installation instructions | Please note that from February 2013, MSI installation operations are changed, and the install set is supplied as an executable (.exe) rather than a zip archive.The workstation must have Microsoft Net Framework 4.0 or later installed. |
| Performance Effect | Negligible |
| Resource or Capacity Effect | None |
| Prerequisite Customer Tests | A full trial run on a test database is highly recommended.Ensure the workstation user has sufficient privileges to modify the database schema. Without this the upgrade will not be applied.On completion of the run it is highly recommended that you promptly email the resultant log file from c:\temp to AIT |
| Pre-requisite Database Backup | Required |
| Pre-requisite previous version backup | Yes |
| Detailed update Steps | ** If you have not updated the database for Unicode compliance, please first refer to the document ‘How to Upgrade a SQL Server database for Unicode compliance’
|
| Rollback Steps | Restore the database backup taken before the schema upgrade. Uninstall and reinstall previous application version. |