It has the cheapest instance types, and the lowest resources so if it is doing a job for you, then there is no need to change. If you are on the basic service tier, then from a cost optimization process there is not too much more to say. Azure SQL Single DB comes with a choice of Basic, Standard and Premium. Azure SQL Database Service TiersĮnsure you are on the right service tier. Any instance using < 50% of CPU is a good candidate for scaling down. I would apply a similar rule to scaling up or down here based on needs. Managed Instances only use the vCore purchase model. There is no way to allocate extra memory however, this is bound to the number of vCores you have. You can choose your compute and storage resources separately. The vCore purchase model provides more flexibility than the DTU model. (Providing the lower class has enough storage) Again, adjust this to suit your own needs but there is no need to pay double unless you absolutely need to bake in a lot of spare capacity. If you are averaging below 50% and have few or no peaks above this, you can scale down. You can adjust this figure based on how relaxed or nervous you are the DTU getting pinned at 100%. If you are averaging above 85% and have regular peaks higher than that for DTU usage, you should scale up. When monitoring performance, you should be looking mainly at DTU percentage used and storage percentage used. They come with fixed storage per instance type. Small to medium single databases can use the DTU purchase model which is a blend of cpu, memory and IO. With this operating model, you should only pay for what you need, and adjust your scale as driven by demand, not future projections. Pay As You Go cloud solutions fall under operational expenditure (OPEX) as they are ongoing costs. Items such as electrical power, rent and staff salaries come under OPEX. Operational Expenditure (OPEX) on the other hand describes ongoing costs and operating expenses. For something like a database server, you might forecast what size you will need in 5 years and buy accordingly. It’s a big upfront expense to provide long term value. Once it is purchased, you don’t need to buy it again and can use it until it outlives is usefulness. CAPEX vs OPEXĬapital Expenditure (CAPEX) describes where an up-front purchase is made to provide value into the future. With the cloud, you should shift your thinking from a CAPEX operating model to and OPEX operating model. You should be ready to scale up or out when the time is right but not before. The rest will be available when you need them. With Azure SQL Database, there is no need to buy that 32 vCore service, when all you need right now is 4. Your cloud services should be scaled at the right size to handle current workloads, with a small buffer. With the cloud, it’s important to understand the concepts of scaling and elasticity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |