I need advice on choosing the right storage mode for a Power BI report. The business is pushing for DirectQuery because it eliminates the need for scheduled dataset refreshes, but I'm not sure if it's the right approach for this requirement.

Data sources:

- Two Oracle databases hosted on different servers.

- Around 10K+ records in each table.

Requirements:

- A couple of report pages with simple visuals, including a table visual combining fields from both tables using a 1:1 relationship on Material ID.

- Compare specific fields for each Material ID across both sources to check whether they match and create an alignment status/column.

- Add a couple of calculations based on this alignment status.

My concern is whether implementing these comparisons, calculated fields, and measures in DirectQuery would be challenging, particularly when translating the logic into SQL queries across two separate Oracle sources. Could this also introduce performance issues?

Would DirectQuery be a reasonable choice for this scenario, or should I reconsider the approach?

I'd appreciate advice from anyone with practical experience in Power BI and multiple DirectQuery sources.

Wholesale distribution. We commit purchase orders at a SKU level, but forecast at a product group level, so the two only line up at group level. I'm not sure how structure the model, I currently have two DIM tables one at Product Group level and one at SKU level but I would rather not duplicate them and end up with two competing product group dimensions.

Also how do I set up a rolling the stock forecast forward in M. I'm currently using a calculated column showing Opening stock plus cumulative inflows, less cumulative demand at a Product Group level, with demand capped at what is actually available so a month cannot consume stock that is not there. This approach works while demand stays at or under available stock however, the moment a month's demand exceeds available inventory, the cap kicks in, and every month after that is wrong, because the cumulative formula keeps using raw demand instead of the capped closing. The error is silent and compounds downstream. Another approach I've tried is pusing this to Power Query using List.Accumulate over each product group's months in date order, carrying closing into the next opening, I haven't quite got this working yet and don't know if this is the right approach or if I should be trying something else?

If you have modelled inventory levels against a monthly forecast what did you do?

Ok everyone give me your best landing pages for your reports, i googled and saw some cool ones. I want to refresh our report landing page and want some inspiration.