ApsaraDB RDS for SQL Server lets you modify instance parameters in the console or via the API to suit your business needs. You can also view your 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.
For unsupported instances, you can set instance parameters using SQL commands.
Usage notes
To ensure instance stability, you can only modify parameters available in the console.
Parameter modifications typically take effect within 10 seconds. For the exact effective time of each parameter, refer to the parameter details table. None of the parameters available in the console require an instance restart.
If a primary Cluster Edition instance has read-only instances, parameter changes on the primary instance are not synchronized to its read-only instances. You must configure the parameters for each read-only instance individually.
If you manually restart an instance after modifying a Trace Flag (TF) parameter, the system applies the new value after the restart. However, there is a buffer delay of approximately 10 minutes before the change takes effect.
View parameter values
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.
In the navigation pane on the left, click Parameters.
Modify parameter values
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.
In the navigation pane on the left, click Parameters.
On the Modifiable Parameters tab, click the
icon in the Running Value column of the target parameter.Enter the new value and click OK.
Click Apply Changes. In the dialog box that appears, click OK.
ImportantThe change will not take effect until you click Apply Changes.
Query parameter modification history
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.
In the navigation pane on the left, click Parameters.
Click the Edit History tab, select a time range, and then click OK.
Appendix: Modifiable parameters
For details about these parameters, see the official Microsoft documentation.
Server configuration parameters
Parameter | Description | Default | Value range |
| Enables ad hoc distributed queries. | 0 | [0-1] |
| Enables Database Mail. | 0 | [0-1] |
| Specifies the threshold, in seconds (s), at which blocked process reports are generated. | 0 | [0-86400] |
| Specifies whether SQL Server can run user assemblies. | 0 | [0-1] |
| Controls the | 0 | [0-1] |
| Sets the cost threshold above which SQL Server creates and runs parallel plans for a query. | 5 | [0-32767] |
| Specifies the default language for full-text indexes. | 1033 | [0-6000] |
| Specifies the default language for all newly created login accounts. | 0 | [0-33] |
| Changes the FILESTREAM access level for this SQL Server instance. | 0 | [0-2] |
| Sets the maximum number of processors used in a parallel plan. | 2 | [0-64] |
| Specifies how long, in seconds (s), a remote operation can run before SQL Server times out. | 600 | [0-2147183647] |
| Specifies the number of seconds to wait before returning from a failed attempt to log in to a remote server. | 10 | [0-2147183647] |
| Specifies the time that a query waits for resources before the query times out. | 30 | [-1-38400] |
| Improves plan cache efficiency for workloads with many single-use ad hoc batches. | 0 | [0-1] |
| Controls whether triggers can cascade. | 1 | [0-1] |
| Sets the maximum number of worker threads available to SQL Server processes. | 0 | [128-65535] |
| Specifies the maximum size of replication data. | 65536 | [0-2147483647] |
| Protects server-to-server procedures by using a Microsoft Distributed Transaction Coordinator (MS DTC) transaction. | 0 | [0-1] |
| Sets an upper limit on the estimated cost for a query to run. | 0 | [0-2147483647] |
| Defines an upper limit on the time, in minutes, that is required to recover a database. | 0 | [0-30] |
| Specifies the minimum amount of memory (in KB) allocated for a query's execution. | 1024 | [512-2147483647] |
| Controls the default outcome for transactions that MS DTC cannot resolve. | 0 | [0-2] |
| Specifies the threshold in milliseconds (ms) for capturing slow SQL statements on an instance. SQL statements whose execution duration exceeds the threshold are recorded in slow query logs. This change takes effect in approximately 5 minutes. No instance restart is required. Important Set a reasonable threshold (recommended: 1,000 ms or greater). A low threshold may capture a large volume of SQL statements, which hinders log filtering and affects instance performance. Balance your monitoring needs with the impact on system load. | 0 | [0-60000] |
| Controls whether to display full SQL parameter details in the audit log and Slow Log Details pages. Set to 1 to enable (disabled by default). This change takes effect in approximately 5 minutes. No instance restart is required. Important Before you enable this feature, make sure that your environment is secure. Fully evaluate the trade-off between troubleshooting benefits and potential system impact.
| 0 | [0-1] |
| 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 Note
| 0 | 0 or 1 |
Trace Flag parameters
Parameter | Description | Default | Value range |
1204 | Returns the resources and types of locks that are participating in a deadlock and the currently affected command. | 0 | [0-1] |
1211 | Disables lock escalation that is based on memory pressure or the number of locks. The SQL Server Database Engine does not escalate row or page locks to table locks. | 0 | [0-1] |
1222 | Returns the resources and types of locks that are participating 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 to help avoid widespread blocking in high-concurrency scenarios. Compared with Trace Flag 1211, which disables lock escalation entirely, 1224 is more flexible and limits escalation only when potential blocking is detected. It is commonly used in high-concurrency environments to avoid performance issues caused by unnecessary table-level locks. | 0 | [0-1] |
2528 | Disables parallel checking of objects by Note This parameter can be modified only for versions 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 versions 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 you bulk load data into a heap or clustered index. Note This parameter can be modified only for versions 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 versions 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 versions 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, this parameter can help mitigate performance bottlenecks that are caused by uneven 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 that is configured for SQL Server is still used by data caches, query execution, and other consumers. | 0 | [0-1] |
2371 | Changes the fixed update statistics threshold to a dynamic update statistics threshold. Note This parameter can be modified only for versions earlier than SQL Server 2016. | 0 | [0-1] |
2430 | Enables alternate lock class cleanup. | 0 | [0-1] |
3604 | This flag is typically used with DBCC commands (e.g., DBCC PAGE) to view internal structures and metadata. It helps troubleshoot in-depth performance issues like lock or resource contention and is often used for performance diagnostics or data structure analysis. | 0 | [0-1] |
6498 | Manages the memory usage for compiling incoming queries to avoid compilation waits for concurrent large queries. Note This parameter can be modified only for versions 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 versions earlier than SQL Server 2014. | 0 | [0-1] |
FAQ
Related operations
To query the current parameter configuration of an instance using the API, see DescribeParameters.
To modify the parameters of an ApsaraDB RDS for SQL Server instance using the API, see ModifyParameter.
To set instance parameters by using SQL commands, see Set instance parameters by using SQL commands.