In my last blog I explained about Azure Policy, concept and creating it. Next action after creating or changing an policy is to see whether is it working or not. Unlike most other azure features where change are propagated immediately, azure policy trigger does not happen immediately after SAVE.
Interval of Evaluation of policies depend upon type of policy change (new or update), effect and resource deployment.
Continue reading “Trigger Azure Policy on demand”
Following is the evaluation interval
Compliance evaluation frequency
On change (New/Update policy Assignment) ~ 15 min after resource change
On periodic cadence ~ Every 24 hours
On demand ~ 3 min
What is Elastic Pool: As the name suggests it is a pool of SqlAzure Dbs.
- Each elastic pool contains sets to SqlAzure dbs.
- Elastic pool has shared capacity among SqlAzure dbs.
- Elastic pool ensures best use of capacity and resource.
- It is very much cost effective also.
- Best option for dealing with unexpected db load at same time remaining cost effective.
- While creating elastic pool, Azure provides suggestion about which db to include in the pool and about min mac DTU, bases on DTU usages of Dbs.
Example: Let’s assume you have 10 basic SqlAzure dbs, which normally use 5 DTUs. During setup in Azure you assign each Db 10 DTU (considering scaling\peak) i.e total 100 DTU while most often consumption is 50 DTUs on average. So, you are paying for 50 DTU extra i.e double.
By putting then in elastic pool and setting the max DTU at a level (for ex: 60), you can handle unexpected db load and achieve cost effective solution.
P.S: In the above example, there is an assumption that all dbs don’t achieve peak at the same time.
Continue reading “Azure Elastic Pool and Elastic Job”