Pega 7.4 Storage Version DSS
In our system, the DSS "prconfig/database/storageversion/default" is set to 6. However, we were recently told that this should be updated to 7 because it is more efficient in terms of memory and CPU.
The question we still have, is this version determined by the version of Pega being used? IE, Pega 6.x should set the DSS to 6 and Pega 7.x should set the DSS to 7. Or is this not the case and the DSS number just happens to correspond to our current Pega version in this case?
***Moderator Edit-Vidyaranjan: Updated SR details***
Pegasystems Inc.
US
For Pega 7.4, please set the DSS "prconfig/database/storageversion/default" value to "7".
There was an old SR. User did an upgrade from Pega 7.1.8 to Pega 7.3.1.
In 7.1.8, they had added this DSS setting to value "6".
In 7.3.1, they were having problem with these "refer" properties.
After they changed to value "7", the issue got resolved.
Auto-Owners Insurance Group
US
Thanks for the response! We are currently updating the DSS to the value "7".
My main question though, is not whether we should update the value to "7", but rather, how could we have known the value needed to be "7"? Is the value "7" because we are on a 7.x version? Or is this just the most recent version available for Pega 7.4?
Please let me know if you need any further clarification.
Accepted Solution
Pegasystems Inc.
IN
Hi Nick,
Let me explain to you what's the significance of storgaeVersion DSS first.
storageVersion
Type: string
Default: 6
Valid Values: 4, “iso8859”, “iso-8859”
5, “unicode”, “utf16”, “utf-16”
6,7
Functionality:
- Setting this entry to “4” causes the system to store "blob" data using ISO-8859-1 encoding and will prevent the use of non-Latin characters within PegaRULES. StorageVersion 4 writes blobs that are compatible with PegaRULES 03-02.
- Setting this entry to "5" enables Unicode support in the database and writes blobs that are compatible with PegaRULES 4.1.
- Setting this entry to "6" not only enables Unicode support but also enables performance enhancements in the way the data is stored in the database. Storage streams written in this format are compatible with Process Commander Version 4.2.
- 7 is similar to 6 . When to use it depends on the type of deployment whether it is an upgrade or fresh installation.
Available since: Version 4.1
Currently database/storageVersion DASS is being shipped with default value 6. We want to determine and set the default value of DASS based on the deployment type.
Hi Nick,
Let me explain to you what's the significance of storgaeVersion DSS first.
storageVersion
Type: string
Default: 6
Valid Values: 4, “iso8859”, “iso-8859”
5, “unicode”, “utf16”, “utf-16”
6,7
Functionality:
- Setting this entry to “4” causes the system to store "blob" data using ISO-8859-1 encoding and will prevent the use of non-Latin characters within PegaRULES. StorageVersion 4 writes blobs that are compatible with PegaRULES 03-02.
- Setting this entry to "5" enables Unicode support in the database and writes blobs that are compatible with PegaRULES 4.1.
- Setting this entry to "6" not only enables Unicode support but also enables performance enhancements in the way the data is stored in the database. Storage streams written in this format are compatible with Process Commander Version 4.2.
- 7 is similar to 6 . When to use it depends on the type of deployment whether it is an upgrade or fresh installation.
Available since: Version 4.1
Currently database/storageVersion DASS is being shipped with default value 6. We want to determine and set the default value of DASS based on the deployment type.
1. If Upgrading or Updating from a version >= 7.1.0 and <= 7.1.7 and If the system already has database/storageVersion DASS, then leave its value as it is (do not override) else import the database/storageVersion DASS and value should be = 6.
2. If Upgrading or Updating from a version < 7.1.0 or > 7.1.7 and If the system already has database/storageVersion DASS, then leave its value as it is (do not override) else import the database/storageVersion DASS and value should be = 7.
3. If fresh install of 7.1.8 and above, database/storageVersion DASS should be = 7.Currently database/storageVersion DASS is being shipped with default value 6. We want to determine and set the default value of DASS based on the deployment type.
1. If Upgrading or Updating from a version >= 7.1.0 and <= 7.1.7 and If the system already has database/storageVersion DASS, then leave its value as it is (do not override) else import the database/storageVersion DASS and value should be = 6.
2. If Upgrading or Updating from a version < 7.1.0 or > 7.1.7 and If the system already has database/storageVersion DASS, then leave its value as it is (do not override) else import the database/storageVersion DASS and value should be = 7.
3. If a fresh install of 7.1.8 and above, database/storageVersion DASS should be = 7.
Thanks,
Abhinav
Auto-Owners Insurance Group
US
Hi Abhinav, thank you for the explanation!
I do have one final question/clarification: Is there a future value >7 for storageVersion in Pega 8?
Pegasystems Inc.
IN
Hi Nick,
No,It accepts only till 7.Please see my above comment.
Thanks,
Abhinav