SQL interface
There are two cases for using the SQL interface:
- Relational planning.
Users want to display data from the in a table-like fashion in Application Studio. The data can be modified and then written back.
- No filters on values are
needed: the request filters only on elements of one or more dimensions. For
example:
Products = 'Monitor 22 LCD' AND Region = 'Italy' - Although aggregated
values are not be displayed in this use case, it provides a way to select all
children of a given level in a hierarchy. For example:
Region = 'Europe'
- No filters on values are
needed: the request filters only on elements of one or more dimensions. For
example:
- Query on attributes tables.
Users want to run queries on a dimension and its attribute tables. The returned list must take the permissions of the user into account. This is sometimes used in applications built with Application Studio to store a menu structure. In this case, the dimension does not need to be a part of any cube.