Thank you, @Anonymous, for a fast and enlightening answer!
I can consider using shortcuts.
However, another option I am wondering about, which would be easier to set up and maintain, is if I create a Power BI report (not semantic model) in a workspace in Capacity B, and this report is connected to the semantic model in Capacity A via live connection.
Will Capacity B (where the report resides) or Capacity A (where the semantic model and lakehouse resides) be regarded as the consuming capacity in this case with regards to throttling? (Ref. this doc which distinguishes between the terms producing capacity and consuming capacity).
Will the transactions when a user is reading the report, be counted against capacity B or capacity A?
Another question: I am happily surprised to learn that shortcuts can access data from a paused capacity.
Because this documentation says that data in a paused capacity is inaccessible.
At the same time, this documentation says that a shortcut can access data from a paused capacity, which is great.
If I understand correctly, a shortcut created in Capacity B could access data which resides in Capacity A, even if Capacity A is paused.
Is it only shortcuts which have a special ability to access data from a paused capacity?
Or can other types of Fabric/Power BI workloads also access data from a paused capacity (without using shortcut).
This documentation says that if a OneLake artifact (I guess that means OneLake data) on capacity A is being consumed by capacity B, then only the throttling state of the consuming capacity B matters. Which, in my mind, kind of implies that all the transactions when accessing OneLake data would be counted against the consuming capacity. This documentation doesn't make a distinction between using shortcut/not using shortcut.
However this documentation implies more strongly that the OneLake transactions are being counted against the owning (aka producing) capacity when accessing it's data, unless I am using shortcuts in which case the OneLake transactions will be counted against the capacity where the shortcut is created.
I guess what maybe confuses me, is that the documentation regarding throttling says that only the throttling state of the consuming capacity matters.
However, the documentation regarding OneLake transactions implies that OneLake transactions are counted against the owning (producing) capacity, unless using shortcuts.
Does this mean, even if I can access the data on a throttling capacity A from a non-throttling capacity B, that the OneLake transactions will be counted against capacity A and add to the overload on capacity A?
(I understand that Shortcuts changes the logic here, so if I am using Shortcuts the OneLake transactions are counted against the consuming capacity. Which is nice.
But I am asking about the case where I am not using shortcuts, but a situation where I have a Power BI report in Capacity B (non-throttling) while the semantic model and lakehouse is in Capacity A (in throttling or reject state).
Or similarly, if I have a notebook in Capacity B which is querying data from Capacity A).
Thank you!
