Gilbert Quevauvilliers saves some money:
After reading about the new SQL Pools feature for Warehouses in Fabric, I had an idea, if I could change the SQL Pool configuration based on the expected query load, I could then consume less capacity and have better performance.
https://learn.microsoft.com/en-us/fabric/data-warehouse/custom-sql-pools
Here is an Example I thought of below.
- When the ETL load is running optimize the SQL pool for writing as typically data is being inserted.
- After the ETL load and for the rest of the day, almost all queries are read by the Warehouse, so change the SQL pool to be read optimized.
Click through for a Python notebook that does this.