The Database Settings allow administrators to adjust how Exago interfaces with databases. Additional type-specific settings allow you to specify which driver to utilize when connecting to each data source.
The following Database Settings are available:
Maximum number of seconds for a single query to run.
Note: This setting will also control the maximum number of seconds that a Web Service Api method can run. If set to ‘0’ the Web Service time out will be ‘infinite’.
Database Row Limit
Maximum number of rows returned on an execution. This only applies to Tables, Views and Functions. Set to '0' to return all rows.
Row Limit Step Size (v2017.2+)
Maximum number of rows returned on a query. Set to '0' to return all rows. Set to > '0' to enable Incremental Loading for Advanced Reports and ExpressViews. The value determines how many rows are returned for each user-initiated data query.
Disable Non-Joined Data Objects
If True users are not able to add Data Objects to a report that does not have a join path with at least one other Data Object on the report. Set to False to disable this behavior.
Enable Special Cartesian Processing
If True any one-to-many Joins will cause special processing to avoid data repeating on the report. Set to False to disable this behavior.
Aggregate and Group in Database (v2016.3+)
If True, aggregate and grouping calculations will be done in the database when possible. This will provide a performance boost for reports with group sections.
Important: Before enabling this, you must ensure that all One-To-Many Joins in your environment are correctly identified and set as One-To-Many in the Join options menu. If these joins are not properly identified, reports which utilize them will return incorrect aggregate data. See Database Aggregation for more information.
Convert Filter Formulas to SQL (v2018.2+)
If True, Exago, when possible, will convert formula filters to SQL, placing it in the WHERE clause when querying data for the report. If set to False, all formula filtering will happen in memory.
Warning: Due to innate difference between Exago's formula engine and SQL database engines, there may be discrepancies in data returned between two methods. Additionally, because the converted SQL formulas may contain arbitrary input, the connection string must read-only access. For more information please see the Database Formulas article.
Type-Specific Database Settings
Each Type of Data Sources has the following settings available.
The name that can be used programmatically to refer to the data provider. This matches the InvariantName found as a property of DbProviderFactories in the machine.config file. See this link for more information.
Table Schema Properties
Specifies how to retrieve the schema of tables.
View Schema Properties
Specifies how to retrieve the schema of views.
Function Schema Properties
Specifies how to retrieve the schema of functions.
Procedure Schema Properties
Specifies how to retrieve the schema of procedures.
Note: For any of the Schema Property settings you can dynamically refer to properties from the Data Source’s connection string by surrounding the property name in @ symbols. For example, "@database@" will be replaces with the database name from the connection string of the Data Source being queried.