Forum Discussion
Architecture Best Practice
Current Architecture and Challenges We currently operate approximately 32 Fabric workspaces, each with its own Open Mirroring Database (OMDB). Users access data in several ways: Querying the SQL ...
Excel refreshes and model refreshes count as SQL work in Fabric. The two things that actually push SQL CU down are moving Excel users onto a small semantic model and cutting unnecessary refresh cycles. Keeping ad‑hoc SQL behind lightweight views also helps—heavy repeated calls drop off without touching anything risky.
For the bigger architecture angle, separating user‑driven SQL from OMDB—whether via a small SQL Pool or a dedicated serving workspace—is a common pattern to keep concurrency pressure under control.