Get The SQL Script Files
Get The SQL Script Files
We have provided a set of SQL scripts which should be used when configuring the database, so please ensure you have these ready when preparing to set up the database. The script files are available from Quest website. The website files are zipped in files titled:
l EvolveSuite-XXXX-X-X-XXX Database-Scripts.zip
Instructions for SQL Server
Instructions for SQL Server
The following table shows high-level steps for setting up the Evolve Repository on Microsoft SQL Server and should only be performed by a SQL Server administrator.
|
1 |
Create a new SQL Instance |
Note the name as: [database_name] Make sure the collation is: Latin1_General_CI_AS |
|
2 |
Run SQL Script Files |
Run each of the supplied SQL Script files against your database, in the following order: 1.CreateMSSQLSchema.sql 2.CreateMSSQLCopyModelProcedure.sql 3.CreateMSSQLDeleteModelProcedure.sql 4.GetNextId.sql 5.CreateCasewiseRWRole.sql 6.GrantAccessToSchemaForCasewiseRWRole.sql |
|
3 |
Create a new login |
Create a new login specifically for Evolve Suite use. We recommend using Windows Authentication, however you can also use SQL Authentication if you wish. Note the login name as [login_name] For Windows Authentication Make sure the User Group you assign to the login includes all users who need to access Evolve Suite. For SQL Authentication Note the password as [login_password] |
|
4 |
Create a new user |
Create a new Database User for the Evolve Database [database_name] and link the user to the login [login_name] you just created. Set Owned Schemas and Membership (Role Members) to CasewiseRW |
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 2020.2
Upgrading to Evolve Suite 2020.2
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. |
I
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 2020. Web Services are however compatible with CW Suite 2016 and can still be operated from a standalone server (that must NOT have Evolve Suite/Evolve 2020 installed on the same server). New JSON/REST based webservices are now available in 2018.1 and above, please ask Support.
|
If you are upgrading from Evolve Suite 2020.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.