Scribd Logo
Upload

Welcome to Scribd!

  • 4 views

    SQL Tip14

    Uploaded by

    Vamsi Chowdary
    1. There are several ways to reduce the cost of Azure SQL, including keeping databases in the appropriate service tier based on usage, scaling databases down to lower tiers during non-business hours, keeping secondary databases in a lower tier than the primary, and automating the starting and stopping of VMs when not in use. 2. Other options are using elastic pools to optimize resource usage across multiple databases, using the serverless tier for intermittent usage, taking advantage of reserved instances for discounts of up to 75%, and purging or archiving large tables to reduce storage costs. 3. Tools like the Azure calculator can help estimate costs and compare pricing differences between options.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    SQL Tip14

    Uploaded by

    Vamsi Chowdary
    4 views1 page
    1. There are several ways to reduce the cost of Azure SQL, including keeping databases in the appropriate service tier based on usage, scaling databases down to lower tiers during non-business hours, keeping secondary databases in a lower tier than the primary, and automating the starting and stopping of VMs when not in use. 2. Other options are using elastic pools to optimize resource usage across multiple databases, using the serverless tier for intermittent usage, taking advantage of reserved instances for discounts of up to 75%, and purging or archiving large tables to reduce storage costs. 3. Tools like the Azure calculator can help estimate costs and compare pricing differences between options.

    Original Description:

    Original Title

    SQL TIP14

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    1. There are several ways to reduce the cost of Azure SQL, including keeping databases in the appropriate service tier based on usage, scaling databases down to lower tiers during non-business hours, keeping secondary databases in a lower tier than the primary, and automating the starting and stopping of VMs when not in use. 2. Other options are using elastic pools to optimize resource usage across multiple databases, using the serverless tier for intermittent usage, taking advantage of reserved instances for discounts of up to 75%, and purging or archiving large tables to reduce storage costs. 3. Tools like the Azure calculator can help estimate costs and compare pricing differences between options.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    4 views1 page

    SQL Tip14

    Uploaded by

    Vamsi Chowdary
    1. There are several ways to reduce the cost of Azure SQL, including keeping databases in the appropriate service tier based on usage, scaling databases down to lower tiers during non-business hours, keeping secondary databases in a lower tier than the primary, and automating the starting and stopping of VMs when not in use. 2. Other options are using elastic pools to optimize resource usage across multiple databases, using the serverless tier for intermittent usage, taking advantage of reserved instances for discounts of up to 75%, and purging or archiving large tables to reduce storage costs. 3. Tools like the Azure calculator can help estimate costs and compare pricing differences between options.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    SQL TIP14.

    Some of the Real-time scenarios where you can reduce the cost of Azure
    SQL?
    Answer:
    1. Keep the database in right service tier. No excessive resources. No inadequate resources.
    Regularly monitor the resource usage graph and take the decision.
    2. You can keep the Databases in low tier(scale down) in non-business hours/Night
    times/Weekends As the usage is the low. Better automate this task
    3. In Geo-replication, you can keep the Secondary database in lower tier. There is no rule to
    keep the databases (primary and secondary) in same tier.
    4. Very important thing is, try to use Failover groups only for HA(Reports) option. No need
    to use DR purpose as no failure cases of Azure SQL Databases. These DB’s are always
    available
    5. Also use Data-Sync option for HA. Data-Sync is a table level and works like as a
    Transaction replication. Here you can keep the schedule s well to sync target DB.
    6. If possible make the DB’s in elastic pool rather keeping in single DB model. Check the All
    database utilization and go for this, if DB usages are unpredictable
    7. Stop the VM’s, when you not using on schedule basis. You can automate this task.
    8. If you have requirements like need more storage with less CPU and Memory and/or less
    CPU with more memory and/or vice-versa, go for VCore model rather DTU Model. Vcore
    model is like Independent scaling IO, CPU and Memory.
    9. You can use azure calculator to know more about the price differences. Cost also vary
    depend on region
    10. Take help of DTU-Calculator and AZURE-Calculator to estimates the costs and know the
    price differences.
    11. Go for reservations/Hybrid concept for discounts. You can get almost 75% discount.
    12. If Intermittent, unpredictable usage of databases, go for servers less model in General
    purpose Vcoremodel to save the huge cost.
    https://docs.microsoft.com/en-us/azure/azure-sql/database/serverless-tier-overview
    13. For automating the jobs, go for using runbooks which are very cheaper rather elastic
    jobs but Monitoring is tough in runbooks.
    14. Check out the databases backup retention and their redundant storages. Don’t blindly
    depended on default options.
    15. Go for purging/Archiving/Partitioning on large tables
    16. Use the Read-Scale benefit when the DB is in Premium/Business critical tiers
    <Contact me (WhatsApp https://wa.me/919966246368 ) for Real-time Azure SQL DBA
    Training's & Live class room recorded sessions and Material and scripts>

    You might also like