Details Required for Connecting to the Database
Details Required for Connecting to the Database
Once you have set up the database, you should pass on the following details to a Evolve Suite user so they can create the connection to the repository:
•The name or IP address of the database server
•The instance name, if you created a new instance
•Port number if required
•Database name, noted as [database_name]
•Login name noted as [login_name] if using SQL Authentication
•Login password noted as [login_password] if using SQL Authentication.
WHAT NEXT?
Once the database is created a Evolve Suite user must load the necessary Evolve Data into the repository in order to complete the database configuration. See Appendix A – Load Models into the Evolve Repository
Upgrading to Evolve Suite
If you want to upgrade from an earlier version of Evolve Suite, then you should read this chapter carefully before installing any software.
|
|
If you are in any doubt about how to proceed with upgrading your copy of Evolve Suite, or any standalone components such as Document Generator or V-Modeler, please contact the Quest support. |
In a multi-user environment, where more than one client machine accesses a networked Evolve Repository, you must upgrade all your clients. The user who upgrades the network databases must have administrator rights to the database as schema changes are required to upgrade to this version. Once a Evolve Repository has been used with a newer version of the client software, an older version of the client may not be able to correctly use the database.
NOTE ON PRODUCT COMPATIBILITY - EVOLVE, PORTAL, CMI, CORPORATE PUBLISHER, COLLECTOR & WEB SERVICES
|
|
Important: Casewise Portal & Casewise Publisher are deprecated. There is no version of Portal or Publisher that runs with Evolve Suite 2024. New JSON/REST and XML based webservices are available since 2018.1, please ask Support. |
If you are upgrading from Evolve Suite 2022.1 or earlier, and you use other Quest products, such as Evolve, Analytics (CMI), or Collector, then you will need to upgrade them at the same time as upgrading your Evolve Suite installation. Previous versions of these products will not work with this new version of Evolve Suite.
It is therefore necessary to take the time to plan your upgrade procedure to prevent users of one system trying to use it while another part is being upgraded. All components will need to be taken offline while they are all upgraded. Each of these components have their own installation guides which you should read before attempting to upgrade them.
Upgrade Paths
Upgrade Paths
This guide only includes instructions on upgrading from the following versions:
l 2009.x l 2011.x l 2013 l 2015 / 2015 SR2
l 2016 / 2018 all versions
l 2020.0 / 2020.1
l 2022.0 / 2022.1
If you want to upgrade to Evolve Suite 2024.0 from an earlier version than those listed above, please contact Quest support for assistance.
Upgrade Procedure
Upgrade Procedure
|
|
Important: If you are upgrading from Evolve Suite 2013, 2015, 2016, 2018, 2020.0, 2020.1, 2022.0, 2022.1 please ensure that you run validate repository on all active databases before you uninstall these versions. This will ensure that the database is in a known state and confirm there are no issues with the current database. This is detailed in Appendix G of this installation guide. |