Forum Discussion
Helper IIhow to force inner joins in direct query SQLs?
Helper IIright, its first for performance reasons.
but also for functionnal point, as the left join results in NULL values in my case.
I have a log table which is like:
Source, LogID, Severity, Timestamp, message (and other columns)
and a table which is a list of possible sources
Source, sourcename, sourcedescription
I want to display the number of logs by sourcename.
but I have some logs without a related source, the left join results in a NULL value and PowerBI display this in the chart.
the possible source table is not the only one connected to my log table. so having inner joins will solve my problem by returning only good values for the users and also will improve the performance as an inner join provides better results than outer joins.
remember that I'm using direct SQL queries.
For now I'm in demo mode, and I'll be able to create custom SQL statements or views if there is no out of the box solution.
Responsive ResidentWillgart Understood, since you are using a direct query your options are limited. Best practice would be to create a default member for your null values in general there shouldn't be any nulls in your data set. for example on your log fact table you should replace your nulls with a default value lets say "Missing Source". In your source table you should have this default value as well "Missing Source". You can than filter out these values. Also if your users wanted to preform cleanup of this data in the future they could create reports to see how many logs are being created without Sources. Heres some additional intofrormation Link. Hope this helps.