There is currently no way to control the scaling of an SQL DB. There should be a way to limit the database from scaling above a certain size. And / or a way to set a fixed cost/size (similar to DTU purchasing model).
4 Comments
- fbcideas_migusrNew MemberStatus added:New
- akatesmithMicrosoft EmployeeStatus changed:NewtoUnder Review
We are aware of this limitation and the challenges it causes.
- RasmusRymarkNew MemberIt seems that there's onlý "one size" right now. We're using the SQL DB for meta-data about pipeline/notebook runs only - so some sort of Small/Medium/Large would be nice. Some sort of "sizing", anyway 🙂
- sukkaurMicrosoft EmployeeStatus changed:Under ReviewtoCompleted
you can change the max vcore by going into Settings option in Web editor.
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias2 hours agoRegular VisitorNew2Views0likes0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu4 hours agoMicrosoft EmployeeNew6Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb5 hours agoNew MemberNew3Views0likes0Comments