Data Quality rule using two tables(datasources) columns throwing exception with the second table not found error
Hello,
We have 2 scenarios,
1.In one of our Data quality rule where the rule condition to be checked on the multiple columns of multiple tables of same schema
2.In another of our Data quality rule where the rule condition to be checked on the multiple columns of multiple tables of different schema
In both cases the second table is not identified while the rule is executed, though it is identified while profiling and we can see them in profile findings. But the rules throw exception with the second table not identified.
The rule is a freeform SQL and Sample query in the rule: SELECT a.* FROM TableA a LEFT JOIN Table2 b ON a.attr1 = b.attr2;
The rule throws Table2 b is not found error!
Hazeena Yoosaf
Posted 2 years ago · Edited 1 year ago·Last reply 2 years ago
2 comments
Hazeena Yoosaf
OP2 years ago · EditedAddlib is added; mssql is the datasource, pull up connection, both tables are from different schema of the same connection
George Luft
·2 years agoI would think this is because the two tables are in different schemas. Not sure if there is a way to fully qualify the table references in SQL Server to join across schemas. Have you opened a Support ticket for this?