Dear All,
When we design the RPD, we always focus on implementing the business concepts but we forget to work on the basic repository features.
One of the cases, is the Database Setting.
Not setting this correctly will affect the features table which is automatically populated with default values appropriate for the database type. These are the SQL features that the Analytics Server uses with this data source. As a result this may enable SQL features that the database does not support; queries may return errors and unexpected results. Also as a consequence of selecting the wrong database type it may result in disabling supported SQL features, the server could then issue less efficient SQL to the database.
Reagrds,
Angad
Please post as a comment for any queries.
When we design the RPD, we always focus on implementing the business concepts but we forget to work on the basic repository features.
One of the cases, is the Database Setting.
The database type has not been correctly defined in the database object in the physical layer.
Lets suppose, you are using Oracle 11G version as the database and in RPD modelling you have defined Oracle 10G version like below.
Not setting this correctly will affect the features table which is automatically populated with default values appropriate for the database type. These are the SQL features that the Analytics Server uses with this data source. As a result this may enable SQL features that the database does not support; queries may return errors and unexpected results. Also as a consequence of selecting the wrong database type it may result in disabling supported SQL features, the server could then issue less efficient SQL to the database.
The database type should be correctly defined in the
database object, and should be set to Oracle 11g, as provided in the list
below:
Reagrds,
Angad
Please post as a comment for any queries.
No comments:
Post a Comment