All Products
Search
Document Center

ApsaraDB RDS:Manage instance parameters

Last Updated:Aug 20, 2026

ApsaraDB RDS for SQL Server allows you to modify instance parameters in the console or by calling an API operation. You can also query the parameter modification history.

Prerequisites

Your ApsaraDB RDS for SQL Server instance must meet the following requirements:

  • Instance type: general-purpose or dedicated (shared instances are not supported)

  • Billing method: subscription or pay-as-you-go (serverless instances are not supported)

Note

For unsupported instances, you can set instance parameters by using SQL commands.

Usage notes

  • To ensure instance stability, you can modify only the parameters shown in the console.

  • Parameter changes typically take effect within 10 seconds. For the exact effective time for each parameter, refer to the parameter details table. None of the modifiable parameters in the console require an instance restart.

  • For a primary instance of the Cluster Edition with read-only instances, parameter changes are not automatically synchronized. You must configure each read-only instance separately.

  • If you modify a Trace Flag (TF) parameter and then manually restart the instance, the new value is automatically applied after the instance restarts. However, the change takes effect only after an approximate 10-minute delay.

View parameter values

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

  2. In the left navigation pane, click Parameters. You can view the configuration of each parameter in the list.

Modify parameter values

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

  2. In the left navigation pane, click Parameters.

  3. On the Modifiable Parameters tab, find the target parameter and click the image.png icon in the Running Value column.

  4. Enter the new value and click OK.

  5. Click Apply Changes. In the confirmation dialog box that appears, click OK.

    Important

    Your modifications do not take effect until you click Apply Changes.

    image

Parameter modification history

  1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

  2. In the left navigation pane, click Parameters.

  3. Click the Edit History tab, select a time range, and then click OK.

Appendix: Modifiable parameters

Note

For more information about the parameters, see the official Microsoft documentation.

Server configuration parameters

Parameter

Description

Default

Value range

Ad Hoc Distributed Queries

Enables ad hoc distributed queries.

0

[0-1]

Database Mail XPs

Enables Database Mail.

0

[0-1]

blocked process threshold (s)

Specifies the threshold, in seconds (s), at which blocked process reports are generated.

0

[0-86400]

clr enabled

Specifies whether SQL Server can run user assemblies.

0

[0-1]

clr strict security

Controls the SAFE, EXTERNAL ACCESS, and UNSAFE permissions in SQL Server.

0

[0-1]

cost threshold for parallelism

Sets the cost threshold above which SQL Server creates and runs parallel plans for queries.

5

[0-32767]

default full-text language

Specifies the default language for full-text indexes.

1033

[0-6000]

default language

Specifies the default language for all newly created logins.

0

[0-33]

filestream access level

Changes the FILESTREAM access level for this SQL Server instance.

0

[0-2]

max degree of parallelism

Sets the maximum number of processors used in a parallel plan.

2

[0-64]

remote query timeout (s)

Specifies how long in seconds (s) a remote operation can run before it times out.

600

[0-2147183647]

remote login timeout (s)

Specifies how long in seconds (s) to wait for a remote login attempt before it times out.

10

[0-2147183647]

query wait (s)

Specifies how long in seconds (s) a query waits for resources before timing out.

30

[-1-38400]

optimize for ad hoc workloads

Improves plan cache efficiency for workloads with many single-use ad hoc batches.

0

[0-1]

nested triggers

Controls whether triggers can cascade.

1

[0-1]

max worker threads

Sets the maximum number of worker threads available to SQL Server processes.

0

[128-65535]

max text repl size (B)

Specifies the maximum size, in bytes, of text, ntext, varchar(max), nvarchar(max), varbinary(max), xml, and image data that can be added to a replicated column in a single INSERT, UPDATE, WRITETEXT, or UPDATETEXT statement.

65536

[0-2147483647]

remote proc trans

Enables a Microsoft Distributed Transaction Coordinator (MS DTC) transaction to protect server-to-server procedure operations.

0

[0-1]

query governor cost limit

Sets the maximum estimated cost for running a query.

0

[0-2147483647]

recovery interval (min)

Sets the maximum time, in minutes, that SQL Server requires to recover a database.

0

[0-30]

min memory per query (KB)

Sets the minimum memory (in KB) allocated for a query's execution.

1024

[512-2147483647]

in-doubt xact resolution

Controls the default outcome for transactions that MS DTC cannot resolve.

0

[0-2]

rds_slow_log_threshold

Specifies the threshold in milliseconds (ms) for capturing slow SQL statements on an instance. SQL statements that exceed this threshold are recorded as slow query logs. Changes to this parameter take effect in approximately 5 minutes and do not require an instance restart.

Important

Set a reasonable threshold (≥1000 ms is recommended). Setting this value too low may capture an excessive number of SQL statements, which can hinder log filtering and impact instance performance. You must balance your monitoring requirements with the system load.

0

[0-60000]

rds_capture_sql_param

Controls whether to display full SQL parameter details in the Audit Log and Slow Log Details pages. Set this parameter to 1 to enable the feature (default: 0). Changes to this parameter take effect in approximately 5 minutes and do not require an instance restart.

Example: Before and after enabling

Before enabling: Only the SQL statement template is recorded. The specific parameter values passed during execution are missing.

(@n int, @keyword nvarchar(100))
SELECT
    TOP (@n) PersonID,
    FullName,
    PhoneNumber
FROM
    Application.People
WHERE
    FullName LIKE @keyword
    OR PreferredName LIKE @keyword
ORDER BY
    PersonID;

After enabling: The full SQL statement details are displayed.

exec sp_executesql N'
SELECT TOP (@n) PersonID, FullName, PhoneNumber
FROM    Application.People
WHERE   FullName LIKE @keyword OR
PreferredName LIKE @keyword
ORDER BY PersonID;',
N'@n int,@keyword nvarchar(100)',
@n = 5,
@keyword = N'%Kim%'
Important

Before enabling this parameter, ensure your environment is secure and fully assess the trade-off between troubleshooting convenience and the potential impact on your system.

  • Functional impact: Enabling this parameter changes the log format. As a result, DAS features such as SQL Explorer and Slow Log Statistics cannot aggregate similar SQL statements for statistical analysis.

  • Security risk: Recording parameter values in plaintext may expose sensitive information, such as passwords.

0

[0-1]

rds_sql_literal_masking

Controls whether to mask SQL literals in audit logs and slow query logs. Set this parameter to 1 to enable masking, or 0 (default) to disable it. When enabled, string literals in SQL statements are replaced with '***', numeric literals with *, and hexadecimal literals with 0x***. DDL statements are not affected. Changes to this parameter take effect in approximately 5 minutes and do not require an instance restart.

Example: Before and after enabling

Before enabling: Logs are displayed in plaintext.

DELETE FROM
    test_mask
WHERE
    id = 3
    AND name = N'Wang Wu'
    AND phone = '12345678910'

After enabling: SQL literals are masked.

DELETE FROM
    test_mask
WHERE
    id = *
    AND name = N'***'
    AND phone = '***'
Note
  • Masking applies only to new logs that are generated after the feature is enabled. Historical logs are not affected.

  • Enabling masking adds minor CPU overhead, which might become noticeable in high-throughput scenarios.

  • We recommend not enabling this parameter and rds_capture_sql_param simultaneously. If both are enabled, parameterized queries are recorded in the sp_executesql format, and their parameter values are not masked. This can still expose sensitive data.

0

0 or 1

Trace Flag parameters

Parameter

Description

Default

Value range

1204

Returns the resources, lock types, and command involved in a deadlock.

0

[0-1]

1211

Disables lock escalation that is based on memory pressure or the number of locks. This prevents the SQL Server Database Engine from escalating row or page locks to table locks.

0

[0-1]

1222

Returns the resources and types of locks that are involved in a deadlock and the currently affected command in an XML format that does not conform to any XSD schema.

0

[0-1]

1224

Controls lock escalation behavior. When enabled, SQL Server limits lock escalation based on the number of locks, which helps prevent widespread blocking in high-concurrency scenarios. Compared with Trace Flag 1211, which completely disables lock escalation, Trace Flag 1224 is more flexible and restricts escalation only when potential blocking is detected. It is primarily used in high-concurrency environments to avoid performance issues that are caused by unnecessary table-level locks.

0

[0-1]

2528

Disables parallel checking of objects by using DBCC CHECKDB, DBCC CHECKFILEGROUP, and DBCC CHECKTABLE.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2014.

0

[0-1]

3205

Disables hardware compression for tape drives.

0

[0-1]

3226

Suppresses backup log entries.

0

[0-1]

4199

Enables query optimizer (QO) hotfixes that are released in SQL Server cumulative updates and service packs.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2016.

0

[0-1]

4616

Makes server-level metadata visible to application roles.

0

[0-1]

6527

Disables memory dump generation on the first out-of-memory exception in CLR integration.

0

[0-1]

692

Disables fast inserts when data is bulk loaded into a heap or clustered index.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2016.

0

[0-1]

1117

When a file in a filegroup meets the autogrow threshold, all files in the filegroup grow.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2016.

0

[0-1]

1118

Forces page allocations on uniform extents instead of mixed extents to reduce contention on the SGAM page.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2016.

0

[0-1]

1262

Optimizes parallel processing for partitioned tables, especially in high-throughput scenarios. When you process large-scale partitioned tables, Trace Flag 1262 can help mitigate performance bottlenecks that are caused by imbalanced load distribution or partition-level parallel processing. This is particularly useful for queries that require parallel access to large amounts of data.

0

[0-1]

2335

Ensures that memory configured for SQL Server remains available for the data cache, query execution, and other consumers.

0

[0-1]

2371

Changes the fixed update statistics threshold to a linear update statistics threshold.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2016.

0

[0-1]

2430

Enables alternate lock class cleanup.

0

[0-1]

3604

Sends diagnostic output to the client. It is typically enabled when you use DBCC commands, such as DBCC PAGE, to view information like page structures and metadata. This helps with in-depth performance troubleshooting, such as checking for lock contention or other resource contention. This flag is often used for database performance diagnostics or data structure analysis.

0

[0-1]

6498

Manages memory usage for the compilation of incoming queries to avoid compilation waits for concurrent large queries.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2014.

0

[0-1]

8048

Converts NUMA-partitioned memory objects to CPU-partitioned memory objects.

Note

This parameter can be modified only for instances that run a version earlier than SQL Server 2014.

0

[0-1]

FAQ

Do parameter changes take effect immediately? Is a restart required?

Parameter changes typically take effect within 10 seconds. For the exact effective time for each parameter, refer to the parameter details table. A restart is not required for any parameters that can be modified in the console.

Why are my parameter changes not taking effect?

Ensure that you clicked Apply Changes after setting the parameter value. Your changes will not take effect otherwise.

Related operations