 | Loading… |
|
|
|
Upgrade
Upgrade
In this section we will check how to upgrade Pantheon to a newer version.
|
Table of content
- Basic parameters
- Simple upgrade
- Advanced upgrade
|
 |
For a more detailed treatment of what upgrade is and how it works see topic How Upgrade Works? |
|
Upgrade of Pantheon database to Row Level Security (RLS) on SQL servers lower version than SQL 2017 is not supported from Pantheon version 27.10.
When executing such upgrade, program will open a message
MSSQL 2017 is required as the lowest version for RLS to work properly, but Microsoft provides active support only until November 2022. See more about Microsoft support for MSSQL versions.
|
1. Basic parameters
The following are basic parameters that must be set when attempting to upgrade:
| Upgrades |
Specify the path to the location where upgraded data downloaded from the Internet are stored.
|
The path (directory), which you can set here, is the LOCAL PATH on the computer where you are creating a backup copy. Enter it as a local path in case of mapped drive (e.g. F:\DATALAB\UPGRADE) or (recommended) using the UNC annotation if a network share location is specified \\SERVERNAME\DATALAB\UPGRADE. |
|
| Backup |
Specify the path to the location where database and program backup copy is created.
|
The path (folder), which you can set here, is the LOCAL PATH on the computer where you are creating a backup copy. Enter it as a local server path (e.g. C:\MSSQL\BACKUP, where C:\MSSQL represents a server folder or using the UNC annotation if a network share location is specified \\SERVERNAME\BACKUP. |
|
| Executable |
Specify the path to the location of the current working directory where PANTHEON.EXE is located. |
| Wait |
Enter the time interval for waiting (in seconds), required for exiting program and copying. If identified when starting PANTHEON that the database is of a more recent date than the executable (EXE) being used, the program is stopped automatically and wait process (COPYDELAY.EXE) starts, waiting for the program to stop work and then a new executable version is copied from the upgrade directory to the current working directory. |
 e-Mail Notification |
If checked, an e-mail notification will be sent to the selected adressee (the Send To field) after upgrade finishes. Settings for sending mails. If incorrect information is provided for email settings, e-mail notification can't be sent and there will be an error message at the end of upgrade log. |
When the above data are set just select the mode for upgrade to be used and click Upgrade.
Select between two modes used in upgrading:
2. Simple Upgrade
Simple upgrade is, because easy to use, intended for all non-professionals. You only need to set the parameters required for upgrading. After clicking the Upgrade button, it is done in the following way:
- First, the program creates a backup copy of database in the directory set in the Backup field.
- What follows is creaton of the backup copy of executables in the directory set in the Backup field. If upgrade is not completed successfully, the above two copies are restored automatically, thus enabling work with the previous version.
- Files containing the required data are then downloaded from the Internet and saved in the Upgrades directory.
- After download completes, all databases which can be found on the server are upgraded.
- In the end after databases are upgraded successfully, a message appears informing you that the operation completed successfully.
When upgrade finished close the program and run it once more. The version of executable (.exe) is changed automatically.
|
Differential upgrade is always included in simple upgrade (only data vary between the currently used and new version) hence shortening the upgrade process. |
3. Advanced Upgrade
As distinct from simple upgrade the advanced offers you a possibility to set suing parameters individual steps in upgrading.
|
It is recommended that the advanced upgrade should be used only to experienced users with substantial knowledge on how to proceed when upgrading. |
 Backup Executables |
If checked, backup copies are saved in order to be loaded once more after upgrade is not completed successfully.
If unchecked, backup copies are not created. |
 Backup Database |
If checked, backup copies of databases in order to be loaded once again after upgrade is not completed successfully.
If unchecked, backup copies of databases are not saved. |
 Online Upgrade |
If checked, upgrade is performed using the Internet.
If unchecked, you would be trying to upgrade using a temporary code where you transfer files required for upgrading manually (e.g. using CD-ROM).
It is only significant in terms of the computer where the upgrade is performed. |
 Download Upgrades |
If checked, new data are downloaded from the Interent to the Upgrades directory.
If unchecked, when upgrades were already transferred to the Upgrades directory (e.g. by transferring files from a CD or when they have been already transferred during previous upgrading). |
 Full DB Upgrade (not differential) |
If checked, the differential upgrading is not used. In this case a complete table scheme and SQL procedures ranging from the first build on get transferred by upgrading and it is checked that all the tables match the ones in the destination build. Use this option when you assume that in some previous upgrade process was not completed in its entireity and ypi want to ensure the appropriate structure.
If unchecked, the differential upgrade is used (that is, only the changes are transferred). |
| Upgrade To |
Select between the release build (tested by Datalab), whcih is released in regular time intervals, and the nightly build (beta) variant which was not tested. Upgrade to beta build only in case you want to verify a certain functionality between two builds.
You are strongly discouraged to use beta upgrades on running systems. Furthermore, we take no responsibility for the actions taken! |
 Upgrade Database |
If checked, the database is upgraded together with th executable.
If unchecked, the database is non upgraded. |
| BMP to PNG |
All pictures in databases that are in .BMP format are converted into .PNG format due to reduction of space in SQL database. |
| Databases on Server |
This window displays all available PANTHEON databases on server. Here you can:
- select a database and so included it in upgrading, or
- leave the checkbox unchecked or deselect it and leave it out.
This option is used mostly when trying to upgrade to a certain specific database.
|
| (internal checkboxes) |
They are always checked regardless of the upgrade mode:
 Upgrade DB Structure  Fill Authorizations
 Fill Reports  Fill Procedures
|
 Upgrade All Objects |
Upgrades all objects regardless of the fact whether they were changed or not. If unchecked, only those objects are upgraded that are different between the current and upgraded vesrion. In this case the upgrade process is performed faster. |
 Upgrade Executables |
If checked, executables (EXE) are upgraded.
If unchecked, executables are not upgraded. |
| Show Open Sessions |
Before database is upgraded no other connection to the database is possible. Set focus to a database in a list of databases and use button "Show Open Sessions", a form with all open connection to the selected database is opened. Connections can be manually closed/killed using button "Disconnect users". After all connections are closed an upgrade can begin.
|
|
Single-User Mode
|
Before database is upgraded no other connection to the database is possible. By using parameter "Single-User Mode", database is set as "Single-User Mode" during upgrade process. During the proces of upgrade, login to database is not possible. Also connections with SQL Management Studio and other management tools are not possible. All connections to database are automatically closed/killed. After all connections are closed an upgrade can begin. After upgrade is complete, database is switched off from "Single-User Mode".
If login to database is executed during an upgrade process, error message is displayed: 
|
| Messages/Errors |
Shows all mesages and errors that ocured during upgrade.  opens "Log Messages" form for additional information on messages and errors during upgrade.
|
| Advanced |
Features: Data compression
- Keep existing - compression / decompression not executed
- Enable - executes compression on undo tables
- Disable - executes decompression on undo tables
Unicode conversion
Conversion from ansi to unicode.
Parallel execution
For faster upgrade, upgrade is executed in multiple parallel threads. Threads can also be used in case there's multiple files group.
Database: Database owner
Setting a database owner
Database Collation
To ensure proper program funcitoning the database and computer collations need to be equivalent.
The default collation for Datalab database is Latin_1_General_CI_AS.
Normally you set it before program installation. If you do not select it or you are unable to do so, you have to modify Change Collation setting.
Encrypted drop: parameter is needed if there is an encrypted sql module that depends on database collation and is not part of pantheon. Setting allows you to remove encrypted sql modules for the time of upgrade.
Database size
Shrinking database files: data and log
Index Rebuild
Tables and Index rebuild during an upgrade.
|
| PAW |
Upgrading PAW
Impersonate user.
Enter domain name, user name and password.
|
| PAWS |
Upgrading PAWS
|
| PAAS |
Upgrading PAAS
|
|
In case your company does not have a tax ID defined the upgrade cannot be successful. The following IRIS message appears where you can add this data (see 5184 Our company has no tax ID defined!). |
|
After every upgrade it is recommended that you run the command for creating ZEUS cubes (when using ZEUS, that is).
It is wise that you use automatic processing, which, if set accordingly, creates cubes automatically. |
| Loading… |
| Loading… |
|
|
|
|