Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hello!
I'm testing out the database in Fabric and I'm really surprised of the CU usage, it's eating up all available resources.
It's an F2 license.
When I'm connected to the database with SSMS or VS Code, the CU usage goes to 80-100%, and when I close the connection the usage drops to normal levels.
I'm not doing anything (querying, inserting etc.), it's just an active connection to the database in one of the tools (VS Code or SSMS).
Is this expected behavior?
The warehouse does not behave in this way, I see no spikes in CU when connected with VS Code/SSMS all day long.
Hi @agranaas
Tools like SSMS/VS Code often run background queries (e.g., fetching metadata for IntelliSense, refreshing object explorer, checking session status). These lightweight queries can spike CU usage on low-tier capacities (F2).The F2 SKU has minimal CU allocation (2 CUs). Even minor background activity can max out resources. Higher SKUs (F4+) buffer this better.
Best Regards,
Jayleny
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Do you have any idea why the warehouse does not behave in the same way?
Open connections to the warehouse has no impact on CU usage from what I have seen.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.