By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Scaling Down RDS Running SQL Server Standard Edition

0

The above-mentioned database is running a db.m4.4xlarge instance (16vCPU, 64GB RAM) . But from the monitoring data of last 6 months, it looks heavily underutilized Enter image description here Enter image description here Enter image description here Enter image description here Enter image description here Enter image description here Enter image description here Where average CPU connection is max 20% and DB connections are max 15. To reduce the cost, I want to scale it down. But, I don't know how to pick the right instance size. Should I just go 1/2 or 1/4 size down? For example, I was thinking about db.m4.xlarge/db.m5.xlarge(both 4vCPU, 16 GB RAM), also m6ixlarge(I'm unsure if it supports SQL Server Standard Edition ).

Is this alright or any other suggestion or how to pick?

Moreover, I just modify the instance with the whichever size I pick and AWS will move the database data's inside it, right?

Topics
DatabaseMigration & ModernizationAnalyticsAWS Well-Architected FrameworkCloud Financial ManagementFinOps
Tags
Microsoft SQL ServerAmazon Relational Database ServiceCost OptimizationCloud Financial ManagementFinOps
Language
English
Ash
asked 9 months ago419 views
1 Answer
1
Accepted Answer

Yes you can just modify the instance type and it will transition the db's as such.. (requries downtime)

The next size down is half (2xlarge). You will not be able to reduce by 1/4.

Yes, SQL Server is supported on m6i, i have deloyed on this type already.

You didnt provide a screen shot for yor memory, so that would need reviewing also.

However, I would look carefully at your IOPS and review your Storage configuration if your using Provisioned IOPS and your stroage type may also help changing to GP3 if you havent already. Also check and if you have a long disk queue also?

profile picture
EXPERT
Gary Mclean
answered 9 months ago
profile picture
EXPERT
Giovanni Lauria
reviewed a month ago
  • Ash
    9 months ago

    Thank you for answering. I'm new to this domain so I didn't know what details to provide exactly. Why can't I reduce it by 1/4? I have provided the screenshot of memory, IOPS, throughput, disk queue, and storage. Yes, I haven't updated to GP3, that's also on my list.

    Please advise.

    Also, it would be helpful to know if you have any article guide to understand how to use above-mentioned metrics to understand the right db size.

  • Gary Mclean EXPERT
    9 months ago

    You can reduce by 3/4 but not by 1/4. You are at a 4xlarge.. You can go to a 2xlarge which is 1/2 You can go to a xlarge which is 3/4 which is may be what you mean 1/4 of what you have but its a reduction of 3/4 Your disk queue seems high.. Your storage auto scailing has maxed out btw.. Have you checked the free space?

  • Gary Mclean EXPERT
    9 months ago

    Im not sure if you will run out of RAM if you drop the instance size! I know traditional SQL Server can take x% of memory and allocate it to the process. Need to check if same with SQL on RDS

  • Gary Mclean EXPERT
    9 months ago

    Whats the EBSIOBalance ?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content