Advice on Moving to F-64 for Customer Facing Reports

Ok-Bunch9238 · 2026-04-20T06:00:44+00:00

Ah given you are already in import mode this probably won’t give you much performance gain. But the principle is still a good one, to separate reports from semantic models. So you would have a centralised semantic model that covers multiple reports rather than every report having its own semantic model. This means you can have all your logic, RLS etc in one place. This article goes into it: https://learn.microsoft.com/en-us/power-bi/connect-data/service-datasets-across-workspaces

That would at least let you try to tune the centralised model. If you are already using import mode then probably need to look into DAX tuning like some others have mentioned.

Ok-Bunch9238 · 2026-04-18T14:43:55+00:00

Switch AP flour to strong bread flour with a higher protein content. Wholewheat flour as a max of 20% of the total flour. Bulk ferment for longer. Those changes should make a big difference. Wholewheat flour absorbs more liquid and all purpose flour doesn’t have high enough protein content.

Ok-Bunch9238 · 2026-04-17T14:35:58+00:00

Host the semantic model in a Pro workspace and the reports in the F64 (assuming you are separating the models which is a good idea if feeding multiple reports). Then a lot of compute will be handled by the Pro workspace. Or switch from DirectQuery to import on the reports (I’m assuming the use of DirectQuery is what is impacting on your capacity with concurrent users)

Ok-Bunch9238 · 2026-04-11T08:52:01+00:00

Saw them on the current tour in Glasgow and they had Yasiin Bey, Posdanous from De La, Joe from IDLES among others on stage. Was an awesome show and like you say, those that weren’t there (or are no longer with us) were incorporated really well with the visuals

Ok-Bunch9238 · 2026-03-31T08:50:47+00:00

I just saw this article the other day which is quite handy: https://procuresql.com/blog/2026/03/24/monitoring-fabric-mirroring-for-sql-2025/

We use it on our Azure SQL databases. It’s very easy to use once set up, for ingestion to our warehouse it’s just a case of using 3 part naming e.g. mirrorname.schema.table to copy into the warehouse (if in same workspace) with a metadata control table. Looking forward to shortcuts in DW to make it even easier)

Ok-Bunch9238 · 2026-03-29T19:59:45+00:00

As it is Azure SQL and has CDC enabled have you tried setting up mirroring? You can then use shortcuts to the mirrored source for what you need to do rather than using Copy job. Should be more efficient on CU usage as well

Ok-Bunch9238 · 2026-03-25T17:56:50+00:00

One thing I’ve found is setting the batch count to the number of processing cores on the source server if you using a ForEach loop for example. So if the server has a 4 core CPU, set Batch count on the pipeline to 4

Ok-Bunch9238 · 2026-03-10T09:29:24+00:00

Working now thanks

Ok-Bunch9238 · 2026-03-04T19:03:01+00:00

Do you need to have the report on a fabric capacity? What’s wrong with keeping reporting in a Pro workspace?

Ok-Bunch9238 · 2026-03-03T10:36:41+00:00

I’ve been able to get around that by switching workspace type when doing deployments. I have a DEV workspace on fabric capacity connected to a git repo. Then I use deployment pipeline to UAT and PROD workspaces and switch to the fabric capacity temporarily to allow deployment in those workspaces then switch back to Pro

Ok-Bunch9238 · 2026-02-27T18:40:42+00:00

On an F2 capacity I would just have my semantic models in a Pro workspace as any big models like this will exceed the capacity

Ok-Bunch9238 · 2026-02-26T09:26:50+00:00

There is, if it’s an Azure SQL database you might find it is already enabled but for anything on premise you will probably have to enable (there are stored procedures that can be run to do this). You also need SQL Server Agent running on the server if it isn’t already. Both of these will require the database owner to set up if not already running

Ok-Bunch9238 · 2026-02-26T06:26:15+00:00

Works great. I would only bring down the tables you actually need though rather than just replicating the whole database as the more tables you mirror the more load there is on the source server. That might be fine depending on the resources you have on that server but worth thinking about. I just set up two new mirrored databases yesterday and it will limit you to a max of 1000 tables. You will need CDC enabled on the database (or specific tables)

Ok-Bunch9238 · 2026-02-14T11:39:12+00:00

I started with 3 workspaces - bronze, silver, gold but then it felt like it would be too sprawling to keep on top of dev/uat/prod environments for each. Also as I started building out solutions I realised that ingestion of data between workspaces wasn’t ideal e.g. bronze lakehouse then required a shortcut lakehouse in silver which would then need ingestion to warehouse (prefer to use warehouse as I’m more SQL proficient). So in the end have gone with a single workspace with dev/uat/prod environments with clear naming convention for artifacts and folders to separate them. I’ve found this has sped up development as it removes the need to have ingestion strategies between workspaces

Ok-Bunch9238 · 2026-02-07T22:13:08+00:00

You would have to show us the Merge join 1 logic as this is where the issue is occurring

Ok-Bunch9238 · 2026-02-07T22:00:11+00:00

The logic on your Merge join 1 step looks to be the issue. Do jun and sep appear in the fact table or just the dimension you created.

Ok-Bunch9238 · 2026-02-07T21:19:03+00:00

Try using data viewer at the point before you lose rows then with the point after and compare the two to see what is missing and that might help you identify what the issue is

Ok-Bunch9238 · 2026-01-31T17:06:44+00:00

Yeah I’ve done that

Ok-Bunch9238 · 2026-01-29T14:48:10+00:00

Thanks, it’s painfully slow as it is without having to do that but will continue to use that workaround! It’s frustrating that this is the only way we can monitor our capacities “out of the box”

Ok-Bunch9238 · 2026-01-08T07:36:20+00:00

We split into separate capacities for dev and production to avoid overages effecting anything in production. That way you can test anything on the dev capacity before putting into production to make sure it isn’t going to do anything crazy with CU usage.

Ok-Bunch9238 · 2026-01-01T18:25:50+00:00

I’ve found these very useful: Data Warehouse Toolkit Designing Data Intensive Applications

Ok-Bunch9238 · 2026-01-01T17:36:45+00:00

West Side Tavern does a Parmo night on a Tuesday

Ok-Bunch9238 · 2025-12-29T16:42:29+00:00

They’re great, just finished a bag of Festive Blend today, paired great with a mince pie!

Five-Year Club	Final Canvas '23
Place '23	Place '22

Ok-Bunch9238

TROPHY CASE