When you upgrade the Intelligence Server, the Data Engine quotes all the Warehouse identifiers. In some situations, when a table prefix contains multiple segments, the quoting behavior may lead to report failures.
Note: Only some warehouses may have this issue, for example, Microsoft SQL Server.
maindb.tpchis quoted as a whole, which causes a syntax error in the query, leading to the report execution failure.
The Data Engine does not support multi-segment table prefix for all databases.
Warehouses hosted on databases, like Microsoft SQL Server, do not usually need to use table prefix. There are some databases like the Snowflake, which needs to use a multi-segment table prefix. For those databases, the Data Engine uses an internal table pattern and will quote the table prefix correctly.
For example, if the above case used a snowflake warehouse, the SQL View will look like this:
The behavior is expected as the Data Engine does not support multi-segment table prefix for Warehouses hosted on databases like Microsoft SQL Server. Users need to reevaluate whether the multi-segment table prefix is necessary and modify it accordingly. For example, in Microsoft SQL Server, there is no need to keep the database name in the table prefix. Please consider removing “
maindb.” and keep only the schema name “
tpch.” After editing the table prefix, please restart the Intelligence Server and rerun the report to verify if the issue is fixed.
