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
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v43 minutes agoCommunity ChampionNew606Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v8 hours agoCommunity ChampionNew12Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019711 hours agoFrequent VisitorNew6Views0likes0Comments