By default, for report SQL, if no aggregation is needed and the attribute defined on the table is not a primary key, the SQL engine uses SELECT DISTINCT in Select statement. In some scenarios, users would like to disable the usage of SELECT DISTINCT for specific query purpose.
The generation of Distinct or Group By in the SQL statement is controlled by a VLDB property called "Distinct/Group by Option(when no aggregation and not table key)" which is available at the Database Instance level. Follow the steps below to change the property.


The following three options are available for the VLDB property "Distinct/Group by Option(when no aggregation and not table key)". If the user would like to disable SELECT DISTINCT in report SQL, they can uncheck Use default and choose either "No DISTINCT, no GROUP BY" or "Use GROUP BY".
Below is a comparison of the report SQLs generated when each option is applied.
select distinct a11.ITEM_COLOR_ID ITEM_COLOR_ID, a11.COLOR_DESC COLOR_DESC from DSSADMIN.LOOKUP_COLOR a11
select a11.ITEM_COLOR_ID ITEM_COLOR_ID, a11.COLOR_DESC COLOR_DESC from DSSADMIN.LOOKUP_COLOR a11
select a11.ITEM_COLOR_ID ITEM_COLOR_ID, max(a11.COLOR_DESC) COLOR_DESC from DSSADMIN.LOOKUP_COLOR a11 group by a11.ITEM_COLOR_ID
When none of the above conditions are met, the option selected for this property determines how DISTINCT and GROUP BY are used in the SQL statement.