Help Center/ Relational Database Service_RDS for SQL Server/ User Guide/ Parameters/ Modifying RDS for SQL Server Instance Parameters
Updated on 2026-09-11 GMT+08:00
View PDF
Share

Modifying RDS for SQL Server Instance Parameters

You can modify parameters in a custom parameter template to optimize RDS database performance.

You can only change parameter values in custom parameter templates. You cannot change the parameter values in default parameter templates.

The following are the key points you should know when using parameters:

  • Modifying instance parameters: When you modify dynamic parameters on the Parameters page of a DB instance and save the modifications, the modifications take effect immediately regardless of the Effective upon Reboot setting. However, when you modify static parameters on the Parameters page of a DB instance and save the modifications, the modifications do not take effect until you manually reboot the DB instance.
  • Modifying parameter template parameters: When you modify parameters in a custom parameter template on the Parameter Templates page and save the modifications, the modifications do not take effect until you have applied the template to your DB instances. For operation details, see Applying a Parameter Template. When you modify static parameters in a custom parameter template on the Parameter Templates page and save the modifications, the modifications do not take effect until you have applied the template to your DB instances and manually rebooted those DB instances.

When you modify a parameter, the time when the modification takes effect depends on the type of the parameter.

The RDS console displays the statuses of DB instances that the parameter template applies to. For example, if the DB instance has not yet used the latest modifications made to its parameter template, its status is Parameter change. Pending reboot. Manually reboot the DB instance for the latest modifications to take effect for that DB instance.

RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If an instance cannot be started due to incorrect parameter settings of its parameter template, you can reconfigure the parameters based on the default parameter template.

Modifying a Custom Parameter Template and Applying It to DB Instances

  1. Log in to the RDS console.
  2. Click in the upper left corner and select a region.
  3. Choose Parameter Templates in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  4. On the Parameters page, modify parameters as required.

    Relevant parameters are as follows:

    • Set remote access to 0 (default value) to prevent local stored procedures from running on a remote server and remote stored procedures from running on a local server.

    Available operations are as follows:

    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.

  5. After the parameter values are modified, you can click Change History to view the modification details.
  6. Apply the parameter template to your DB instance. For details, see Applying a Parameter Template.
  7. View the status of the DB instance to which the parameter template was applied.

    If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.

    • A DB instance reboot caused by instance class changes will not make parameter modifications take effect.
    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.

Modifying Instance Parameters

  1. Log in to the RDS console.
  2. Click in the upper left corner and select a region.
  3. On the Instances page, click the target instance name.
  4. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    Relevant parameters are as follows:
    • Set remote access to 0 (default value) to prevent local stored procedures from running on a remote server and remote stored procedures from running on a local server.

    Available operations are Save, Cancel, and Preview.

    • To save the modifications, click Save.
    • To cancel the modifications, click Cancel.
    • To preview the modifications, click Preview.
    In the Effective upon Reboot column:
    • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required the modifications to take effect.
      • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
      • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
    • If the value is No, the modifications take effect immediately.

    After the parameters are modified, you can view the change history.

Common Parameters

Table 1 Common parameters

Parameter

Description

Value Range

Default Value

Reference

remote query timeout

The time (in seconds) that a remote operation can take before SQL Server times out.

0~2,147,483,647

The default value is 600, indicating that the maximum wait time is 10 minutes.

Will I Be Logged Out If the Connection to an RDS for SQL Server Instance Times Out?

max degree of parallelism

Adjusts the maximum degree of parallelism for RDS for SQL Server to optimize query performance and resource utilization. Setting this parameter to a value that is too high may cause lock blocking, while setting it too low may lead to underutilized resources. You are advised to set it based on your workload and instance specifications. It is generally recommended to set the initial value to half the number of the instance's vCPUs or fine-tune it according to actual workloads.

0~32,767

2

-

Secure TLS

Whether to enable secure TLS versions and cipher suites. 0 indicates that the parameter is disabled and 1 indicates that it is enabled. Once enabled, TLSv1.0 and TLSv1.1 as well as insecure cipher suites will be disabled.

0 or 1

0

-

Lock pages in memory

Whether to enable the "Lock Pages in Memory" option. 0 indicates that the parameter is disabled and 1 indicates that it is enabled. Once enabled, the SQL Server account can keep process data in physical memory, preventing the OS from paging data to virtual memory on disk.

0 or 1

0

-

rds_databases_quota

Maximum number of databases that can be created.

10~300

100

Creating a Database

rds_databases_quota_single

Maximum number of databases that can be created. This option takes effect only for single-node instances and has a higher priority than rds_databases_quota.

10~1,000

100

Creating a Database

long_query_time

Minimum threshold (in seconds) for a query to be logged as a slow query.

1~3,600

The default value is 1, indicating that a SQL statement taking 1 second or longer to execute is defined as a slow SQL statement.

Managing Slow Query Logs
Parent Topic: Parameters