ClientVersionPrecision

This parameter lets you more precisely identify the minimum and maximum versions of clients that can connect to the Planning Analytics database.

Parameter type: optional, dynamic

The ClientVersionMinimum and ClientVersionMaximum parameter values are expressed as a version string using the following format:

m.n.tffhh

m = major release number,

n = minor release number

t = maintenance release number

ii = interim fix number

Using this format, the version string 9.4.10305 indicates major release 9, minor release 4, maintenance release 1, fix pack 3, and hot fix 5.

If ClientVersionPrecision is not set in the Planning Analytics database configuration or if it is set to 0, only the major release number, minor release number, and maintenance release number are used to enforce compatibility between client and database. In this case, any client from major release 9, minor release 4, maintenance release 1 and more recent can connect to the database.

You can enforce more precise database and client version compatibility by adding ClientVersionPrecision to the Planning Analytics database configuration and setting the parameter to one of the following values.

1 - Indicates that the fix pack number will be enforced, but not the hot fix number.
2 - Indicates that both the fix pack number and hot fix number will be enforced.

Examples

If ClientVersionMinumum = 9.4.10305 and ClientVersionPrecision = 1, only clients from major release 9, minor release 4, maintenance pack 1, fix pack 3 or later can connect to the database. In this case, the hot fix number is not enforced when determining database/client compatability.

If ClientVersionMinumum = 9.4.10305 and ClientVersionPrecision = 2, only clients from major release 9, minor release 4, maintenance pack 1, fix pack 3, hot fix 5 or later can connect to the database. In this case, both the fix pack and hot fix numbers are enforced when determining database/client compatability.