This document is for customers using a full installation of SQL Server 2012 or newer to host the ESHA Database.
- If the Server name includes either "\ESHA", or is literally "(localdb)\v11.0", then it is an ESHA instance of SQL Server, and you may use these instructions, or use the similar instructions for updating via Database Utility.
- If the Server name does not include "\ESHA" or "(localdb)\v11.0", you are using a full installation of SQL Server (non-ESHA instance), and will continue with the instructions below.
Download the script files
If you have not already done so, download and extract the .zip file for Genesis R&D
Note: The script file names reflect the starting database structure version, not the ending. For example, s11.4.0.sql runs when the structure version is 11.4.0, and on successful completion, the database structure will be updated (e.g. 11.4.1, or possible something like 11.5.0).
These scripts must be executed in the correct order for the update to be successful.
Back up your database
- If you use Database Utility, follow these instructions
- If you use SQL Management, follow these instructions.
Run the scripts
Find your Database Version
- Select the appropriate database, for your program; typically, this is 'gendata' for Genesis.
- Click File>New>Query with Current Connection.
- Type the following SQL statement: select * from UDatabaseVersion
- Press F5 to execute the query.
- Note the Structure Version.
Determine Starting Script
Once you have found the version numbers for the database, you need to determine which script to run. Generally speaking, run the 's' script that matches the Structure Version you found above. For example, if your structure version is 11.8.0, the script to run is 's11.8.0.sql'. This means that the ending structure version will be higher than the last script you run.
Execute Script
To execute a script in Management Studio:
- Connect to the proper SQL Server instance.
- Connect to the proper database name (typically 'gendata').
- Open & Execute the proper Starting Script (details above).
- Note the resulting Structure Version after script execution.
Repeat until your Structure Version matches the Target Structure Version based on the table below.
NOTE: Recheck the database version after running each script. The scripts do not necessarily take you to the next row in the update table. And remember the script number is the starting structure version, not the ending structure version.
| Genesis (First Release) |
Target DB Structure | Final Script (*.sql) |
|
11.15.x (Sept/Nov 2024) |
11.15.0 | s11.14.5 |
|
11.14.x (Jan 2024) |
11.14.0 | s11.13.1 |
|
11.13.x (Feb 2023) |
11.13.1 | s11.13.0 |
|
11.12.x (July 2022) |
11.12.1 | s11.11.0 |
|
11.11.x (Oct 2021) |
11.11.0 | s11.10.0 |
|
11.10.x (Mar 2021) |
11.10.0 | s11.9.0 |
|
11.9.x (Nov 2020) |
11.9.0 | s11.8.0 |
|
11.8.x (June 2020) |
11.8.0 | s11.7.2 |
|
11.7.x (June 2019) |
11.7.1 | s11.7.0 |
|
11.6.x |
11.6.0 | s11.5.1 |
|
11.5.x |
11.5.1 | s11.5.0 |
|
11.4.x |
11.4.2 | s11.4.1 |
|
11.3.x |
11.3.4 | s11.3.3 |
|
11.2.x |
11.2.1 | s11.1.3 |
|
11.1.x |
11.1.3 | s11.1.2 |
| 11.0.x (Aug 2015) |
11.0.0 | s9.8.4 |
|
9.14.x |
9.8.3 | s9.8.2 |
|
9.13.x |
9.7.5 | s9.7.4 |
|
9.12.x |
9.6.0 | s9.5.1 |
|
9.11.x |
9.5.1 | s9.5.0 |
|
9.10.x |
9.4.0 | s9.3.1 |
|
9.9.x |
9.3.1 | 9.3.0 |
|
9.8.x |
9.2.0 | s9.1.0 |
|
9.7.x |
9.1.0 | s9.0.1 |
|
9.6.x |
9.0.1 | s9.0.0 |
|
9.5.x |
8.9.2 | s8.9.1 |
|
9.4.x |
8.8.0 | s8.7.0 |
|
9.3.x |
8.7.0 | s8.6.1 |
|
9.1.x |
8.6.0 | s8.5.1 |
|
9.0.x |
8.5.1 | s8.5.0 |
Comments
0 comments
Please sign in to leave a comment.