Amazon RDS for SQL Server FAQs

Please visit Amazon RDS for SQL Server Pricing for complete DB instance and regional availability information.

Instance pricing is calculated from the time the instance is created to the time the instance is deleted. Instances are billed in one second increments with a 10 minute minimum charge following a billable status change such as creating, modifying, or deleting an instance.

As an example, if you create an r5.large instance at 1:00:00 PM, modify the instance to an r5.xlarge at 1:30:00 PM and delete the instance at 1:50:00 PM, you will be charged for 1,800 seconds (30 minutes) at r5.large pricing and 1,200 seconds (20 minutes) at r5.xlarge prices. If you create an r5.large instance at 3:00:00 PM and delete it at 3:06:00PM, the 10 minute minimum applies, and you will be charged for 600 seconds (10 minutes) at r5.large pricing.

No. The Amazon RDS for SQL Server price includes the software license, underlying hardware resources, and Amazon RDS management capabilities.

The storage size of a database instance can be set anywhere between 10GiB to 16TiB. You can automatically grow your database storage with no downtime by leveraging the Auto-Scale Storage Feature.

You can increase the storage size as often as you want but you will need to wait 6 hours from the previous scale.

You can scale the compute resources allocated to your instance in the AWS Management Console by selecting the desired instance and clicking the “modify” button. Memory and CPU resources are modified by changing your instance class.

When you modify your instance class, your requested changes will be applied during your specified maintenance window. Alternatively, you can use the "Apply Immediately" flag to apply your scaling requests immediately. Both of these options will have an availability impact for a few minutes as the scaling operation is performed. Bear in mind that any other pending system changes will also be applied.

By default, Amazon RDS enables automated backups of your DB Instance with a 7 day retention period. Free backup storage is limited to the size of your provisioned database and only applies to active DB Instances. For example, if you have 100 GB of provisioned database storage over the month, we will provide 100 GB-months of backup storage at no additional charge.

If you would like to modify your backup retention period, you can do so using the console or the CreateDBInstance API (when creating a new DB Instance) or the ModifyDBInstance API (for existing instances). You can use these APIs to change the RetentionPeriod parameter to any number from 0 (which will disable automated backups) to the desired number of days. The value can't be set to 0 if the DB instance is a source to Read Replicas. For more information on automated backups, please refer to the Amazon RDS User Guide.

Yes, you can also back up your DB instance manually by manually creating a DB snapshot. For more information about creating a DB snapshot, see Creating a DB snapshot.

When you delete a DB instance, you can create a final DB snapshot upon deletion; if you do, you can use this DB snapshot to restore the deleted DB instance at a later date. Amazon RDS retains this final user-created DB snapshot along with all other manually created DB snapshots after the DB instance is deleted. Refer to the pricing page for details of backup storage costs.

Yes, with Amazon RDS, you can copy automated or manual DB snapshots. After you copy a snapshot, the copy is a manual snapshot.

You can copy a snapshot within the same AWS Region, you can copy a snapshot across AWS Regions, and you can copy shared snapshots.

Amazon RDS supports Multi-AZ deployments for Microsoft SQL Server by using either SQL Server Database Mirroring (DBM) or Always On Availability Groups (AGs). Multi-AZ deployments provide increased availability, data durability, and fault tolerance for DB instances. In the event of planned database maintenance or unplanned service disruption, Amazon RDS automatically fails over to the up-to-date secondary DB instance.

Go to Multi-AZ deployments for Amazon RDS for SQL Server to learn more.

Yes, you can create up to five read replicas from one source DB instance.

Yes, you can create cross-region read replica for your Enterprise Edition workloads.

The primary and standby instances use the same endpoint, whose physical network address transitions to the secondary replica as part of the failover process. You don't have to reconfigure your application when a failover occurs.

Traffic on port 3343 for TCP and UDP needs to be allowed both in Network ACLs of your VPC and in the Security Group that is attached to your Amazon RDS for SQL Server Multi AZ instance. This traffic is needed for both in-bound and out-bound directions. Please note that the traffic on this port is only required within the VPC in Network ACLs and within the Security Group that is attached to the RDS SQL Server instance.

If you have not deleted the default inbound and default outbound rules in your ACL, then you do not have to take any further action on your ACLs.

Allow traffic on the port 3343 for UDP and TCP in the Security Group that is attached to your RDS SQL Server Multi-AZ instance.

Not allowing traffic on the port 3343 for UDP and TCP can cause unexpected failures in WSFC service. Even if you have not seen any failures so far, you may see them in the future. It depends on how and when the WSFC service needs traffic on port 3343. Also, your instance may currently be using an engine version that is not using AlwaysOn for Amazon RDS for SQL Server. In which case Amazon RDS for SQL Server would be using Database Mirroring for providing Multi-AZ, and port 3343 is not required. However, in the future you may upgrade to a version that is using AlwaysOn on Amazon RDS for SQL Server, and you must allow this traffic.

The following documents are available to guide you through how to modify Network ACL to add ACL rules, add Security Groups (egress) rules, and add Security Groups (ingress) rules.

The 'max server memory (MB)' setting is used to let SQL Server know how much physical memory it can reserve for its buffer pool. Configuring a maximum allowable value for this setting ensures the operating system (OS) and other processes won't compete for memory with the SQL Server process. This helps to prevent memory pressure issues and increases the stability of the database instance.

• If the instance has less than 2 GB, then the maximum allowable value of ‘max server memory (MB)’ is total memory - 200MB. 

• If the instance has less than 8 GB, then the maximum allowable value of ‘max server memory (MB)’ is total memory - total memory*1/8. 

• If the instance has less than 64 GB: then the maximum allowable value of ‘max server memory (MB)’ is total memory - total memory*1/16. 

• If the instance has 64 GB or more, then the maximum allowable value of ‘max server memory (MB)’ is total memory-4GB.

Yes, this is because 60GB is the maximum allowable value of 'max server memory (MB)' on a DB instance with 64GB of total memory.

According to the maximum allowable values mentioned above, the new value will be set to 60GB. After the value is applied to your database instance, you will see an event in AWS console or via CLI that says 'max server memory (MB)' value has been reset to 60GB.

Yes, you are allowed to customize this value up to the maximum allowable value mentioned above. In this case the maximum allowable value is 60GB.

We will calculate a new default value similar to the AWS documentation on your behalf and apply that to your database instance.

After March 7th, 2023, we will apply the new default parameter value to your instance as per the memory calculations mentioned above.

No, you may see “Pending Reboot” status for your parameter group on the RDS console, but a reboot is not required for your database instance as the 'max server memory (MB)' parameter change would have been automatically applied. This message will clear after the next instance reboot and no action is needed.

Based on the available memory on the new database instance and according to the memory calculation mentioned above, we will reset the ‘max server memory (MB)’ to 30GB on your new database instance.

No, there is no downtime to change the 'max server memory' configuration.