From 88b6007443a8e430c32b5e29d5ecc604d46e9d27 Mon Sep 17 00:00:00 2001 From: wangdengke2 Date: Thu, 2 Apr 2026 09:58:19 +0000 Subject: [PATCH] rds_umn Reviewed-by: Wagner, Fabian Co-authored-by: wangdengke2 Co-committed-by: wangdengke2 --- docs/rds/umn/ALL_META.TXT.json | 82 +++++++-------- docs/rds/umn/CLASS.TXT.json | 48 ++++----- docs/rds/umn/en-us_image_0000002378668778.png | Bin 13147 -> 0 bytes docs/rds/umn/en-us_image_0000002390290289.png | Bin 609 -> 0 bytes docs/rds/umn/en-us_image_0000002526234126.png | Bin 0 -> 179 bytes docs/rds/umn/en-us_image_0000002534464226.png | Bin 0 -> 579 bytes docs/rds/umn/en-us_image_0000002557433943.png | Bin 0 -> 252 bytes .../rds/umn/en-us_topic_add_read_replica.html | 14 ++- .../rds/umn/en-us_topic_connect_instance.html | 2 +- docs/rds/umn/en-us_topic_scale_cluster.html | 12 +-- docs/rds/umn/en-us_topic_scale_rds.html | 4 +- .../en-us_topic_sqlserver_reset_password.html | 2 +- docs/rds/umn/rds_01_0020.html | 54 ++++++---- docs/rds/umn/rds_01_0021.html | 4 +- docs/rds/umn/rds_01_0089.html | 13 --- docs/rds/umn/rds_02_0008.html | 20 +++- docs/rds/umn/rds_02_0016.html | 10 +- docs/rds/umn/rds_02_0047.html | 8 +- docs/rds/umn/rds_02_0051.html | 10 +- docs/rds/umn/rds_03_0007.html | 6 +- docs/rds/umn/rds_03_0011.html | 14 ++- docs/rds/umn/rds_03_0013.html | 6 +- docs/rds/umn/rds_03_0065.html | 18 +++- docs/rds/umn/rds_03_0100.html | 22 +++- docs/rds/umn/rds_04_0061.html | 16 ++- docs/rds/umn/rds_05_0001.html | 2 +- docs/rds/umn/rds_05_0003.html | 2 +- docs/rds/umn/rds_05_0024.html | 2 +- docs/rds/umn/rds_05_0038.html | 2 +- docs/rds/umn/rds_05_0039.html | 4 +- docs/rds/umn/rds_05_0060.html | 4 +- docs/rds/umn/rds_05_0085.html | 2 +- docs/rds/umn/rds_05_0140.html | 55 ++++++++-- docs/rds/umn/rds_08_0003.html | 2 +- docs/rds/umn/rds_08_0004.html | 12 ++- docs/rds/umn/rds_08_0013.html | 2 +- docs/rds/umn/rds_08_0025.html | 8 +- docs/rds/umn/rds_08_0026.html | 2 +- docs/rds/umn/rds_08_0027.html | 2 +- docs/rds/umn/rds_08_0028.html | 6 +- docs/rds/umn/rds_08_0029.html | 2 +- docs/rds/umn/rds_08_0030.html | 8 +- docs/rds/umn/rds_08_0031.html | 5 +- docs/rds/umn/rds_08_0032.html | 2 +- docs/rds/umn/rds_08_0033.html | 94 ++++++++++++++---- docs/rds/umn/rds_08_0035.html | 21 ++-- docs/rds/umn/rds_08_0037.html | 16 +-- docs/rds/umn/rds_08_0039.html | 3 +- docs/rds/umn/rds_09_0024.html | 2 +- docs/rds/umn/rds_09_0026.html | 2 +- docs/rds/umn/rds_09_0065.html | 38 +++---- docs/rds/umn/rds_11_0006.html | 2 +- docs/rds/umn/rds_11_0015.html | 2 +- docs/rds/umn/rds_11_0017.html | 4 +- docs/rds/umn/rds_11_0019.html | 2 +- docs/rds/umn/rds_11_0026.html | 2 +- docs/rds/umn/rds_11_0032.html | 2 +- docs/rds/umn/rds_11_0047.html | 2 +- docs/rds/umn/rds_add_read_replica_pg.html | 14 ++- docs/rds/umn/rds_change_database_port.html | 4 +- docs/rds/umn/rds_faq_0036.html | 2 +- docs/rds/umn/rds_faq_0050.html | 10 +- docs/rds/umn/rds_faq_0051.html | 2 +- docs/rds/umn/rds_faq_0065.html | 2 +- docs/rds/umn/rds_faq_0076.html | 7 +- docs/rds/umn/rds_faq_0100.html | 2 +- docs/rds/umn/rds_faq_0119.html | 2 +- docs/rds/umn/rds_faq_0144.html | 2 +- docs/rds/umn/rds_history_0008.html | 14 ++- docs/rds/umn/rds_modify_availability.html | 2 +- docs/rds/umn/rds_modify_instance_name.html | 4 +- docs/rds/umn/rds_mysql_0001.html | 8 +- docs/rds/umn/rds_pg_05_0001.html | 2 +- docs/rds/umn/rds_pg_05_0003.html | 2 +- docs/rds/umn/rds_pg_05_0004.html | 2 +- docs/rds/umn/rds_pg_05_0024.html | 2 +- docs/rds/umn/rds_pg_05_0026.html | 2 +- docs/rds/umn/rds_pg_05_0038.html | 2 +- docs/rds/umn/rds_pg_05_0039.html | 2 +- docs/rds/umn/rds_pg_05_0060.html | 2 +- docs/rds/umn/rds_pg_05_0084.html | 69 ++++++++++++- docs/rds/umn/rds_pg_08_0025.html | 6 +- docs/rds/umn/rds_pg_08_0026.html | 10 +- docs/rds/umn/rds_pg_08_0027.html | 2 +- docs/rds/umn/rds_pg_08_0030.html | 4 +- docs/rds/umn/rds_pg_08_0032.html | 2 +- docs/rds/umn/rds_pg_08_0033.html | 4 +- docs/rds/umn/rds_pg_08_0037.html | 14 +-- docs/rds/umn/rds_pg_08_0039.html | 20 ---- docs/rds/umn/rds_pg_08_0057.html | 16 +++ docs/rds/umn/rds_pg_10_0005.html | 4 +- docs/rds/umn/rds_pg_11_0004.html | 2 +- docs/rds/umn/rds_pg_11_0005.html | 2 +- docs/rds/umn/rds_pg_change_database_port.html | 4 +- docs/rds/umn/rds_pg_modify_availability.html | 2 +- docs/rds/umn/rds_pg_modify_instance_name.html | 4 +- docs/rds/umn/rds_pg_reset_password.html | 2 +- docs/rds/umn/rds_pg_scale_cluster.html | 12 +-- docs/rds/umn/rds_pg_scale_rds.html | 4 +- docs/rds/umn/rds_pg_switch_ha.html | 2 +- docs/rds/umn/rds_reset_password.html | 2 +- docs/rds/umn/rds_sqlserver_0024.html | 4 +- docs/rds/umn/rds_sqlserver_05_0008.html | 2 +- docs/rds/umn/rds_sqlserver_05_0024.html | 2 +- docs/rds/umn/rds_sqlserver_05_0038.html | 2 +- docs/rds/umn/rds_sqlserver_05_0050.html | 25 +++-- docs/rds/umn/rds_sqlserver_05_0117.html | 6 +- docs/rds/umn/rds_sqlserver_11_0004.html | 2 +- .../rds_sqlserver_change_database_port.html | 4 +- docs/rds/umn/rds_sqlserver_dba_02.html | 2 +- .../rds_sqlserver_modify_availability.html | 2 +- .../rds_sqlserver_modify_instance_name.html | 4 +- docs/rds/umn/rds_sqlserver_scale_cluster.html | 8 +- docs/rds/umn/rds_sqlserver_scale_rds.html | 4 +- docs/rds/umn/rds_sqlserver_switch_ha.html | 2 +- docs/rds/umn/rds_switch_ha.html | 2 +- 116 files changed, 647 insertions(+), 383 deletions(-) delete mode 100644 docs/rds/umn/en-us_image_0000002378668778.png delete mode 100644 docs/rds/umn/en-us_image_0000002390290289.png create mode 100644 docs/rds/umn/en-us_image_0000002526234126.png create mode 100644 docs/rds/umn/en-us_image_0000002534464226.png create mode 100644 docs/rds/umn/en-us_image_0000002557433943.png delete mode 100644 docs/rds/umn/rds_pg_08_0039.html create mode 100644 docs/rds/umn/rds_pg_08_0057.html diff --git a/docs/rds/umn/ALL_META.TXT.json b/docs/rds/umn/ALL_META.TXT.json index 263b43228..fe40589b7 100644 --- a/docs/rds/umn/ALL_META.TXT.json +++ b/docs/rds/umn/ALL_META.TXT.json @@ -1864,7 +1864,7 @@ "node_id":"rds_08_0025.xml", "product_code":"rds", "code":"92", - "des":"On the Overview page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance met", + "des":"On the Summary page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance metr", "doc_type":"usermanual", "kw":"Introduction to Instance Overview,Instance Modifications,User Guide", "search_title":"", @@ -1900,7 +1900,7 @@ "node_id":"rds_modify_instance_name.xml", "product_code":"rds", "code":"94", - "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", "search_title":"", @@ -1956,7 +1956,7 @@ "code":"97", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", - "kw":"scale up storage space,scale up storage space,MySQL,Scaling up Storage Space,Instance Modifications,", + "kw":"scale up storage space,MySQL,Scaling Up Storage Space,Instance Modifications,User Guide", "search_title":"", "metedata":[ { @@ -1964,7 +1964,7 @@ "documenttype":"usermanual" } ], - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "githuburl":"" }, { @@ -1990,7 +1990,7 @@ "node_id":"rds_05_0140.xml", "product_code":"rds", "code":"99", - "des":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.Alternatively, click the instance name to go to the Overview page. ", + "des":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.Alte", "doc_type":"usermanual", "kw":"Changing a Storage Type,Instance Modifications,User Guide", "search_title":"", @@ -2062,7 +2062,7 @@ "node_id":"rds_05_0060.xml", "product_code":"rds", "code":"103", - "des":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.Primary/standby instances running MySQL 5.7, or 8.0 support standby instance mig", + "des":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.Primary/standby instances running MySQL 5.7 or 8.0 support standby instance migr", "doc_type":"usermanual", "kw":"Migrating a Standby DB Instance,Instance Modifications,User Guide", "search_title":"", @@ -2260,7 +2260,7 @@ "node_id":"rds_03_0100.xml", "product_code":"rds", "code":"114", - "des":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.You can also select the binlog backups ", + "des":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary. For details, see Downloading a Binlog ", "doc_type":"usermanual", "kw":"binlog backup files,Downloading a Binlog Backup File,Backups and Restorations,User Guide", "search_title":"", @@ -3232,7 +3232,7 @@ "node_id":"rds_08_0033.xml", "product_code":"rds", "code":"168", - "des":"You can create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better performance at high c", + "des":"SQL throttling allows you to create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better ", "doc_type":"usermanual", "kw":"Creating a SQL Throttling Rule,SQL Analysis,User Guide", "search_title":"", @@ -3952,7 +3952,7 @@ "node_id":"rds_pg_08_0025.xml", "product_code":"rds", "code":"208", - "des":"On the Overview page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performanc", + "des":"On the Summary page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performance", "doc_type":"usermanual", "kw":"Introduction to Instance Overview,Instance Modifications,User Guide", "search_title":"", @@ -3988,7 +3988,7 @@ "node_id":"rds_pg_modify_instance_name.xml", "product_code":"rds", "code":"210", - "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", "search_title":"", @@ -4044,7 +4044,7 @@ "code":"213", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", - "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", + "kw":"scale up storage space,Scaling Up Storage Space,Instance Modifications,User Guide", "search_title":"", "metedata":[ { @@ -4052,7 +4052,7 @@ "documenttype":"usermanual" } ], - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "githuburl":"" }, { @@ -4060,7 +4060,7 @@ "node_id":"rds_pg_05_0084.xml", "product_code":"rds", "code":"214", - "des":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.If the storage type of a read replica is different from that of its", + "des":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.If t", "doc_type":"usermanual", "kw":"Changing a Storage Type,Instance Modifications,User Guide", "search_title":"", @@ -4991,29 +4991,11 @@ "title":"Problem Diagnosis", "githuburl":"" }, - { - "uri":"rds_pg_08_0039.html", - "node_id":"rds_pg_08_0039.xml", - "product_code":"rds", - "code":"266", - "des":"You can kill sessions when necessary on the Sessions that Can Be Killed If Necessary tab page. This page covers:Emergency Channel: If the maximum number of connections fo", - "doc_type":"usermanual", - "kw":"Killing Sessions,Problem Diagnosis,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"rds", - "documenttype":"usermanual" - } - ], - "title":"Killing Sessions", - "githuburl":"" - }, { "uri":"rds_pg_08_0026.html", "node_id":"rds_pg_08_0026.xml", "product_code":"rds", - "code":"267", + "code":"266", "des":"You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, a", "doc_type":"usermanual", "kw":"Managing Real-Time Sessions,Problem Diagnosis,User Guide", @@ -5027,6 +5009,24 @@ "title":"Managing Real-Time Sessions", "githuburl":"" }, + { + "uri":"rds_pg_08_0057.html", + "node_id":"rds_pg_08_0057.xml", + "product_code":"rds", + "code":"267", + "des":"You can query historical sessions, historical wait events, and historical top SQL statements of your DB instance.In the session statistics area, you can filter sessions b", + "doc_type":"usermanual", + "kw":"Managing Historical Sessions,Problem Diagnosis,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"rds", + "documenttype":"usermanual" + } + ], + "title":"Managing Historical Sessions", + "githuburl":"" + }, { "uri":"rds_pg_10_0006.html", "node_id":"rds_pg_10_0006.xml", @@ -5752,7 +5752,7 @@ "node_id":"rds_sqlserver_05_0117.xml", "product_code":"rds", "code":"308", - "des":"On the Overview page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performanc", + "des":"On the Summary page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performance", "doc_type":"usermanual", "kw":"Introduction to Instance Overview,Instance Modifications,User Guide", "search_title":"", @@ -5770,7 +5770,7 @@ "node_id":"rds_sqlserver_modify_instance_name.xml", "product_code":"rds", "code":"309", - "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", "search_title":"", @@ -5824,7 +5824,7 @@ "node_id":"rds_sqlserver_05_0050.xml", "product_code":"rds", "code":"312", - "des":"If the storage type of your DB instance does not match your workloads, you can change it as needed.If the storage type of a read replica is different from that of its ass", + "des":"If the storage type of your DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.If the s", "doc_type":"usermanual", "kw":"Changing a Storage Type,Instance Modifications,User Guide", "search_title":"", @@ -5844,7 +5844,7 @@ "code":"313", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "doc_type":"usermanual", - "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", + "kw":"scale up storage space,Scaling Up Storage Space,Instance Modifications,User Guide", "search_title":"", "metedata":[ { @@ -5852,7 +5852,7 @@ "documenttype":"usermanual" } ], - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "githuburl":"" }, { @@ -7930,9 +7930,9 @@ "node_id":"rds_faq_0076.xml", "product_code":"rds", "code":"421", - "des":"No. After an RDS DB instance is created, the storage type cannot be changed.", + "des":"Yes. After an RDS DB instance is created, you can change its storage type.For RDS for MySQL instances, see Changing a Storage Type.For RDS for PostgreSQL instances, see C", "doc_type":"usermanual", - "kw":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?,Database Stor", + "kw":"Can I Change the Storage Type of an RDS DB Instance?,Database Storage,User Guide", "search_title":"", "metedata":[ { @@ -7943,7 +7943,7 @@ "documenttype":"usermanual" } ], - "title":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?", + "title":"Can I Change the Storage Type of an RDS DB Instance?", "githuburl":"" }, { @@ -8371,7 +8371,7 @@ "node_id":"rds_faq_0119.xml", "product_code":"rds", "code":"442", - "des":"PostgreSQL 12 supports test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_decoding, set wal_level to logical.", + "des":"For more information about test_decoding, see test_decoding introduction.To use test_decoding, set wal_level to logical.", "doc_type":"usermanual", "kw":"Does RDS for PostgreSQL Support the test_decoding Plugin?,Database Parameter Modification,User Guide", "search_title":"", diff --git a/docs/rds/umn/CLASS.TXT.json b/docs/rds/umn/CLASS.TXT.json index ff0f30901..01bb8c5a6 100644 --- a/docs/rds/umn/CLASS.TXT.json +++ b/docs/rds/umn/CLASS.TXT.json @@ -819,7 +819,7 @@ "code":"91" }, { - "desc":"On the Overview page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance met", + "desc":"On the Summary page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance metr", "product_code":"rds", "title":"Introduction to Instance Overview", "uri":"rds_08_0025.html", @@ -837,7 +837,7 @@ "code":"93" }, { - "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "product_code":"rds", "title":"Changing a DB Instance Name", "uri":"rds_modify_instance_name.html", @@ -866,7 +866,7 @@ { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "uri":"en-us_topic_scale_cluster.html", "doc_type":"usermanual", "p_code":"91", @@ -882,7 +882,7 @@ "code":"98" }, { - "desc":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.Alternatively, click the instance name to go to the Overview page. ", + "desc":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.Alte", "product_code":"rds", "title":"Changing a Storage Type", "uri":"rds_05_0140.html", @@ -918,7 +918,7 @@ "code":"102" }, { - "desc":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.Primary/standby instances running MySQL 5.7, or 8.0 support standby instance mig", + "desc":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.Primary/standby instances running MySQL 5.7 or 8.0 support standby instance migr", "product_code":"rds", "title":"Migrating a Standby DB Instance", "uri":"rds_05_0060.html", @@ -1017,7 +1017,7 @@ "code":"113" }, { - "desc":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.You can also select the binlog backups ", + "desc":"RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary. For details, see Downloading a Binlog ", "product_code":"rds", "title":"Downloading a Binlog Backup File", "uri":"rds_03_0100.html", @@ -1503,7 +1503,7 @@ "code":"167" }, { - "desc":"You can create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better performance at high c", + "desc":"SQL throttling allows you to create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better ", "product_code":"rds", "title":"Creating a SQL Throttling Rule", "uri":"rds_08_0033.html", @@ -1863,7 +1863,7 @@ "code":"207" }, { - "desc":"On the Overview page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performanc", + "desc":"On the Summary page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performance", "product_code":"rds", "title":"Introduction to Instance Overview", "uri":"rds_pg_08_0025.html", @@ -1881,7 +1881,7 @@ "code":"209" }, { - "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "product_code":"rds", "title":"Changing a DB Instance Name", "uri":"rds_pg_modify_instance_name.html", @@ -1910,14 +1910,14 @@ { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "uri":"rds_pg_scale_cluster.html", "doc_type":"usermanual", "p_code":"207", "code":"213" }, { - "desc":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.If the storage type of a read replica is different from that of its", + "desc":"If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.If t", "product_code":"rds", "title":"Changing a Storage Type", "uri":"rds_pg_05_0084.html", @@ -2385,19 +2385,19 @@ "code":"265" }, { - "desc":"You can kill sessions when necessary on the Sessions that Can Be Killed If Necessary tab page. This page covers:Emergency Channel: If the maximum number of connections fo", + "desc":"You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, a", "product_code":"rds", - "title":"Killing Sessions", - "uri":"rds_pg_08_0039.html", + "title":"Managing Real-Time Sessions", + "uri":"rds_pg_08_0026.html", "doc_type":"usermanual", "p_code":"265", "code":"266" }, { - "desc":"You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, a", + "desc":"You can query historical sessions, historical wait events, and historical top SQL statements of your DB instance.In the session statistics area, you can filter sessions b", "product_code":"rds", - "title":"Managing Real-Time Sessions", - "uri":"rds_pg_08_0026.html", + "title":"Managing Historical Sessions", + "uri":"rds_pg_08_0057.html", "doc_type":"usermanual", "p_code":"265", "code":"267" @@ -2763,7 +2763,7 @@ "code":"307" }, { - "desc":"On the Overview page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performanc", + "desc":"On the Summary page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performance", "product_code":"rds", "title":"Introduction to Instance Overview", "uri":"rds_sqlserver_05_0117.html", @@ -2772,7 +2772,7 @@ "code":"308" }, { - "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to", + "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to ", "product_code":"rds", "title":"Changing a DB Instance Name", "uri":"rds_sqlserver_modify_instance_name.html", @@ -2799,7 +2799,7 @@ "code":"311" }, { - "desc":"If the storage type of your DB instance does not match your workloads, you can change it as needed.If the storage type of a read replica is different from that of its ass", + "desc":"If the storage type of your DB instance does not match your workloads, you can change it as needed.For details about storage types, see DB Instance Storage Types.If the s", "product_code":"rds", "title":"Changing a Storage Type", "uri":"rds_sqlserver_05_0050.html", @@ -2810,7 +2810,7 @@ { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.You are advised to set alarm rules for the storage space u", "product_code":"rds", - "title":"Scaling up Storage Space", + "title":"Scaling Up Storage Space", "uri":"rds_sqlserver_scale_cluster.html", "doc_type":"usermanual", "p_code":"307", @@ -3780,9 +3780,9 @@ "code":"420" }, { - "desc":"No. After an RDS DB instance is created, the storage type cannot be changed.", + "desc":"Yes. After an RDS DB instance is created, you can change its storage type.For RDS for MySQL instances, see Changing a Storage Type.For RDS for PostgreSQL instances, see C", "product_code":"rds", - "title":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?", + "title":"Can I Change the Storage Type of an RDS DB Instance?", "uri":"rds_faq_0076.html", "doc_type":"usermanual", "p_code":"418", @@ -3969,7 +3969,7 @@ "code":"441" }, { - "desc":"PostgreSQL 12 supports test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_decoding, set wal_level to logical.", + "desc":"For more information about test_decoding, see test_decoding introduction.To use test_decoding, set wal_level to logical.", "product_code":"rds", "title":"Does RDS for PostgreSQL Support the test_decoding Plugin?", "uri":"rds_faq_0119.html", diff --git a/docs/rds/umn/en-us_image_0000002378668778.png b/docs/rds/umn/en-us_image_0000002378668778.png deleted file mode 100644 index 9c717d58679704f18c61163ee96f254f6207c5a6..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 13147 zcmeHuXH-+`yC)!sf`Uf`qzOvzYUnK}0s;mEq*qZ0Eg)4&01*Z0Ae~4PLa&CHa+p0)n&F z_59yWiLij5$^}KTza1hywKb3j(5ZEdTszAodMCzaSp^ zr!xW~)){~u5%DEi0>Xd(aFAU}0cA}8>;J#seS@kX{r5w@aGH^+Ddr1jnX!Y&2Gg6C z0BjQ&63ylJ?{_mM;Lop81Sk$2VIdW89_%Q#mgFkkzxZb)_YIdh_^KQ7M2qwev@92( zSpU~QnKcCwzd?n$z7Ir&4W$hI>p0ce6eRP_=H}Iv_4Q$@uX;0p7_r29{NrRqO$XE;3>ICJfmZnQ1zg)Wc&ebO zD1mH9i>xdTCBW)2u($sc0XOBpOg9Dy*6o?8Un#2H8LRc&&5WL(rXgC6q60B44iNE+ zaXY&C24Y9McPwxcy;J=hb4NR2-oqcKJi+CTao((y%EdV}SIk7#eD)w^(9 zE$)1PKK;C^y;EMj0rz@6ze(QURxW5y#X9`C2Mk79pIesOoRnY9yCIuskE^m_@Dzv| zk)jojQ{i3P=VBMwa*kE@u}?yRAt32sF_$#35hT;#9+;x1C8pL#qOw~3z^NeK^>`dO zhUVItycViZUsLAb=;5AIl$nP1Ip{600(E_>C><%Z2MB$F|G>ShiZ4p$=s?uR;Q$c} z2MfBIFT;SN2gi?>_UF1xY->E=T`>!&6v3dGqy0??nHo3i^6NJ8IoI$tTYG;O-~0^= z<0O!wO4U|sRYPyUgzSu2S!s4)aL*F5cY!4#G9SIwffPGi!1sib@yn~XB5F;9JdEF! zNNNQc7^UY|wR9E)*&rno&^;@u`mS{KMd2u(u<0;0Q4>tsXv>vkwr-vGzVhY*q!f}C z4AyZv9Zd7adY`%y5pUbe)Ay907BNwoY?KBZ@T5*L@2tO*U@G%xtteb8w3LjfvZ-c% zSvr$^8*?^O)vj`{rrrrVS_4}u#g&98y)W6x>Hj!`aEzxWLKYo==%3zeZ}FdJp1b

iNP(6wYCLz>MiF4(;R@pUr2E1sIK}H|58L#qtL<*JqLb;Z zl7t<~0RhoZ9{sMiuLdo<7oFuF>hmfk6ckWl*jED!`fd!noFsq{4*|`PU-2rpOfO&H`aJyFf?u`&>Lu%csT5{troL^%wZR|Qgehz zAFcB2lGqlP#B4=4-}c)71SgZkSwO|sLYya!ZcDW#g%%PD>EGD8 z1712?3dCW<<<*6ba82Xo_P~>)O?h?bMjI!spfO+2Op(v=^1YOAejaX~+PdkG7yQQd_@r)e@bv;pbiZb=jGSdYQ&bc4 z;HBRN17O=OFYMv^#5R| z94boaa7|2#Y6YGvgr);T50BgC7bT@+pT^TIiw^M2N%_pkG14v`i){I3G#7nwnWuCi z`oe7kr7o&uSekAd&jZj~O2MZhh#T*g&hM7hZQYlfR*KGQm|D z5D(G}-q`>Jo--y5h1#m`&5XG zJZe(am~UmQ2*)_#sc*zb%6{N$k_77N?w|g+Gk^o49ttqU`o7iqbp96 z_d+`|pLG!T0Oz@MKZ_>b@Oc;O%ZTCGk{1P}jUehcZ}+>K9|p8&Rm0F%1r$3hJw%tJ zO-23IN272hH%wJosgDWc{(DbQk=A zQe`oy-epjy4}8cv`4#{iu?&8XKNnpYU-B&soVdX&Feqmo!Hi_? z=y!YoVA4~wGQAEg*%gSUDXa44KEAo$vFtIWP3IcnnTy#>=mRdPaAJ5Bh;tq;RSwZi zDwOHObv190c7!}7iLBE|r{h_VL72aZfWxzQI4RlFFjVeHgS0Y6PHhd9rQC#PV&7v` zb_K3f@jiP^45LotC1kEP*FwL}`v^c;#PI9Kbq4v@C7-DPACh?}1c((UwM*teRA9y`b zS6GAJMR$BKN~G2ChRba=C$55Xx9rGkxs5P+@77DU*r4#ZG9}Td$pex1ZD@L*P_DSp z@>dM&#EeOG6VADc9X7tt#?HQNVfA5BhicavI07M)o1m{`b!{XM?gj@z~Uo66APg}J@_tqx+1nIU!PPPos}Y!>j?3STMLY_t#N>6Dk3r+6&o z(ic%j`|7(?-g~`zL;eTZh4(Zr;qpdjw zS$(m_+QDq8X;c%f7kxi~N`gUAT}48qxPTf*t>6-}RfVUKLm1xf zy0(!!?%ET)sXH0^eLbbJ*=ZCvchEA*sS_IIQ(A97=vLa{$UNKGMm~g7!WdK9U^g(m zCdLR9h#!EjA33HM8ee{vR|*&k7DHx|GCP7c*y-&r*nS-fFyOQw=s)h?F=0i-Y0(J{RgUeF+^Kls+_aB0k`;G@5`GWE84 zj>#@Is-amevEoDY8@yrZC#C+wd!%g&xocQQyQBIz++ zp?$9Q}6U0k1fKlb0t_0vA-%+mbo`P!5O`ocS+DO1fWugy9+1@*P2dl&wH7#=Hq9I!> zww0My9*YkiZM2fl*CqfcsZD(M-jx!~j1n~D3YtNnWb)pjrrOn-Av1toM5*CrZ?j<= z;o_c@xlOgPjYcR=bfffUT-4+1MHskfS$nbHL~8{>XWo-#*@GNo+RqRvM+ z9@lpb3qCRcE0jr{M@P{>cJ&OKKc|`zU+;)$PbOH_(tW3&80jB7Ar*Wr;CkyunJ&UF zRYzI1#t7qfil6L9BS!@V&4#zC2|t0f(Dsq*2~efCN}Nx>{56ym=YLnrL$rn3q(U@9 zSL|7bRt{Un#i7QB1)Z7FSL|vI7&vwdmecX&92<+k2v30pgy6bW-`ZFK_c6IByslO} zq+hV|_}s=SFL)N9EXW6>Y?Oj$IaeqnV9#PIZG6mFOYZV68WeVb8fWVqpED+3<`(-r zsO-BZg(Xz1OcICEN_^3{us!fo>&x#j!y(7$8|GKNVidq~bKlz(IM>9tY)^gzqCYiXg&sM=v!r)0o|| zAx9^WS+c>C6srKaHYwo)!w$`a6fqB_)!J3H_L3vu!Y5sfh`=sc_FzjUQhZTEqMHN? zoj>c!P*t=(3o#zJ{ugfiPg)#vL!i(*B>KvbXLXh^->rt_P(Y<*-4tA3p; zqW0d$U6iX%J$HL{qC)MHfyWkI_LI)_?3!iqO0Q8~ZU=+bP!W7CIOPktdGZ z=(0LL))+upznQdNvo{m0*?UdO?HhXCdv|NGAHyU_$d()t)l&-MA;{ z?rrvAYtu-Z`@zAW(G4>j=6x$EZ#XqbV0{KL5`??CUX?63%)H+3x3LL5a!le5S2;AD zb=>xE^n0q%%T^YDm?Jm2l(JgM$ay>uGU&Cr6}q3XeSv{SCRskb@fopZUEc>$%$X9_ zs{8pAwkwA@tV#N&`R$ohc0+d+p8(Cpu)N{&=E}Pd3MEW5E*HOQ)iskQG+Z~Xrkj{i z4`MGBN?W5v%+r+wc1R~|szab0kXUZOyLaV_C^dhmP3B7D8pAY~v_4&A_r1jTLh25n zkuv-ps%95%QFi@mFp?!GgsSB zTq=F;(Q!ZRRTwRAbY5?+SL0gDOj8%r`XOGPDh777cEtRKA6|E1gVf zo}+EmZMVL4e+^u>kJooHMb3%Ui~fL>bzR_2)#1$n4q?%kk51yEBpF+7OtlnI9ZS>Q zjpv)XSl$IX;pZ|m)%AI2zAu=30vy#hX*c^xfJ$Z?m(5>ghoiEpn#o)o}<{ zY#i`P@>ciFjfZZHpWl#$1{82I{+tG?aIxId9)ZOka_q;Ek8PY$backfG;`Oh0i2hS z!^R9#S!E*>9h93-$lID-(~NA;77D9lQi&Sh3y*h)Ue3EAeAoGv;y1ZCb%3{IV9++A zYom)PF(y=!n{jp5o#%sis4ZWah}TX`8Gl7BI;AVOeRgE%ktC+!fB3*-Vg9k?Tc@hV zp$3xxP1lNQ`^A?iOr=sFDi$p8we9lx=t=)kqxv_fDntgy&kDqwsQ!4>-m}&iUt!?t zYmL|aC}rYJs#}ZZx7$L#6P*=3R1tnZOP|6|eLLySk51_CvAeFIFMgsslY}4JEyCk) zCVL+Hn7ApgU9>^DT|wNZ&UB^=XB(%V&0ELTzMOt0cJ)G{rxJ8%1+cCdh??hraQwpv zKZnoHuKFGyAAdCc*6VOWf8p%m;bE6-6Szxe(>r?4cJk9e_|Ka^7YvL}3r{v-z`j*iZaG!|**@tfpM>AIK0A z56wOKLUVHKxu%bm+&i`z#F>fwEAqc<q5mMV^B^9uK73P1Vp5lSY#v# zXypH~XZUWzArO86fVOytz46Pdez46b`(kf}Ko>8h?-Rk|Y6nNi3FBd#`HSCP(lC9> z*FuZdIhJQqBts&S<7hE=DR8v<@0%b1`9Kr6`p@g3;6jZ?u0flAk7< zx3|)QTR8d$0{>Q?=|vL#X0WI|dYamSosyu!qn4xZ z(MyH8KSE57a0V~~_ybKs;=gxhdW|<@uCxBZsE_dGdV~7+-V85#JXg;h=+59b0iQn} zi>VTokwP-}_<|<(t*@Ry-4}Rqze@X41I1NDvChq3Y}|Gyr)L2j-F80i3qz}d_GsJ& zKC%2aMsOi9>vTEnkbGW8-?C?uxwq1-(>QK2X{AYG{zqw%viv9{>{l2Pd>%cqwoa}WQRjN*r)Akyd}m))X)9_ zcBa&L0BAc5eFgkMoQ9WpBhnCq0Dtn9JT6&iSr9@YBaYh?1PH-g}p)sLfdMG3>xAveSFZ%2EW+({TeGZ%S-|@ zuxt|nw;-nB#*?}a8T&aI{4QIp>WepEZ_SshN47b1zVdjT@N2-zeiPdlPK75k6>TaB zG_Y1Mjl^>vJdnx%o7zkliQl-*i?WY&qhb^P(#;^ij^038k^hDfT?xV)$@`%5{}VgS zwfpV_1XMJq-va#aSxfc&PwM^4q=4kC-$xv-uInD8$$9+FJFVO-lTT5_7y4EyUnD1A3Fb7T;bOgI!N{PnQy6wAJ8^jIx*ZWU&f?C)v<@= zA@4jST;%3^7r~yJ;rLoa3?Zd|$cUv@<^MunF1}WLcLpKyCHhx)^2Jb}QmXM=sRCc? zQj{7B6Ex)%x4e{1y;&wxH@#;`LO&n5mrnk`*@6i$qAX$sNlxtopln@$gTD06Nlt2_sfwXiQAXwh*+!|$DZ;az8h-3TBoc-!p$h5v z#VicBe6QX@rEyx;_0RxTo78CJnO5%p)n-|L%Ti{hxO|Pqt!R*jlM!e%3SuQ2aNRaSdyd+@z-$#UVA4_x6EuzC+)EwDgqgdJ}N))j?Tlc zrgqm(#(nc3{mz;RfMLaQ+~JUdb$QO*1#{(e#=}fko>pa~cnK?NoV@O-RC;-~&zx-Q z#;dWV^?94E!2XAuszp$xIyZGi&BvV76}V+u{H*w()&68(6<$PHWFob>74;Z6rgnnZ z&@ETu!j6gwf`5%qrZL1E1r-#cX9H1&^B)kki}limNsGD2P}E&li|cm*Ihh0irL5p^ z7bwSQLi2;`J3;65L0lr&EpoZJx92|F?smGQq;_$)NxZd&*%wimXw2D7xhA;li0?J+ zkM2W~s#iJa#uaI@D>a;ArN{XCS+Mv3a^_;i#w7Om&V1j*qu9%0|YGF=%ki z=LT(@z~tqIh}*CB@>87op5GKGCsBJD_>KCdc<;Ex^~qZDDnibIDYfQ}I$-s)d59f6 zOKH_htQ-xtpQzUwGv}}xi%}_`tfoD@B9f|Fn8p0Ztc@;wh_rv*aIyQQ-cFy(1S`vEco7HXVva*J(6WjxJ==>C%J5o#@Iz$wB<2Q$DI(4X}8AN2E3cF%3uaaJz|A-A(l3(U|S$UbNZYBrm<5l|Z zSD2D}QjQO00A#_sp`p%kK_spi8Y4%cLt8f?W~^@4DePB#FFbWR3VlK~1K?j|>N^~; zy=CtJ%e81ze@Ol9QWb`qyj%Qhsk`_}HqY>2ko&lwf>akq(+o}+OI;>y9t&NyyZ?oH zCO1NBkzKp55X}^fdU{6xTz%=Yb6;j)as|aqul)J&tJp$HQB{A5C(GAEg4Gk(Y@*aN zaE2b2I!Jks_YT-UwIW zT6X}ja_4~4EL}VvQTEA+O=>BHLU?#S7A&4fW}subK5@by#9U|MHEdDsJ)kwR)?T8~ z1b)Ky?w3A|z&GYHKEw}PNzvPj5efO6s44fZ7U$}-u%aDgo9htICJEo;D^h*ZMCBwZ z$IP3epMM3h5g`8UG*DDQ2_?lle0AYP74d>zA_>a=BkH0_i)}S4!xUVR-ps53G)H>) zK`7AbVD37<#Yf9R^VoEJn1*TQCiF8G(yCRUh8MXenuHH77kP_VC31X|j4%c(D;4hVZSbk^t-qqM&#ox6k$-F} z_pQNst2mjoEq8Wi`mfgAk_NLbJ5qhO9raWG(nyoJW!_P6_IOa)k(R!6%tJ zXy)Vud#MXM3J#E)<@q(sh$R!b@D?_PKe_?y3sR4ZlL?N*!0krGdZ)%$?IG(S0$XL> zYoj~aH5O$g1!teZIkqx9DdYJ3T{fc?EVNg?vGN)%o@S@lcpZ&)`6^XiRge0hkzvjW zP)$s%0V`HN0uf(M1(_2?o52M`mr9cxPmJ&()#>hl9@N4?qr2G=%Au!=`+x@1o3 z^a5rM0ccW`YP80@Xl4ow^J)tE*v;X44|vO2Iz>JzISo}AUaQ+MMr>KAk&`wGl&SV^ zoLdURdu5?%wbP=^u+HVm`}V`dclyu~n#Nj=o{m6+G4`x&5=9%=dJ_3fGq1r7`}^hO z9Yr@CObTifF|J_AQw-s&RuSjIUyBPu;`g%Xpyh8Oa9fq!-i#JO!Obz3BA@r=R4)O6 zZe@oDGTa7TRqzjkU(C|K&F4&ptrAAkxDeW6bfCMVBR34=u-$hiLE2~}r~iTfkWd8V8C5@xTze0uma@~{LT3APc}T6Rr>R;gXjAlrG6xUN*|x7C zO7=P(OQT9u^jZ9$=ZK)aG6N_5R~4PW&I19eY%p-GD-TT2%0sBm(6DFMPDQZPkvnB!hJnlxo+MBGPBuSn`otlz)9o5AzO_f9D8qX_;}r# ztgj+#RY6KL!bA;jssCJqp88O%c4{NZ+kB1=d^ijse$B|gHv5cIaat2K!OO4=_t&=Yc^aKv1gc%d>#wjUk#4+esgWVKTftTt!XM%6 z4&r($F$M}>8XAYLjr!97g9MtK?7ZRL==lDRXd_SNZhjfw)%~CpJDPs3u1Z5F2eVKt z{)01uYSb20`-DXaV~Ua~tq%x1iJ;jDevP`_ZU)zQ7E&K&dm6zLzC{n{ASTvq@fq5NTU$NVEea@q_xd3sz zWp$4!$MZBmZ~tAFP_TV7m)2|P&?z$6g^BWylLZ=ZSsFebeo&=Lbi0Ff!eL}A%6rqI z?xwAEu+F^L>^D{fuT66eg#BZ}v4Q9KtY!3+Kb=OwH^}|23{M>aD`m{C&udZrDsngw zv+J4Z%xAmZN8hKF)~vF#h%4#ES9D&-S_ImYt6nPV`d9j|peEB6z13yIM$AU3eKs@e z!f$g_KEA)^+NE}J*P`=$5l^HXj#sC0W9M4u(Y>Bd0dN!cK@ATu(Sx0Oo-?y!))9ta z9+XjpBDYEG>Q0V1gJ-tJJ#pyIYacxQ0BW?&fD>GfWE{mZFQee_%mu6-Ia|=LlZl4Q ze)b9DqnjV#MIRyVu>Ip0CnnoQDc3{y&9005*z^O6Wz}k3 ze6i2}fT#F5?)7`FWE^(frw~Wf9WX4I?C#-MA(C@<%Ch6h3?la76}ex#3HI+jKnCkO zxpJw~Zi4&2>f(h&QYLduSr`9`vt)a6Y4^%$JHUs_q!>ROwRK7T-W2$^kzDikz`ZtB z#{I@K%I*jkUVQpny*y(0WjeH@=;S7`h5W&i^zq%3nXKm=H93fJd`-3qXukF9 z5F$TWb~DIky9E((?K{S1@fe#+y_2flIbNuA8+p0WHonyk5I65XwAwqi@J2EI|3x>U zb3;czN>!wj6{`p6<_jOfgWel1aCa1b^kO(QYMs?G;vFH2p%e{Ri>vR8?{WSjbbjq`S;d|En_;!6~cNb#pbxIi0 z#ZAJS(ef1%02YW!WpWpJj-Lg5>okX@j-9c?ok1V*ldE}z?QwtAt^)MVX_LR zY!jfK`=hIO*+59c4g92xCI@8jYkB*kq3?Xtn}CyUHPgk+cNEw0<8%BiigOAMzZNXA zU);`j3W~g+=XzGNMyuf0AaOd#n#~7T{C4Ya$M%iIPiy$oxcqziY-+IR2Y>6|SJ)W%&Ea{B-aSk=pLqEHMI<5(Lg8p@yPwWfEXr=+|7eClNnZ6{;a$_0 F{|mZWa}@vp diff --git a/docs/rds/umn/en-us_image_0000002390290289.png b/docs/rds/umn/en-us_image_0000002390290289.png deleted file mode 100644 index bb7bf1b85cb107abd8414182524f2829f476d480..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 609 zcmV-n0-pVeP)UoMw(vdZW4`~99y zxYcUOntx=aQlSCH9?$J`I(a-ED3#pia5$7kFrUu}{g6XE9tXg2oY(7>e^IemJRA<> znM@|s6)oa6v)PPhB(5L`01O7hX0xI8Yq8ty>~=c|%0W9<5Cn_G0w9q{h@e;8 zYPAZWTCLKaiekN9i_lamMFXKw2vE5XTDYs#%49MTg4`<-_BiyW5ArP*u- zkWQz`uO_r|m&>KmXatbU<=tX!T zve~T5ExH;>-)wSE0szd$0>0KURUu7`t39lgXs3p?baEVzId0 vZeO6v+~=WhtUToV4ZoV@hbt!Yt{grAnb1+6YA45=00000NkvXXu0mjf-lrrq diff --git a/docs/rds/umn/en-us_image_0000002526234126.png b/docs/rds/umn/en-us_image_0000002526234126.png new file mode 100644 index 0000000000000000000000000000000000000000..c27951e692251cf641bf5f4949ff5e7a99541d0c GIT binary patch literal 179 zcmeAS@N?(olHy`uVBq!ia0vp^B0wz6!3HEJ^yqE{QjEnx?oJHr&dIz4a#+$GeH|GX zHuiJ>Nn{1`ISV`@iy0XB4ude`@%$AjKtT^r7sn6_|KuP3sSf(g>;J?@#QobpM`Mq` z3Ms}HsS1V+X_{?~OLnleIksK6?-0WIh9UCpipBtgHM~do+NLxvN%$q@;rrpgJ%dY% VoRm$jh8fUI22WQ%mvv4FO#n>$Hedh% literal 0 HcmV?d00001 diff --git a/docs/rds/umn/en-us_image_0000002534464226.png b/docs/rds/umn/en-us_image_0000002534464226.png new file mode 100644 index 0000000000000000000000000000000000000000..3c2fe725375820a8ef294eb307405dc85606066f GIT binary patch literal 579 zcmV-J0=)f+P)rTQz5QY2x@8bQ!O+^p{MHA7W0hDr6R0N7GNU1XBOtK9HX}e^9I7!>>&g`CVXPen- z^p8zj#n$P(Q|Z1!ncNlaM^0#CJF4V5h$JbSyQb1Zm7w8gOK_GoqGT$s1SHIYpaspp z%mb&_TeQ8GV6bRBMb$^0-n%`T*fw8iqYu6?!eL{esW;k7d@kIR-eke8-8hviHJZ(4 zOTnT8KE!P9#FRpUVcrYg(^A;K|XsuBpr(76K-iR(-59Ty0^$Wk4}jCObi~U}Ct7!VOQ{>l-pW zp4je3Unv}z7%mb!<%y?`;}Mj3nM`b@aA0CMQT-vXuBnCt6T@ZB3%u&rx9+-Zgt0;2 zk&GWq40l&5^Tg|v5wRN8@QY$BbMPZJ zXp3b0qWB6r7Y-e$^x~H(nac4y3ao8U`9iyQ=LttJ5vEc?x zo3;4=)$6y3!XUM

Storage Type

Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

-
  • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
  • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
+
  • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
  • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
  • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

AZ

@@ -70,6 +70,18 @@

By default, storage space of a read replica is the same as that of the primary DB instance.

+

IOPS

+ +

This parameter is required when the storage type is Flexible SSD.

+

The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

+ + +

Throughput

+ +

This parameter is required when the storage type is Flexible SSD.

+

The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

+ +

Disk Encryption

Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

diff --git a/docs/rds/umn/en-us_topic_connect_instance.html b/docs/rds/umn/en-us_topic_connect_instance.html index 46d7cc663..9a46db474 100644 --- a/docs/rds/umn/en-us_topic_connect_instance.html +++ b/docs/rds/umn/en-us_topic_connect_instance.html @@ -56,7 +56,7 @@

-

Using SSL to Connect to a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region and a project.
  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
  4. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
  5. Import the root certificate to the Linux OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

    • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

      For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

      +

      Using SSL to Connect to a DB Instance

      1. Log in to the management console.
      2. Click in the upper left corner and select a region and a project.
      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
      4. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
      5. Import the root certificate to the Linux OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

        • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

          For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

        • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.

      6. Connect to an RDS DB instance. The Linux OS is used as an example.

        mysql -h <host> -P <port> -u <userName> -p --ssl-ca=<caDIR> diff --git a/docs/rds/umn/en-us_topic_scale_cluster.html b/docs/rds/umn/en-us_topic_scale_cluster.html index 5dd7ae2e8..d2e1a8596 100644 --- a/docs/rds/umn/en-us_topic_scale_cluster.html +++ b/docs/rds/umn/en-us_topic_scale_cluster.html @@ -1,9 +1,9 @@ -

        Scaling up Storage Space

        +

        Scaling Up Storage Space

        Scenarios

        If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

        You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

        -

        RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

        +

        Services are not interrupted during storage scale-up.If you need to change the storage type, refer to Changing a Storage Type.

        Instance Becomes Read-Only When Storage Is Full

        For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

        @@ -37,19 +37,19 @@

        Constraints

        • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
        • The DB instance is in Scaling up state when its storage space is being scaled up and the backup services are not affected.
        • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
        • You cannot reboot or delete a DB instance that is being scaled up.
        • Storage space can only be scaled up, not down.
        • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.

        Scaling up a Primary DB Instance

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

          You can also perform the following operations to scale up storage space:

          -
          • Click the target DB instance to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
          +
          • Click the target DB instance to enter the Summary page. In the Storage & Backup area, click Scale Storage Space.

        5. On the displayed page, specify the new storage space and click Next.

          The minimum increment for each scaling is 10 GB.

        6. Confirm specifications.

          • If you need to modify your settings, click Previous.
          • If you do not need to modify your settings, click Submit.
          -

        7. View the scale-up result.

          Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Overview page to verify that the scale-up is successful.

          +

        8. View the scale-up result.

          Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Summary page to verify that the scale-up is successful.

          If the DB instance is running the MySQL DB engine, you can view the detailed progress and result of the task on the Task Center page. For details, see section Task Center.

        Scaling up a Read Replica

        Scaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately scale read replicas to meet service requirements. New storage space of read replicas after scaling up must be greater than or equal to that of the primary DB instance.

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, locate the target DB instance and click in front of it. Locate a read replica to be scaled and choose More > Scale Storage Space in the Operation column.

          You can also perform the following operations to scale up storage space:

          -
          • Click the target DB instance to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
          +
          • Click the target DB instance to enter the Summary page. In the Storage & Backup area, click Scale Storage Space.

        5. On the displayed page, specify the new storage space and click Next.

          The minimum increment for each scaling is 10 GB.

        6. Confirm specifications.

          • If you need to modify your settings, click Previous.
          • If you do not need to modify your settings, click Submit.
          -

        7. View the scale-up result.

          Scaling up storage space takes 3-5 minutes. During the time period, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Overview page to verify that the scale-up is successful.

          +

        8. View the scale-up result.

          Scaling up storage space takes 3-5 minutes. During the time period, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Summary page to verify that the scale-up is successful.

          If the read replica is running the MySQL DB engine, you can view the detailed progress and result of the task on the Task Center page. For details, see section Task Center.

        diff --git a/docs/rds/umn/en-us_topic_scale_rds.html b/docs/rds/umn/en-us_topic_scale_rds.html index bb06640ba..b8de8bf55 100644 --- a/docs/rds/umn/en-us_topic_scale_rds.html +++ b/docs/rds/umn/en-us_topic_scale_rds.html @@ -5,9 +5,9 @@

        Constraints

        • A DB instance cannot be deleted when its instance class is being changed.
        • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

          Alternatively, click the target DB instance to go to the Overview page. Under Instance Class, click Configure.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select a region and a project.
          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
          4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

            Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

          5. On the displayed page, specify the new instance class and click Next.

            -

          6. View the DB instance class change result.

            Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Overview page to check that the change is successful.

            +

          7. View the DB instance class change result.

            Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Summary page to check that the change is successful.

            After you change a MySQL instance class, the values of the following parameters will also be changed accordingly: back_log, innodb_buffer_pool_size, innodb_log_buffer_size, innodb_log_files_in_group, max_connections, innodb_page_cleaners, innodb_buffer_pool_instances, threadpool_size, and slave_parallel_workers.

          diff --git a/docs/rds/umn/en-us_topic_sqlserver_reset_password.html b/docs/rds/umn/en-us_topic_sqlserver_reset_password.html index e51274164..cae088fa4 100644 --- a/docs/rds/umn/en-us_topic_sqlserver_reset_password.html +++ b/docs/rds/umn/en-us_topic_sqlserver_reset_password.html @@ -13,7 +13,7 @@

        -

        Method 2

        1. Log in to the management console.
        2. Click in the upper left corner and select a region and a project.
        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
        4. On the Instances page, click the target DB instance.
        5. On the Overview page, find Administrator and click Reset Password under it.
        6. In the displayed dialog box, enter and confirm a new password.

          Keep this password secure. The system cannot retrieve it.

          +

          Method 2

          1. Log in to the management console.
          2. Click in the upper left corner and select a region and a project.
          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
          4. On the Instances page, click the target DB instance.
          5. On the Summary page, find Administrator and click Reset Password under it.
          6. In the displayed dialog box, enter and confirm a new password.

            Keep this password secure. The system cannot retrieve it.

            The new password must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_+?,). Enter a strong password and periodically change it for security reasons.

            If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
            • To submit the new password, click OK.
            • To cancel the reset operation, click Cancel.
            diff --git a/docs/rds/umn/rds_01_0020.html b/docs/rds/umn/rds_01_0020.html index a27f2fbf0..402feb2fe 100644 --- a/docs/rds/umn/rds_01_0020.html +++ b/docs/rds/umn/rds_01_0020.html @@ -2,54 +2,68 @@

            DB Instance Storage Types

            The database system is generally an important part of an IT system and has high requirements on storage I/O performance. You can select a storage type based on service demands. You cannot change the storage type after the DB instance is created.

            -

            Description

            RDS supports Cloud SSD and Extreme SSD to suit different performance requirements of your workloads.

            -
            • Cloud SSD

              Stores data in cloud disks for decoupled storage and compute. The maximum throughput is 350 MB/s.

              +

              Description

              RDS supports Cloud SSD, Extreme SSD and Flexible SSD to suit different performance requirements of your workloads.
              • Cloud SSD

                Stores data in cloud disks for decoupled storage and compute. The maximum throughput is 350 MB/s.

              • Extreme SSD

                Uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.

                +
              • Flexible SSD

                Decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

                +

                You can preconfigure an IOPS ranging from 3,000 to 128,000. This IOPS must also be less than or equal to 500 times the storage capacity. You can preconfigure a throughput ranging from 125 to 1,000 MiB/s. This throughput must also be less than or equal to the IOPS divided by 4.

              +

              Performance Comparison

              -
              @@ -80,17 +78,29 @@ - + + + + + + - -
              Table 1 Performance comparison

              Item

              +
              - - + - - - + - - - + - - - + - - - + - - - + diff --git a/docs/rds/umn/rds_01_0021.html b/docs/rds/umn/rds_01_0021.html index 4593cfc4c..02f1942d4 100644 --- a/docs/rds/umn/rds_01_0021.html +++ b/docs/rds/umn/rds_01_0021.html @@ -25,9 +25,9 @@ - - diff --git a/docs/rds/umn/rds_01_0089.html b/docs/rds/umn/rds_01_0089.html index b7083c6f2..27c9988f5 100644 --- a/docs/rds/umn/rds_01_0089.html +++ b/docs/rds/umn/rds_01_0089.html @@ -83,19 +83,6 @@ - - - - - - -
              Table 1 Performance comparison

              Item

              Cloud SSD

              +

              Cloud SSD

              Extreme SSD

              +

              Extreme SSD

              +

              Flexible SSD

              I/O performance

              +

              I/O performance

              Subpar I/O performance due to additional network I/O overheads

              +

              Subpar I/O performance due to additional network I/O overheads

              Higher I/O performance than cloud SSDs

              +

              Higher I/O performance than cloud SSDs

              +

              On-demand IOPS and throughput

              Elastic scalability

              +

              Elastic scalability

              Scaling in seconds

              +

              Scaling in seconds

              Scaling in seconds

              +

              Scaling in seconds

              +

              Scaling in seconds

              Maximum IOPS

              +

              Maximum IOPS

              50,000

              +

              50,000

              128,000

              +

              128,000

              +

              128,000

              Maximum throughput

              +

              Maximum throughput

              350 MiB/s

              +

              350 MiB/s

              For specifications with more than 32 vCPUs, the maximum throughput is 1,000 MiB/s.

              +

              For specifications with more than 32 vCPUs, the maximum throughput is 1,000 MiB/s.

              For specifications with 32 vCPUs or fewer, the maximum throughput may not reach 1,000 MiB/s due to the underlying architecture.

              1,000 MiB/s

              +

              Read/write latency

              +

              Read/write latency

              Medium

              +

              Medium

              Medium

              +

              Medium

              +

              Medium

              PostgreSQL

              • 17
              • 16
              • 15
              • 14
              • 13
              • 12
              +
              • 17
              • 16
              • 15
              • 14
              • 13
              • 17
              • 16
              • 15
              • 14
              • 13
              • 12
              +
              • 17
              • 16
              • 15
              • 14
              • 13

              Not supported

              November 2026

              12

              -

              Commercial use

              -

              October 2019

              -

              November 2024

              -

              February 2021

              -

              April 2026

              -
              diff --git a/docs/rds/umn/rds_02_0008.html b/docs/rds/umn/rds_02_0008.html index 7e0ee1a2a..7d20572ac 100644 --- a/docs/rds/umn/rds_02_0008.html +++ b/docs/rds/umn/rds_02_0008.html @@ -49,7 +49,7 @@

              Storage Type

              Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

              -
              • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
              • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
              +
              • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
              • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
              • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

              Primary AZ/Standby AZ

              @@ -71,8 +71,6 @@

              Instance Class

              Refers to the CPU and memory of a DB instance. Different instance classes have different numbers of database connections and different maximum IOPS.

              -

              -

              For details about instance classes, see section DB Instance Classes.

              After a DB instance is created, you can change its instance class. For details, see section Changing a DB Instance Class.

              Storage Space

              Contains the file system overhead required for inode, reserved block, and database operation.

              -

              After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space.

              +

              After a DB instance is created, you can scale up its storage space. For details, see section Scaling Up Storage Space.

              Enable autoscaling

              If the storage type is cloud SSD or extreme SSD, you can enable storage autoscaling. When the available storage drops to a specified threshold, autoscaling is triggered.
              • Enable autoscaling: If you select this option, autoscaling is enabled.
              • Trigger If Available Storage Drops To: If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.
              • Autoscaling Limit: The default value range is from 40 GB to 4,000 GB. The limit must be no less than the storage of the DB instance.
              +
              You can enable storage autoscaling. When the available storage drops to a specified threshold, autoscaling is triggered.
              • Enable autoscaling: If you select this option, autoscaling is enabled.
              • Trigger If Available Storage Drops To: If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.
              • Autoscaling Limit: The default value range is from 40 GB to 4,000 GB. The limit must be no less than the storage of the DB instance.
              NOTE:

              If you specify a read replica when creating a primary DB instance and enable storage autoscaling for the primary DB instance, storage autoscaling is also enabled for the read replica by default.

              IOPS

              +

              This parameter is required when the storage type is Flexible SSD.

              +

              The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

              +

              Throughput

              +

              This parameter is required when the storage type is Flexible SSD.

              +

              The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

              +

              Disk Encryption

              Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

              diff --git a/docs/rds/umn/rds_02_0016.html b/docs/rds/umn/rds_02_0016.html index e0d22dec7..dc08687b2 100644 --- a/docs/rds/umn/rds_02_0016.html +++ b/docs/rds/umn/rds_02_0016.html @@ -25,12 +25,12 @@

              <host>

              Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Overview page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connectivity area.

              +

              Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Summary page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connectivity area.

              <port>

              Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Overview page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

              +

              Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Summary page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

              <datastore>

              @@ -47,7 +47,7 @@ 
              psql --no-readline -U root -h 192.168.0.44 -p 5432 -d postgres -W

              -

              SSL Connection

              1. Log in to the management console.
              2. Click in the upper left corner and select a region and a project.
              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
              4. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
              5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

                For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

                +

                SSL Connection

                1. Log in to the management console.
                2. Click in the upper left corner and select a region and a project.
                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                4. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

                  For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

                6. Connect to an RDS DB instance. The Linux OS is used as an example.

                  psql --no-readline -h <host> -p <port> "dbname=<database> user=<user> sslmode=verify-ca sslrootcert=<ca-file-directory>"
                  - - - @@ -57,7 +57,7 @@

                  -

                  SSL Connection

                  1. Log in to the management console.
                  2. Click in the upper left corner and select a region and a project.
                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                  4. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
                  5. Import the root certificate to the Linux OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

                    • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

                      +

                      SSL Connection

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                      4. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                      5. Import the root certificate to the Linux OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?

                        • Since April 2017, RDS has offered a new root certificate that has a 20-year validation period. The new certificate takes effect after DB instances are rebooted. Replace the old certificate before it expires to improve system security.

                          For details, see section How Can I Identify the Validity Period of an SSL Root Certificate?

                        • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.
                        @@ -72,12 +72,12 @@
                  - - - -
                  Table 2 Parameter description

                  Parameter

                  @@ -58,12 +58,12 @@

                  <host>

                  IP address of the primary DB instance. To obtain this parameter, go to the Overview page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connectivity area.

                  +

                  IP address of the primary DB instance. To obtain this parameter, go to the Summary page of the DB instance. If the DB instance is accessed through the ECS, the IP address can be found in the Floating IP Address field in the Connectivity area.

                  <port>

                  Database port in use. The default value is 5432. To obtain this parameter, go to the Overview page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                  +

                  Database port in use. The default value is 5432. To obtain this parameter, go to the Summary page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                  <database>

                  diff --git a/docs/rds/umn/rds_02_0047.html b/docs/rds/umn/rds_02_0047.html index 4d3baece9..05ecfec92 100644 --- a/docs/rds/umn/rds_02_0047.html +++ b/docs/rds/umn/rds_02_0047.html @@ -30,7 +30,7 @@

                  Host

                  Indicates the floating IP address of the DB instance to be connected. To view the floating IP address and port of the DB instance, perform the following steps:
                  1. Log in to the RDS console.
                  2. Select the region in which the DB instance is located.
                  3. Click the target DB instance to enter the Overview page.
                  4. In the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, view the floating IP address.
                  +
                  Indicates the floating IP address of the DB instance to be connected. To view the floating IP address and port of the DB instance, perform the following steps:
                  1. Log in to the RDS console.
                  2. Select the region in which the DB instance is located.
                  3. Click the target DB instance to enter the Summary page.
                  4. In the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, view the floating IP address.

                  <host>

                  Floating IP address. To obtain this parameter, go to the Overview page of the DB instance. In the navigation pane on the left, choose Connectivity & Security. View the floating IP address in the Connection Information area,

                  +

                  Floating IP address. To obtain this parameter, go to the Summary page of the DB instance. In the navigation pane on the left, choose Connectivity & Security. View the floating IP address in the Connection Information area,

                  <port>

                  Database port. By default, the value is 3306. To obtain this parameter, go to the Overview page of the DB instance. In the navigation pane on the left, choose Connectivity & Security. View the database port in the Connection Information area.

                  +

                  Database port. By default, the value is 3306. To obtain this parameter, go to the Summary page of the DB instance. In the navigation pane on the left, choose Connectivity & Security. View the database port in the Connection Information area.

                  <userName>

                  diff --git a/docs/rds/umn/rds_02_0051.html b/docs/rds/umn/rds_02_0051.html index e2564eea0..f2d1f7cda 100644 --- a/docs/rds/umn/rds_02_0051.html +++ b/docs/rds/umn/rds_02_0051.html @@ -24,12 +24,12 @@

                  <host>

                  Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Overview page of the DB instance. The IP address can be found on the EIPs page.

                  +

                  Indicates the IP address of the primary DB instance. To obtain this parameter, go to the Summary page of the DB instance. The IP address can be found on the EIPs page.

                  <port>

                  Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Overview page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                  +

                  Indicates the database port in use. The default value is 5432. To obtain this parameter, go to the Summary page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                  <datastore>

                  @@ -46,7 +46,7 @@ 
                  psql --no-readline -U root -h 192.168.0.44 -p 5432 -d postgres -W

                  -

                  SSL Connection

                  1. Log in to the management console.
                  2. Click in the upper left corner and select a region and a project.
                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                  4. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
                  5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

                    For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

                    +

                    SSL Connection

                    1. Log in to the management console.
                    2. Click in the upper left corner and select a region and a project.
                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                    4. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                    5. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.

                      For details about how to import the root certificate to the Linux OS on the ECS, see How Can I Import the Root Certificate to a Windows or Linux OS?

                    6. Connect to an RDS DB instance. The Linux OS is used as an example.

                      psql --no-readline -h <host> -p <port> "dbname=<database> user=<user> sslmode=verify-ca sslrootcert=<ca-file-directory>"
                      - - + + + + + + - + + + + + + + + + + + +
                      Table 2 Parameter description

                      Parameter

                      @@ -57,12 +57,12 @@

                      <host>

                      IP address of the primary DB instance. To obtain this parameter, go to the Overview page of the DB instance. The IP address can be found on the EIPs page.

                      +

                      IP address of the primary DB instance. To obtain this parameter, go to the Summary page of the DB instance. The IP address can be found on the EIPs page.

                      <port>

                      Database port in use. The default value is 5432. To obtain this parameter, go to the Overview page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                      +

                      Database port in use. The default value is 5432. To obtain this parameter, go to the Summary page of the DB instance. The port number can be found in the Database Port field in the Connectivity area.

                      <database>

                      diff --git a/docs/rds/umn/rds_03_0007.html b/docs/rds/umn/rds_03_0007.html index a389f6d5a..05b177087 100644 --- a/docs/rds/umn/rds_03_0007.html +++ b/docs/rds/umn/rds_03_0007.html @@ -10,17 +10,17 @@

                      Non-SSL Connection

                      1. Start SQL Server Management Studio.
                      2. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

                        Figure 1 Connecting to the server
                        -
                        • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                          • The IP address is the EIP that has been bound to the DB instance.
                          • The port is the database port in the Connectivity area on the Overview page of the DB instance.
                          +
                          • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                            • The IP address is the EIP that has been bound to the DB instance.
                            • The port is the database port in the Connectivity area on the Summary page of the DB instance.
                          • Authentication: indicates the authentication mode. Select SQL Server Authentication.
                          • Login: indicates the RDS database username. The default administrator is rdsuser.
                          • Password: indicates the password of the RDS database username.

                        • Click Connect to connect to the DB instance.

                          If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

                      -

                      SSL Connection

                      1. Download the SSL root certificate and then upload it.

                        1. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
                        2. Upload the root certificate to the ECS to be connected to the DB instance.
                        3. Import the root certificate to the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
                          • Replace the old certificate before it expires to improve system security.
                          • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.
                          +

                          SSL Connection

                          1. Download the SSL root certificate and then upload it.

                            1. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                            2. Upload the root certificate to the ECS to be connected to the DB instance.
                            3. Import the root certificate to the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
                              • Replace the old certificate before it expires to improve system security.
                              • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.

                          2. Start SQL Server Management Studio.
                          3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

                            Figure 2 Connecting to the server
                            -
                            • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                              • The IP address is the EIP that has been bound to the DB instance.
                              • The port is the database port in the Connectivity area on the Overview page of the DB instance.
                              +
                              • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                                • The IP address is the EIP that has been bound to the DB instance.
                                • The port is the database port in the Connectivity area on the Summary page of the DB instance.
                              • Authentication: indicates the authentication mode. Select SQL Server Authentication.
                              • Login: indicates the RDS database username. The default administrator is rdsuser.
                              • Password: indicates the password of the RDS database username.

                            • On the Connection Properties page, enter related parameters and select Encrypt connection to enable SSL encryption. (By default, Encrypt connection is not selected. You need to select it manually.)

                              Figure 3 Connection properties

                            • Click Connect to connect to the DB instance.

                              If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

                              diff --git a/docs/rds/umn/rds_03_0011.html b/docs/rds/umn/rds_03_0011.html index 5ff5c55ad..e92b5225d 100644 --- a/docs/rds/umn/rds_03_0011.html +++ b/docs/rds/umn/rds_03_0011.html @@ -42,7 +42,7 @@

                      Storage Type

                      Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

                      -
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      +
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

                      AZ

                      @@ -73,6 +73,18 @@

                      By default, storage space of a read replica is the same as that of the primary DB instance.

                      IOPS

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                      +

                      Throughput

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                      +

                      Disk Encryption

                      Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

                      diff --git a/docs/rds/umn/rds_03_0013.html b/docs/rds/umn/rds_03_0013.html index 6f49f0d08..51de13744 100644 --- a/docs/rds/umn/rds_03_0013.html +++ b/docs/rds/umn/rds_03_0013.html @@ -14,17 +14,17 @@

                      Non-SSL Connection

                      1. Log in to the ECS or device that can access RDS.
                      2. Start SQL Server Management Studio.
                      3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

                        Figure 1 Connecting to the server
                        -
                        • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                          • The IP address is the floating IP address in the Connectivity area on the Overview page of the DB instance.
                          • The port is the database port in the Connectivity area on the Overview page of the DB instance.
                          +
                          • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                            • The IP address is the floating IP address in the Connectivity area on the Summary page of the DB instance.
                            • The port is the database port in the Connectivity area on the Summary page of the DB instance.
                          • Authentication: indicates the authentication mode. Select SQL Server Authentication.
                          • Login: indicates the RDS database username. The default administrator is rdsuser.
                          • Password: indicates the password of the RDS database username.

                        • Click Connect to connect to the DB instance.

                          If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

                      -

                      SSL Connection

                      1. Download the SSL root certificate and then upload it.

                        1. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSLfield to download the root certificate or certificate bundle.
                        2. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.
                        3. Import the root certificate into the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
                          • Replace the old certificate before it expires to improve system security.
                          • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.
                          +

                          SSL Connection

                          1. Download the SSL root certificate and then upload it.

                            1. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                            2. Upload the root certificate to the ECS or save it to the device to be connected to the DB instance.
                            3. Import the root certificate into the Windows OS on the ECS. For details, see How Can I Import the Root Certificate to a Windows or Linux OS?
                              • Replace the old certificate before it expires to improve system security.
                              • After you bind an EIP to a DB instance, you must reboot the instance for the SSL connection to take effect.

                          2. Start SQL Server Management Studio.
                          3. Choose Connect > Database Engine. In the displayed dialog box, enter login information.

                            Figure 2 Connecting to the server
                            -
                            • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                              • The IP address is the floating IP address in the Connectivity area on the Overview page of the DB instance.
                              • The port is the database port in the Connectivity area on the Overview page of the DB instance.
                              +
                              • Server name: indicates the IP address and port of the DB instance. Use a comma (,) to separate them. For example: x.x.x.x,8080.
                                • The IP address is the floating IP address in the Connectivity area on the Summary page of the DB instance.
                                • The port is the database port in the Connectivity area on the Summary page of the DB instance.
                              • Authentication: indicates the authentication mode. Select SQL Server Authentication.
                              • Login: indicates the RDS database username. The default administrator is rdsuser.
                              • Password: indicates the password of the RDS database username.

                            • On the Connection Properties page, enter related parameters and select Encrypt connection to enable SSL encryption. (By default, Encrypt connection is not selected. You need to select it manually.)

                              Figure 3 Connection properties

                            • Click Connect to connect to the DB instance.

                              If the connection fails, ensure that preparations have been correctly made in Preparations and try again.

                              diff --git a/docs/rds/umn/rds_03_0065.html b/docs/rds/umn/rds_03_0065.html index 3eb8c8d49..1a7ab2f04 100644 --- a/docs/rds/umn/rds_03_0065.html +++ b/docs/rds/umn/rds_03_0065.html @@ -49,7 +49,7 @@

                      Storage Type

                      Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

                      -
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      +
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

                      Primary AZ/Standby AZ

                      @@ -78,15 +78,27 @@

                      Storage Space

                      Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

                      -

                      After a DB instance is created, you can scale up its storage space. For details, see Scaling up Storage Space.

                      +

                      After a DB instance is created, you can scale up its storage space. For details, see Scaling Up Storage Space.

                      Enable autoscaling

                      If the storage type is cloud SSD or extreme SSD, you can enable storage autoscaling. When the available storage drops to a specified threshold, autoscaling is triggered.
                      • Enable Storage Autoscaling: If you select this option, storage autoscaling is enabled.
                      • Trigger If Available Storage Drops To: If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.
                      • Autoscaling Limit: The default value range is from 40 to 4000, in GB. The limit must be no less than the storage of the DB instance.
                      +
                      You can enable storage autoscaling. When the available storage drops to a specified threshold, autoscaling is triggered.
                      • Enable Storage Autoscaling: If you select this option, storage autoscaling is enabled.
                      • Trigger If Available Storage Drops To: If the available storage drops to a specified threshold or 10 GB, autoscaling is triggered.
                      • Autoscaling Limit: The default value range is from 40 to 4000, in GB. The limit must be no less than the storage of the DB instance.

                      IOPS

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                      +

                      Throughput

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                      +

                      Disk Encryption

                      Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

                      diff --git a/docs/rds/umn/rds_03_0100.html b/docs/rds/umn/rds_03_0100.html index 4b345db5f..c1e4ffe0a 100644 --- a/docs/rds/umn/rds_03_0100.html +++ b/docs/rds/umn/rds_03_0100.html @@ -1,11 +1,29 @@

                      Downloading a Binlog Backup File

                      -

                      Scenarios

                      RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary.

                      +

                      Scenarios

                      RDS for MySQL allows you to download binlog backup files to your client computer and use them to restore DB instances if necessary. For details, see Downloading a Binlog Backup File or Downloading a Merged Binlog.

                      -

                      Downloading a Binlog Backup File

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                      4. On the Instances page, click the target DB instance. The Overview page is displayed.
                      5. In the navigation pane on the left, choose Backups & Restorations. On the Binlog Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                        You can also select the binlog backups to be downloaded and click Download above the list.

                        +

                        Downloading a Binlog Backup File

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                        4. On the Instances page, click the target DB instance. The Summary page is displayed.
                        5. In the navigation pane on the left, choose Backups & Restorations. On the Binlog Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                          You can also select the binlog backups to be downloaded and click Download above the list.

                        6. After the download is complete, you can view the binlog backups locally.
                        +

                        Downloading a Merged Binlog

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                        4. On the Instances page, click the target DB instance. The Summary page is displayed.
                        5. In the navigation pane on the left, choose Backups & Restorations. On the Merged Binlogs page, select a binlog time range and click Merge.

                          • The maximum time range for merging binlogs is 24 hours.
                          • The available time range is consistent with the retention period you have set for the automated backups. For details about how to set the retention period, see Configuring an Intra-Region Backup Policy.
                          +

                        6. During the merging process, the file status is Merging. Wait until the status becomes Merged successfully and click Download in the Operation column.
                        7. In the displayed dialog box, select a download method.

                          After the merged file is downloaded, delete it. The system will delete it after 30 days if you do not delete it yourself.

                          +

                          On the Merged Binlogs page, you can locate the target merged binlog to be deleted and click Delete in the Operation column.

                          +
                          +
                          • Use OBS Browser+
                            1. Download OBS Browser+ by following Step 1 provided on the download guide page.
                            2. Decompress and install OBS Browser+.
                            3. Log in to OBS Browser+ using the username provided in Step 2 on the download guide page.
                            4. Add an external bucket using the bucket name provided in Step 2 on the download guide page.

                              In the Add External Bucket dialog box of OBS Browser+, enter the bucket name provided in step 2 on the download guide page, and click OK.

                              +
                            5. Download a merged binlog.

                              On the OBS Browser+ page, click the bucket that you added. In the search box on the right of the object list page, enter the backup file name and start a search. In the search result, locate the target backup and click in the Operation column.

                              +
                            +

                          • Use Current Browser

                            +

                            Download the merged binlog directly from the current browser.

                            +
                          • Use Download URL

                            Click to copy the URL within the validity period to download the merged binlog.

                            +
                            • You can use other download tools to download the merged binlog.
                            • You can also run the following command to download the merged binlog:

                              wget -O FILE_NAME --no-check-certificate "DOWNLOAD_URL"

                              +

                              Variables in the commands are as follows:

                              +

                              FILE_NAME: indicates the new name of the merged binlog file. The original backup file name may be too long and exceed the maximum characters allowed by the client file system. You are advised to use the -O argument with wget to rename the backup file.

                              +

                              DOWNLOAD_URL: indicates the location of the merged binlog to be downloaded. If the location contains special characters, escape is required.

                              +
                            +
                          +

                        +
                      diff --git a/docs/rds/umn/rds_04_0061.html b/docs/rds/umn/rds_04_0061.html index 1685ecfe0..4af8dafc8 100644 --- a/docs/rds/umn/rds_04_0061.html +++ b/docs/rds/umn/rds_04_0061.html @@ -49,7 +49,7 @@

                      Storage Type

                      Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

                      -
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      +
                      • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                      • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                      • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

                      Primary AZ/Standby AZ

                      @@ -78,7 +78,7 @@

                      Storage Space

                      Contains the file system overhead required for inode, reserved block, and database operation. Storage space can range in size from 40 GB to 4,000 GB and can be scaled up only by a multiple of 10 GB.

                      -

                      After a DB instance is created, you can scale up its storage space. For details, see section Scaling up Storage Space.

                      +

                      After a DB instance is created, you can scale up its storage space. For details, see section Scaling Up Storage Space.

                      Enable autoscaling

                      @@ -87,6 +87,18 @@

                      IOPS

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                      +

                      Throughput

                      +

                      This parameter is required when the storage type is Flexible SSD.

                      +

                      The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                      +

                      Disk Encryption

                      Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

                      diff --git a/docs/rds/umn/rds_05_0001.html b/docs/rds/umn/rds_05_0001.html index d38f23ed6..8623cf12b 100644 --- a/docs/rds/umn/rds_05_0001.html +++ b/docs/rds/umn/rds_05_0001.html @@ -18,7 +18,7 @@
                    7. Changing a DB Instance Class
                      8. -
                    8. Scaling up Storage Space
                      +
                    9. Scaling Up Storage Space
                    10. Storage Autoscaling
                      11. diff --git a/docs/rds/umn/rds_05_0003.html b/docs/rds/umn/rds_05_0003.html index d2b78fb01..30b62ff6f 100644 --- a/docs/rds/umn/rds_05_0003.html +++ b/docs/rds/umn/rds_05_0003.html @@ -7,7 +7,7 @@

                      Constraints

                      • If the replication delay between primary and standby DB instances is longer than 300 seconds, the minor version cannot be upgraded.
                      • Minor versions cannot be upgraded for DB instances with abnormal nodes.
                      • Currently, RDS for MySQL supports a maximum of 100,000 tables. If there are more than 100,000 tables, the minor version upgrade may fail.
                      -

                      Procedure

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                      4. On the Instances page, click the instance name to go to the Overview page.
                      5. Under DB Engine Version, click Upgrade Minor Version.
                      6. In the displayed dialog box, select a scheduled time and click OK.
                      +

                      Procedure

                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                      4. On the Instances page, click the instance name to go to the Summary page.
                      5. Under DB Engine Version, click Upgrade Minor Version.
                      6. In the displayed dialog box, select a scheduled time and click OK.
                      diff --git a/docs/rds/umn/rds_05_0024.html b/docs/rds/umn/rds_05_0024.html index b297eaabc..346450af5 100644 --- a/docs/rds/umn/rds_05_0024.html +++ b/docs/rds/umn/rds_05_0024.html @@ -9,7 +9,7 @@

                      Changing a Floating IP Address

                      You can change the floating IP address of an existing DB instance.

                      -
                      1. Log in to the management console.
                      2. Click in the upper left corner and select a region and a project.
                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                      4. On the Instances page, click the target DB instance name to go to the Overview page.
                      5. Under Floating IP Address, click Configure.
                      6. In the displayed dialog box, check the number of in-use IP addresses. If the in-use IP addresses are less than 254, there are unused floating IP addresses.
                      7. Select an available IP address and click OK.

                        An in-use IP address cannot be used as the new floating IP address of the DB instance.

                        +
                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                        4. On the Instances page, click the target DB instance name to go to the Summary page.
                        5. Under Floating IP Address, click Configure.
                        6. In the displayed dialog box, check the number of in-use IP addresses. If the in-use IP addresses are less than 254, there are unused floating IP addresses.
                        7. Select an available IP address and click OK.

                          An in-use IP address cannot be used as the new floating IP address of the DB instance.

                        diff --git a/docs/rds/umn/rds_05_0038.html b/docs/rds/umn/rds_05_0038.html index 8eacab7c2..772cd7f3f 100644 --- a/docs/rds/umn/rds_05_0038.html +++ b/docs/rds/umn/rds_05_0038.html @@ -5,7 +5,7 @@

                        Precautions

                        • During the maintenance window, the DB instance will be intermittently disconnected for one or two times. Ensure that your applications support automatic reconnection.
                        -

                        Procedure

                        1. Log in to the management console.
                        2. Click in the upper left corner and select a region and a project.
                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                        4. On the Instances page, click the target DB instance name to go to the Overview page. Under Maintenance Window, click Configure.
                        5. In the displayed dialog box, select an interval and a time range, and click OK.

                          Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                          4. On the Instances page, click the target DB instance name to go to the Summary page. Under Maintenance Window, click Configure.
                          5. In the displayed dialog box, select an interval and a time range, and click OK.

                            Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                          diff --git a/docs/rds/umn/rds_05_0039.html b/docs/rds/umn/rds_05_0039.html index fef9e619e..e95c0209a 100644 --- a/docs/rds/umn/rds_05_0039.html +++ b/docs/rds/umn/rds_05_0039.html @@ -6,9 +6,9 @@

                          You can enable storage autoscaling in either of the following ways:

                          • Enable this function when you create a DB instance. For details, see Step 1: Create a DB Instance.
                          • Enable this function after you create a DB instance. See the operations provided in this section.
                          -

                          Constraints

                          • The storage space can be scaled up automatically only when your instance status is Available or Storage full.
                          • Storage autoscaling for RDS for MySQL DB instances is supported only for cloud SSD and extreme SSD storage types.
                          • The maximum allowed storage is 4,000 GB.
                          • For primary/standby DB instances, autoscaling the storage for the primary DB instance will also autoscale the storage for the standby DB instance.
                          • Storage autoscaling is unavailable when the DB instance is in any of the following statuses: changing instance class, upgrading a minor version, migrating the standby DB instance, and rebooting.
                          +

                          Constraints

                          • The storage space can be scaled up automatically only when your instance status is Available or Storage full.
                          • The maximum allowed storage is 4,000 GB.
                          • For primary/standby DB instances, autoscaling the storage for the primary DB instance will also autoscale the storage for the standby DB instance.
                          • Storage autoscaling is unavailable when the DB instance is in any of the following statuses: changing instance class, upgrading a minor version, migrating the standby DB instance, and rebooting.
                          -

                          Procedure

                          1. Log in to the management console.
                          2. Click in the upper left corner and select a region and a project.
                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                          4. On the Instances page, click the target DB instance or read replica name (click in front of a DB instance to locate the read replica) to go to the Overview page.
                          5. In the Storage & Backup area, toggle on the Storage Autoscaling switch.
                          6. In the displayed dialog box, set the following parameters:

                            +

                            Procedure

                            1. Log in to the management console.
                            2. Click in the upper left corner and select a region and a project.
                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                            4. On the Instances page, click the target DB instance or read replica name (click in front of a DB instance to locate the read replica) to go to the Summary page.
                            5. In the Storage & Backup area, toggle on the Storage Autoscaling switch.
                            6. In the displayed dialog box, set the following parameters:

                              Table 1 Parameter description

                              Parameter

                              Description

                              diff --git a/docs/rds/umn/rds_05_0060.html b/docs/rds/umn/rds_05_0060.html index 225efca3d..a509e0670 100644 --- a/docs/rds/umn/rds_05_0060.html +++ b/docs/rds/umn/rds_05_0060.html @@ -2,10 +2,10 @@

                              Migrating a Standby DB Instance

                              Scenarios

                              You can migrate a standby DB instance to another AZ in the same region as the original AZ.

                              -
                              • Primary/standby instances running MySQL 5.7, or 8.0 support standby instance migration to another AZ.
                              • DDL operations and scheduled events will be suspended during migration. To prevent service interruptions, perform the migration during off-peak hours.
                              +
                              • Primary/standby instances running MySQL 5.7 or 8.0 support standby instance migration to another AZ.
                              • DDL operations and scheduled events will be suspended during migration. To prevent service interruptions, perform the migration during off-peak hours.
                              -

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, locate the target DB instance and choose More > Migrate Standby Instance to Another AZ in the Operation column.
                              5. On the displayed page, select a target AZ and click Submit.
                              6. After the migration is complete, you can view and manage the DB instance on the Instances page.

                                • During the migration process, the DB instance status is Migrating standby DB instance. You can view the progress on the Task Center page. For details, see section Task Center.
                                • In the upper right corner of the DB instance list, click to refresh the list. After the migration is complete, the DB instance status will become Available.
                                • On the Overview page, find AZ and check the AZ hosting the standby DB instance.
                                +

                                Procedure

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, locate the target DB instance and choose More > Migrate Standby Instance to Another AZ in the Operation column.
                                5. On the displayed page, select a target AZ and click Submit.
                                6. After the migration is complete, you can view and manage the DB instance on the Instances page.

                                  • During the migration process, the DB instance status is Migrating standby DB instance. You can view the progress on the Task Center page. For details, see section Task Center.
                                  • In the upper right corner of the DB instance list, click to refresh the list. After the migration is complete, the DB instance status will become Available.
                                  • On the Summary page, find AZ and check the AZ hosting the standby DB instance.

                                diff --git a/docs/rds/umn/rds_05_0085.html b/docs/rds/umn/rds_05_0085.html index f74264681..5a3073f12 100644 --- a/docs/rds/umn/rds_05_0085.html +++ b/docs/rds/umn/rds_05_0085.html @@ -7,7 +7,7 @@

                                Procedure

                                When you buy a DB instance, the system automatically assigns a private domain name to your instance.

                                After the DB instance is created, you can change the private domain name as needed.

                                -
                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, click the target DB instance name to go to the Overview page.
                                5. Under Private Domain Name, click Configure.

                                  Alternatively, in the navigation pane on the left, choose Connectivity & Security. On the displayed page, click Change next to the Private Domain Name field.

                                  +
                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select a region and a project.
                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                  4. On the Instances page, click the target DB instance name to go to the Summary page.
                                  5. Under Private Domain Name, click Configure.

                                    Alternatively, in the navigation pane on the left, choose Connectivity & Security. On the displayed page, click Change next to the Private Domain Name field.

                                  6. In the displayed dialog box, enter a new domain name and click OK.

                                    • Only the prefix of a private domain name can be modified.
                                    • The prefix of a private domain name contains 8 to 63 characters, and can include only letters and digits.
                                    • The new private domain name must be different from existing ones.

                              diff --git a/docs/rds/umn/rds_05_0140.html b/docs/rds/umn/rds_05_0140.html index 13d6d36d7..2d37353d9 100644 --- a/docs/rds/umn/rds_05_0140.html +++ b/docs/rds/umn/rds_05_0140.html @@ -2,6 +2,7 @@

                              Changing a Storage Type

                              Scenarios

                              If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.

                              +

                              For details about storage types, see DB Instance Storage Types.

                              Constraints

                              Table 1 Constraints

                              Phase

                              @@ -29,7 +30,7 @@
                              -
                              Table 2 Storage types

                              Instance Type

                              +
                              @@ -37,24 +38,62 @@ - - - - - + + + + + + + + + + + + + + + + + + + +
                              Table 2 Storage types that can be changed

                              Instance Type

                              Original Storage Type
                              • Primary/Standby
                              • Read Replica
                              • Single
                              +

                              Single

                              Cloud SSD

                              +

                              Cloud SSD

                              Extreme SSD

                              +

                              Flexible SSD

                              Ultra-high I/O

                              +

                              Flexible SSD

                              Cloud SSD or extreme SSD

                              +

                              Cloud SSD

                              +

                              Read Replica

                              +

                              Cloud SSD

                              +

                              Extreme SSD or Flexible SSD

                              +

                              Extreme SSD

                              +

                              Cloud SSD or Flexible SSD

                              +

                              Flexible SSD

                              +

                              Cloud SSD or Extreme SSD

                              +

                              Primary/Standby

                              +

                              Cloud SSD

                              +

                              Extreme SSD or Flexible SSD

                              +

                              Extreme SSD

                              +

                              Cloud SSD or Flexible SSD

                              +

                              Flexible SSD

                              +

                              Cloud SSD or Extreme SSD
                              -

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, locate a DB instance using cloud SSD and choose More > Change Instance Class in the Operation column.

                                Alternatively, click the instance name to go to the Overview page. Under Instance Class, click Configure.

                                -

                              5. On the displayed page, select Extreme SSD for Storage Type and click Next.
                              6. Confirm the new storage type. Click Submit.
                              7. Check the results.

                                Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Overview page.

                                +

                                Procedure

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, locate a DB instance using cloud SSD and choose More > Change Instance Class in the Operation column.

                                  Alternatively, click the instance name to go to the Summary page. Under Instance Class, click Configure.

                                  +

                                5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

                                  If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

                                  +
                                  • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

                                    This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                                    +
                                  • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

                                    This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                                    +
                                  +

                                6. Confirm the configurations and Click Submit.
                                7. Check the results.

                                  Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.

                              diff --git a/docs/rds/umn/rds_08_0003.html b/docs/rds/umn/rds_08_0003.html index 89a05d4be..fc9142c08 100644 --- a/docs/rds/umn/rds_08_0003.html +++ b/docs/rds/umn/rds_08_0003.html @@ -3,7 +3,7 @@

                              Changing a Security Group

                              Scenarios

                              This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

                              -

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, click the target primary DB instance or read replica.
                              5. On the Overview page, click Configure under Security Group.
                              6. In the displayed dialog box, select one from the drop-down list.
                              7. Click OK to submit the modification.
                              8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Overview page to view the results.
                              +

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, click the target primary DB instance or read replica.
                              5. On the Summary page, click Configure under Security Group.
                              6. In the displayed dialog box, select one from the drop-down list.
                              7. Click OK to submit the modification.
                              8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Summary page to view the results.
                              diff --git a/docs/rds/umn/rds_08_0004.html b/docs/rds/umn/rds_08_0004.html index 298698ea4..3e279adf2 100644 --- a/docs/rds/umn/rds_08_0004.html +++ b/docs/rds/umn/rds_08_0004.html @@ -9,7 +9,17 @@

                              Constraints

                              • The number of tables in a DB instance affects the backup speed. The maximum number of tables is 500,000.
                              • The system verifies the connection to the DB instance when starting a full backup task. If either of the following conditions is met, the verification fails and a retry is automatically performed. If the retry fails, the backup will fail.
                                • DDL operations are being performed on the DB instance.
                                • The backup lock failed to be obtained from the DB instance.
                              -

                              Modifying an Automated Backup Policy

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, click the target DB instance.
                              5. On the Backups & Restorations page, in the upper right corner of the page, choose Modify Backup Policy > Configure Same-Region Backup Policy. On the displayed page, you can view the existing backup policy. If you want to modify the policy, adjust the values of the following parameters:

                                • Retention Period is the number of days that your automated backups are saved for. Increasing the retention period will improve data reliability.
                                • If you shorten the retention period, the new backup policy takes effect for all backup files. Any backup files that have expired, based on a newly configured retention period, will be deleted.
                                • The backup retention period is the number of days you want automated full backups and binlog backups of your DB instance to be saved for. It ranges from 1–732 days. The backup time window is one hour. You are advised to select an off-peak time window for automated backups. By default, each day of the week is selected for Backup Cycle and you can change it. At least one day must be selected.
                                +

                                Modifying an Automated Backup Policy

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, click the target DB instance.
                                5. On the Backups & Restorations page, in the upper right corner of the page, choose Modify Backup Policy > Configure Same-Region Backup Policy. On the displayed page, you can view the existing backup policy. If you want to modify the policy, adjust the values of the following parameters:

                                  • Retention Period: It indicates how many days your automated full backups and binlog backups can be retained. The retention period is from 1 to 732 days and the default value is 7.
                                    • Extending the retention period enhances data availability.
                                    • Reducing the retention period takes effect for existing backups. Any backups (except manual backups) that have expired will be automatically deleted. Exercise caution when performing this operation.
                                    +

                                    Automatic deletion policy for full backups:

                                    +

                                    To ensure data integrity, the system keeps the most recent backup that has exceeded the retention period during automatic deletions. This ensures that data within the retention period can still be restored.

                                    +

                                    For example, if Backup Cycle was set to Monday and Tuesday and Retention Period was set to 2, the deletion behavior is as follows:

                                    +
                                    • The full backup created on Monday is automatically deleted on Thursday.

                                      The full backup created on Monday expires on Wednesday, but according to the deletion policy, the system retains the most recent full backup that has exceeded the retention period. So it is retained until a new backup expires. The next full backup is created on Tuesday and expires on Thursday. Therefore, on Thursday, the Monday backup is deleted and the Tuesday backup is retained.

                                      +
                                    • The full backup created on Tuesday is automatically deleted on Wednesday of the following week.

                                      The backup generated on Tuesday will expire on Thursday, but as it is the last backup, so it will be retained until a new backup expires. The next backup will be generated on the next Monday and will expire on the next Wednesday. So the full backup generated on Tuesday will not be automatically deleted until the next Wednesday.

                                      +
                                    +
                                  • Automatic deletion policy for binlog backups:

                                    To ensure data integrity, the system keeps the binlog backup of the previous day when the full backup is deleted. This ensures that data within the retention period can still be restored.

                                    +
                                  • Time Window: Set it to a one-hour period the backup will be scheduled, such as 01:00-02:00 or 12:00-13:00. It indicates when the backup starts, not the duration of the entire backup task. The backup duration depends on the data volume of your instance.

                                    To minimize potential impact on workloads, set the time window to off-peak hours. The backup time window is saved using the UTC time zone of your local browser. It changes with the time zone if the DST or standard time is switched.

                                    +
                                    +
                                  • Backup Cycle: All options are selected by default, but you can change it. Select at least one day of the week.

                                6. Click OK.
                              diff --git a/docs/rds/umn/rds_08_0013.html b/docs/rds/umn/rds_08_0013.html index 9be1bb394..af33467c1 100644 --- a/docs/rds/umn/rds_08_0013.html +++ b/docs/rds/umn/rds_08_0013.html @@ -5,7 +5,7 @@

                              Constraints

                              • If the DB instance status is Abnormal, the reboot may fail.
                              • Rebooting DB instances will cause service interruptions. During the reboot process, the DB instance status is Rebooting.
                              • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
                              -

                              Procedure

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

                                Alternatively, click the target DB instance on the Instances page to go to the Overview page. Click and choose Reboot in the upper right corner.

                                +

                                Procedure

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

                                  Alternatively, click the target DB instance on the Instances page to go to the Summary page. Click and choose Reboot in the upper right corner.

                                  For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

                                5. In the displayed dialog box, click Yes.
                                6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
                                diff --git a/docs/rds/umn/rds_08_0025.html b/docs/rds/umn/rds_08_0025.html index f2a95aca1..ee5248a2d 100644 --- a/docs/rds/umn/rds_08_0025.html +++ b/docs/rds/umn/rds_08_0025.html @@ -1,8 +1,8 @@

                                Introduction to Instance Overview

                                -

                                On the Overview page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. Intelligent anomaly diagnosis uses operational data analytics and intelligent algorithms to access instance health, and provides you with solutions and suggestions for handling detected exceptions.

                                -

                                Functions

                                Table 1 lists the functions provided on the Overview page.

                                +

                                On the Summary page, you can get knowledge of the overall status of your RDS for MySQL instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. Intelligent anomaly diagnosis uses operational data analytics and intelligent algorithms to access instance health, and provides you with solutions and suggestions for handling detected exceptions.

                                +

                                Functions

                                Table 1 lists the functions provided on the Summary page.

                                @@ -43,7 +43,7 @@
                                Table 1 Function description

                                Function

                                -

                                Instance Information

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, click the target instance name to go to the Overview page.
                                5. In the Instance Information area, check the instance information and modify the instance as required.
                                +

                                Instance Information

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, click the target instance name to go to the Summary page.
                                5. In the Instance Information area, check the instance information and modify the instance as required.

                                Alarms

                                In the Alarms area, check alarm information of your instance.

                                Based on the configured alarm rules, you can see active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.

                                @@ -201,7 +201,7 @@

                                Storage & Backup

                                In the Storage & Backup area, you can check the storage space usage and backup space usage of your instance, enable disk encryption, and scale up storage space.

                                • Files that occupy the storage space include data files, log files, and other temporary files. To check the distribution and changes of used storage, see Managing Storage Capacity.
                                • After an instance is purchased, the disk encryption status and the key cannot be changed.

                                  If you enable disk encryption when purchasing an instance, the new storage space after scale-up still uses the original encryption key. Keep the key secure. Once the key is disabled, deleted, or frozen, your instance will become inaccessible.

                                  -
                                • As workload data increases, the storage capacity of your instance may be insufficient. To scale up the storage space, see Scaling up Storage Space.
                                • Backups are stored as packages in OBS and occupy the backup space. If the free space RDS provides is used up, the additional space required will be billed.
                                +
                              5. As workload data increases, the storage capacity of your instance may be insufficient. To scale up the storage space, see Scaling Up Storage Space.
                              6. Backups are stored as packages in OBS and occupy the backup space. If the free space RDS provides is used up, the additional space required will be billed.
                              diff --git a/docs/rds/umn/rds_08_0026.html b/docs/rds/umn/rds_08_0026.html index fa653e4dc..a319b3a28 100644 --- a/docs/rds/umn/rds_08_0026.html +++ b/docs/rds/umn/rds_08_0026.html @@ -3,7 +3,7 @@

                              Managing Real-Time Sessions

                              Scenarios

                              You can view current session statistics of your instance, identify abnormal sessions, and kill the sessions.

                              -

                              Setting Slow Session Threshold

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, click the DB instance name.
                              5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                              6. Click the Sessions tab. You can perform the following operations on this tab page:

                                • Viewing session statistics

                                  In the sessions statistics, you can view statistics on the slow sessions, active sessions, total sessions, long transaction sessions by user, access host, and database.

                                  +

                                  Setting Slow Session Threshold

                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select a region and a project.
                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                  4. On the Instances page, click the DB instance name.
                                  5. In the navigation pane, choose Sessions under DBA Assistant.
                                  6. On the Sessions page. You can perform the following operations on this tab page:

                                    • Viewing session statistics

                                      In the sessions statistics, you can view statistics on the slow sessions, active sessions, total sessions, long transaction sessions by user, access host, and database.

                                    • Setting a slow session threshold

                                      Click next to the Slow Session Threshold field. In the displayed dialog box, set a slow session threshold and click OK. Sessions whose execution durations are greater than this threshold are automatically displayed.

                                    • Killing abnormal sessions

                                      In the session list, you can view session details. You can also select the abnormal session you want to end and click Kill Session to recover the database.

                                      A maximum of 100 sessions can be killed at a time.

                                      diff --git a/docs/rds/umn/rds_08_0027.html b/docs/rds/umn/rds_08_0027.html index 2e64ece69..864b690c4 100644 --- a/docs/rds/umn/rds_08_0027.html +++ b/docs/rds/umn/rds_08_0027.html @@ -2,7 +2,7 @@

                                      Viewing Performance Metrics of a DB Instance

                                      DBA Assistant allows you to view the performance metrics of your DB instance. Historical trends of performance metrics within a specified time period help you learn about the status and resource usage of your DB instance. If any alarm is reported, you can take actions timely.

                                      -

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                      4. On the Instances page, click the DB instance name.
                                      5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                      6. Click the Performance tab to view historical performance for each metric of your instance within the same time range on different days.

                                        +

                                        Procedure

                                        1. Log in to the management console.
                                        2. Click in the upper left corner and select a region and a project.
                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                        4. On the Instances page, click the DB instance name.
                                        5. In the navigation pane, choose Performance under DBA Assistant.
                                        6. Check metric changes of your instance within the same time range on different days.

                                      diff --git a/docs/rds/umn/rds_08_0028.html b/docs/rds/umn/rds_08_0028.html index 0d6fc77ba..912b6a949 100644 --- a/docs/rds/umn/rds_08_0028.html +++ b/docs/rds/umn/rds_08_0028.html @@ -43,11 +43,11 @@
                              -

                              Viewing the Storage Overview

                              1. Log in to the management console.
                              2. Click in the upper left corner and select a region and a project.
                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                              4. On the Instances page, click the target DB instance name.
                              5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                              6. Click the Storage Analysis tab to view storage usage. If your storage is insufficient, scale it up. Or you can enable storage autoscaling.

                                If the average daily increase in last week is 0 GB, the estimated available days of storage are unlimited and are not displayed.

                                +

                                Viewing the Storage Overview

                                1. Log in to the management console.
                                2. Click in the upper left corner and select a region and a project.
                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                4. On the Instances page, click the target DB instance name.
                                5. In the navigation pane, choose Storage Analysis under DBA Assistant.
                                6. Check your storage usage. If the storage is insufficient, scale it up. Or you can enable storage autoscaling.

                                  If the average daily increase in last week is 0 GB, the estimated available days of storage are unlimited and are not displayed.

                                -

                                Tablespaces

                                This function counts tables with abnormal tablespace growth, tables without primary keys, and tables without indexes. To use this function, subscribe to Intelligent O&M first.

                                -
                                1. Click the Storage Analysis tab to view abnormal tables.
                                2. Click Subscribe. In the displayed dialog box, you can learn about Intelligent O&M functions and pricing.
                                3. After subscribing to Intelligent O&M, view the table diagnosis results of your instance.
                                4. Click next to Auto Diagnosis. In the displayed dialog box, configure the daily tablespace increase limit and click OK.

                                  When the size of a single table is greater than the threshold, the system automatically filters the table and collects statistics on the number of such tables on the Tablespaces page. The system filters tables once a day.

                                  +

                                  Tablespaces

                                  This function counts tables with abnormal tablespace growth, tables without primary keys, and tables without indexes. To use this function, upgrade DBA Assistant first.

                                  +
                                  1. Click the Storage Analysis tab to view abnormal tables.
                                  2. Click Upgrade DBA Assistant. In the displayed dialog box, you can learn about the enhanced features and billing rules.
                                  3. After the upgrade is complete, view the table diagnosis results of your instance.
                                  4. Click next to Auto Diagnosis. In the displayed dialog box, configure the daily tablespace increase limit and click OK.

                                    When the size of a single table is greater than the threshold, the system automatically filters the table and collects statistics on the number of such tables on the Tablespaces page. The system filters tables once a day.

                                  Disk Space Distribution

                                  You can view storage space distribution of your instance.

                                  diff --git a/docs/rds/umn/rds_08_0029.html b/docs/rds/umn/rds_08_0029.html index 1533bfcc1..2827e4d1a 100644 --- a/docs/rds/umn/rds_08_0029.html +++ b/docs/rds/umn/rds_08_0029.html @@ -13,7 +13,7 @@
                                  • DBA Assistant analyzes error logs at regular intervals, parses deadlock information, and performs comprehensive deadlock analysis.
                                  • Dependent parameters:
                                    • The innodb_deadlock_detect parameter must be set to ON (only for RDS for MySQL 5.7).
                                    • The innodb_print_all_deadlocks parameter must be set to ON and the log_error_verbosity parameter must be set to 3 (only for other versions than 5.7).
                                  • Up to 10,000 records can be displayed.
                                  -

                                  Procedure

                                  1. Log in to the management console.
                                  2. Click in the upper left corner and select a region and a project.
                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                  4. On the Instances page, click the DB instance name.
                                  5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                  6. Click the Locks & Transactions tab and enter the administrator password to log in to the database.
                                  7. On the Locks & Transactions tab page, perform the following operations:

                                    • Click the Metadata Locks tab, create a lock analysis task and check whether the instance has metadata locks.

                                      By default, locks whose wait time is longer than 10s are displayed, but you can change this time if needed.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      2. Click in the upper left corner and select a region and a project.
                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                      4. On the Instances page, click the DB instance name.
                                      5. In the navigation pane, choose Locks & Transactions under DBA Assistant.
                                      6. On the displayed page, enter the administrator password to log in to the database.
                                      7. On the Locks tab page, perform the following operations:

                                        • Click the Metadata Locks tab, create a lock analysis task and check whether the instance has metadata locks.

                                          By default, locks whose wait time is longer than 10s are displayed, but you can change this time if needed.

                                        • Click the InnoDB Locks tab, create a lock analysis task and check whether the instance has InnoDB locks.

                                          By default, locks whose wait time is longer than 10s are displayed, but you can change this time if needed.

                                        • Click the Deadlock Analysis tab and create a lock analysis task. DBA Assistant analyzes the latest deadlock log returned by SHOW ENGINE INNODB STATUS. If there are multiple deadlocks, only the latest one is analyzed.

                                          You can only query lock analysis data of the past seven days.

                                        • Click the Full Deadlock Analysis tab and enable Full Deadlock Analysis. DBA Assistant regularly examines error logs, extracts deadlock details from them, and conducts a full deadlock analysis.

                                          You can only query lock analysis data of the past seven days.

                                          diff --git a/docs/rds/umn/rds_08_0030.html b/docs/rds/umn/rds_08_0030.html index 1290cc309..d30989da2 100644 --- a/docs/rds/umn/rds_08_0030.html +++ b/docs/rds/umn/rds_08_0030.html @@ -3,10 +3,12 @@

                                          Viewing Slow Query Logs of a DB Instance

                                          Scenarios

                                          Slow Query Log displays a chart of SQL statements that are taking too long to execute and allows you to sort slow SQL statements by multiple dimensions, such as by user, host, or SQL template. It helps you quickly identify bottlenecks and improve instance performance.

                                          -

                                          Procedure

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                          4. On the Instances page, click the DB instance name.
                                          5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                          6. Click the Slow Query Logs tab.

                                            Slow SQL Analysis needs to be purchased separately. To use this function, subscribe to Intelligent O&M first.

                                            +

                                            Procedure

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                            4. On the Instances page, click the DB instance name.
                                            5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                            6. Click the Slow Query Logs tab.

                                              Slow SQL Analysis needs to be purchased separately. To use this function, upgrade DBA Assistant first.

                                              -

                                            7. Click Subscribe. In the displayed dialog box, you can learn about Intelligent O&M functions and pricing.
                                            8. After subscribing to Intelligent O&M, view slow queries over time of your instance.
                                            9. You can view slow queries over time and you can see the slow log archive history for the last 1 hour, last 3 hours, last 12 hours, or a custom time period (spanning no more than one day).
                                            10. View slow query log details and template statistics.

                                              • To export slow query log information, click Export.
                                              • To view log export history, click View Export List.
                                              -

                                            +

                                          7. Click Upgrade DBA Assistant. In the displayed dialog box, you can learn about the enhanced features and billing rules.
                                          8. View slow queries over time and archived slow query logs in the last 1 hour, last 3 hours, last 12 hours, or a custom time period (spanning no more than one day).
                                          9. To export slow query log details or statistics, click the Details or Statistics tab above the log list and click Export on the tab page.
                                          +
                                          +

                                          Follow-up Operations

                                          To view historical export records, do as follows:

                                          +
                                          1. Above the log list, click the Details or Statistics tab.
                                          2. Click View All Export Records. The displayed dialog box shows all historical export records.
                                          diff --git a/docs/rds/umn/rds_08_0031.html b/docs/rds/umn/rds_08_0031.html index 9cfab60b4..e77802f63 100644 --- a/docs/rds/umn/rds_08_0031.html +++ b/docs/rds/umn/rds_08_0031.html @@ -3,10 +3,9 @@

                                          Viewing Top SQL Statements of a DB Instance

                                          Scenarios

                                          Top SQL shows the SQL queries that have been contributed at most to database load. You can sort them by multiple dimensions.

                                          -

                                          Procedure

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                          4. On the Instances page, click the DB instance name.
                                          5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                          6. Choose SQL Explorer > Top SQL.

                                            Top SQL needs to be purchased separately. To use this function, subscribe to Intelligent O&M first.

                                            +

                                            Procedure

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                            4. On the Instances page, click the DB instance name.
                                            5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                            6. Click the Top SQL tab.

                                              Top SQL needs to be purchased separately. To use this function, upgrade DBA Assistant first.

                                              -

                                            7. Click Subscribe. In the displayed dialog box, learn about Intelligent O&M functions and pricing.
                                            8. After subscribing to Intelligent O&M, view top SQL statements of your instance.
                                            9. You can view execution durations of the top SQL statements in the last 1 hour, last 3 hours, last 12 hours, or a custom time period (spanning no more than one day).
                                            -

                                            +

                                          7. Click Upgrade DBA Assistant. In the displayed dialog box, you can learn about the enhanced features and billing rules.
                                          8. After the upgrade is complete, view top SQL statements of your instance.
                                          9. View execution durations of the top SQL statements in the last 1 hour, last 3 hours, last 6 hours, last 12 hours, or a custom time range (spanning no more than one day).
                                          diff --git a/docs/rds/umn/rds_08_0032.html b/docs/rds/umn/rds_08_0032.html index 8b33ec963..d2faf18e8 100644 --- a/docs/rds/umn/rds_08_0032.html +++ b/docs/rds/umn/rds_08_0032.html @@ -6,7 +6,7 @@

                                          Constraints

                                          • You need to enable Collect All SQL Statements before using SQL Insights.
                                          • After Collect All SQL Statements is disabled, new SQL statements will not be collected anymore and the collected SQL data will be deleted.
                                          • If there is a buffer overrun, some data cannot be recorded.
                                          • Any SQL statement that exceeds 4,096 bytes will not be recorded by default.

                                            In RDS for MySQL 5.7.33.3 and later minor versions, you can set the rds_sql_tracer_reserve_big_records parameter to ON (which indicates that SQL statements containing more than 4,096 bytes are still recorded) on the Parameters page to remove this constraint. For details, see Modifying Parameters. RDS for MySQL 5.6 and 8.0 do not support this parameter.

                                          -

                                          Procedure

                                          1. Log in to the management console.
                                          2. Click in the upper left corner and select a region and a project.
                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                          4. On the Instances page, click the DB instance name.
                                          5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                          6. Click SQL Explorer and then SQL Insights.
                                          7. Click next to Collect All SQL Statements.

                                            To disable this function, click Log Settings in the upper right corner, toggle off the Collect All SQL Statements switch, and click OK.

                                            +

                                            Procedure

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                            4. On the Instances page, click the DB instance name.
                                            5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                            6. Click the SQL Insights tab.
                                            7. Click next to Collect All SQL Statements.

                                              To disable this function, click Log Settings in the upper right corner, toggle off the switch, and click OK.

                                              Collecting all SQL statements generates a performance loss of no more than 5%.

                                            8. Click Create Task. In the displayed dialog box, specify Time Range, Dimension, and other configuration items, and click OK.
                                            9. In the task list, click Details in the Operation column to view task details.
                                            diff --git a/docs/rds/umn/rds_08_0033.html b/docs/rds/umn/rds_08_0033.html index 1aeed7189..5f0eeb5ae 100644 --- a/docs/rds/umn/rds_08_0033.html +++ b/docs/rds/umn/rds_08_0033.html @@ -1,13 +1,13 @@

                                            Creating a SQL Throttling Rule

                                            -

                                            Scenarios

                                            You can create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better performance at high concurrency, SQL statements that meet the specified SQL type and keyword and exceed the maximum concurrency will not be executed.

                                            +

                                            Scenarios

                                            SQL throttling allows you to create rules to control concurrent execution of SQL statements by specifying SQL type, keywords, and maximum concurrency. To maintain better performance at high concurrency, SQL statements that meet the specified SQL type and keyword and exceed the maximum concurrency will not be executed.

                                            High SQL concurrency can be caused by the following factors:

                                            -
                                            • A sharp increase in requests: Concurrent SQL statements of a certain type surge due to cache penetration and abnormal calls.
                                            • Stacked slow queries: If a large number of SQL statements without indexes are called, many slow SQL statements will be generated, affecting services.
                                            +
                                            • A sharp increase in requests: Concurrent SQL statements of a certain type surge due to cache penetration and abnormal calls.
                                            • Slow query accumulation: If a large number of SQL statements without indexes are called, many slow SQL statements will be generated, affecting workloads.
                                            -

                                            Supported Versions

                                            Concurrency Control is available to the RDS for MySQL versions listed in Table 1.

                                            +

                                            Version Constraints

                                            SQL throttling is available to only the versions listed in Table 1.

                                            -
                                            Table 1 Supported versions

                                            Major Version

                                            +
                                            @@ -47,27 +47,78 @@
                                            Table 1 Version constraints on instance types

                                            Major Version

                                            Minor Version (Primary Instance)
                                            -

                                            In some versions, concurrency control rules are not applied to requests sent by user root. For details, see Table 2.

                                            +

                                            Table 2 lists the version constraints on built-in users and user root.

                                            -
                                            Table 2 Versions in which requests from root are not limited by concurrency control rules

                                            Major Version

                                            +
                                            - + + - - + + - - + - - + + + + + + + + + + + + + + + + + + + + + + + @@ -75,9 +126,10 @@

                                            To achieve better performance at high concurrency, you are advised to upgrade your DB instance to the latest minor version. For details about how to upgrade a minor version, see Upgrading a Minor Version.

                                            -

                                            Constraints

                                            • A maximum of 100 concurrency control rules can be configured.
                                            • Only SELECT, UPDATE, DELETE, and INSERT statements are supported for concurrency control.
                                            • INSERT statements are only supported for RDS for MySQL 5.7 (5.7.44.240100 or later) and 8.0 (8.0.32.240100 or later) for concurrency control. To use this function, contact customer service to apply for required permissions.
                                            • If a SQL statement matches multiple concurrency control rules, only the most recently added rule is applied.
                                            • SQL statements that have been executed before a concurrency control rule is added are not counted.
                                            • If the replication delay is too long, adding or deleting a concurrency control rule for a read replica does not take effect immediately.
                                            • Concurrency control rules are not applied to system tables.
                                            • Concurrency control rules are not applied to SQL statements not used for data query, such as select sleep(***);.
                                            • Concurrency control rules are not applied to stored procedures, triggers, or functions.
                                            • You can run the following SQL statement through DAS to view the execution of concurrency control rules: select * from information_schema.rds_sql_filter_info;
                                            • Too many concurrency control rules affect the database performance. Delete unnecessary rules after using them.
                                            • Concurrency control rules are not applied to system databases.
                                            +

                                            Constraints

                                            • A maximum of 100 SQL throttling rules can be configured.
                                            • Only SELECT, UPDATE, DELETE, and INSERT statements are supported for SQL throttling.
                                            +
                                            • INSERT statements are only supported for RDS for MySQL 5.7 (5.7.44.240100 or later) and 8.0 (8.0.32.240100 or later) for SQL throttling. To use this function, contact customer service to apply for required permissions.
                                            • If a SQL statement matches multiple SQL throttling rules, only the most recently added rule is applied.
                                            • SQL statements that have been executed before a SQL throttling rule is added are not counted.
                                            • If the replication delay is too long, adding or deleting a SQL throttling rule for a read replica does not take effect immediately.
                                            • SQL throttling rules are not applied to system tables.
                                            • SQL throttling rules are not applied to SQL statements not used for data query, such as select sleep(***);.
                                            • SQL throttling rules are not applied to stored procedures, triggers, or functions.
                                            • You can run the following SQL statement through DAS to view the execution of SQL throttling rules: select * from information_schema.rds_sql_filter_info;
                                            • Too many SQL throttling rules affect the database performance. Delete unnecessary rules after using them.
                                            • SQL throttling rules are not applied to system databases.
                                            • For instances whose kernel version is earlier than 5.6.51.4, 5.7.33.5, or 8.0.25.220700, SQL throttling rules are applied to all users. You are advised to include table names in keywords when configuring SQL throttling rules. Configuring only the SELECT keyword may impact the functionality.
                                            -

                                            Procedure

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                            4. On the Instances page, click the target DB instance name.
                                            5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                            6. Choose SQL Explorer > SQL Throttling.
                                            7. Toggle on the SQL throttling switch . SQL throttling rules take effect only after SQL throttling is enabled.
                                            8. Click Add Rule. Configure the parameters listed in Table 3.

                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance name.
                                              5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                              6. Click the SQL Throttling tab.
                                              7. Toggle on the SQL throttling switch . SQL throttling rules take effect only after SQL throttling is enabled.
                                              8. Click Add Rule. Configure the parameters listed in Table 3.

                                            Table 2 Version constraints on users

                                            Major Version

                                            Minor Version (Primary Instance)

                                            +

                                            Minor Version

                                            +

                                            Built-in User

                                            +

                                            Root User

                                            5.6

                                            +

                                            8.0

                                            ≥ 5.6.51.4

                                            +

                                            ≥ 8.0.28.231000

                                            +

                                            Not affected by throttling rules

                                            +

                                            Subject to throttling rules

                                            5.7

                                            +

                                            8.0.25.1 ≤ Version < 8.0.28.231000

                                            5.7.33.1 ≤ Version < 5.7.43.231000

                                            +

                                            Not affected by throttling rules

                                            +

                                            Not affected by throttling rules

                                            8.0

                                            +

                                            < 8.0.25.1

                                            8.0.25.1 ≤ Version < 8.0.28.231000

                                            +

                                            Subject to throttling rules

                                            +

                                            Subject to throttling rules

                                            +

                                            5.7

                                            +

                                            ≥ 5.7.43.231000

                                            +

                                            Not affected by throttling rules

                                            +

                                            Subject to throttling rules

                                            +

                                            5.7.33.1 ≤ Version < 5.7.43.231000

                                            +

                                            Not affected by throttling rules

                                            +

                                            Not affected by throttling rules

                                            +

                                            < 5.7.33.1

                                            +

                                            Subject to throttling rules

                                            +

                                            Subject to throttling rules

                                            +

                                            5.6

                                            +

                                            ≥ 5.6.51.4

                                            +

                                            Not affected by throttling rules

                                            +

                                            Not affected by throttling rules

                                            +

                                            < 5.6.51.4

                                            +

                                            Subject to throttling rules

                                            +

                                            Subject to throttling rules
                                            - - - @@ -113,7 +165,7 @@

                                          8. Confirm the settings and click OK.
                                            9. -

                                            Follow-up Operations

                                            To delete a concurrency control rule, locate it in the rule list and click Delete in the Operation column. In the displayed dialog box, click OK.

                                            +

                                            Follow-up Operations

                                            To delete a SQL throttling rule, locate it in the rule list and click Delete in the Operation column. In the displayed dialog box, click OK.

                                            diff --git a/docs/rds/umn/rds_08_0035.html b/docs/rds/umn/rds_08_0035.html index d25c149b8..b69010f81 100644 --- a/docs/rds/umn/rds_08_0035.html +++ b/docs/rds/umn/rds_08_0035.html @@ -4,32 +4,31 @@

                                            Scenarios

                                            You can start a diagnosis for your DB instance and subscribe to diagnosis reports.

                                            • Starting a Diagnosis: You can perform an overall health diagnosis on your instance and view details of the current and historical diagnosis reports.
                                            • Subscribing to Diagnosis Reports: Simple Message Notification (SMN) can send diagnosis exception reports to the preset email address so that you can learn about the overall health status of your instance in real time.
                                            -

                                            Starting a Diagnosis

                                            1. Log in to the management console.
                                            2. Click in the upper left corner and select a region and a project.
                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                            4. On the Instances page, click the DB instance name.
                                            5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                            6. Click the Daily Reports tab.
                                            7. Click Start Diagnosis. Select a time range for the diagnosis. The time span is within one day.

                                              If you want to be notified of risks through email, see Subscribing to Diagnosis Reports.

                                              +

                                              Starting a Diagnosis

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the DB instance name.
                                              5. In the navigation pane, choose Daily Reports under DBA Assistant.
                                              6. Click Start Diagnosis. Select a time range for the diagnosis. The time span is within one day.

                                                If you want to be notified of risks through email, see Subscribing to Diagnosis Reports.

                                              7. In the Diagnosis Dimensions area, click Slow SQL Analysis, All SQL Analysis, or Performance & Storage to view diagnosis report details.
                                              8. You can also view historical diagnosis reports or download a report to your local PC.

                                                • To view historical diagnosis reports, click View History in the upper right corner of the page.
                                                • To download a report to your local PC, click Download in the upper right corner of the page.

                                              -

                                              Subscribing to Diagnosis Reports

                                              1. On the Instances page, click the DB instance name.
                                              2. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                              3. Click the Daily Reports tab.
                                              4. In the upper right corner of the page, click Subscribe and set subscription parameters. For details about the parameters, see Table 1.

                                                Figure 1 Subscribe to Daily Report
                                                - -
                                            Table 3 Parameter description

                                            Parameter

                                            Description

                                            @@ -89,23 +141,23 @@

                                            There are four options: SELECT, UPDATE, DELETE, and INSERT.

                                            Keyword

                                            +

                                            Keyword Generation

                                            A maximum of 128 keywords (case-insensitive) are supported. You can specify keywords in either of the following ways:

                                            -
                                            • Enter keywords: Take select~a as an example. select and a are two keywords contained in a concurrency control rule. The keywords are separated by a tilde (~). In this example, the rule restricts the execution of only the SQL statements containing keywords select and a.
                                            • Generate keywords from a SQL statement: You can enter a SQL statement and then click Generate Keyword. The generated keywords are for reference only. Exercise caution when using them.
                                            +
                                            • Manually: Take select~a as an example. select and a are two keywords contained in a SQL throttling rule. The keywords are separated by a tilde (~). In this example, the rule restricts the execution of only the SQL statements containing keywords select and a.
                                            • Using SQL statements: You can enter a SQL statement and then click Generate Keyword. The generated keywords are for reference only. Exercise caution when using them.

                                            SQL statements match the keywords from first to last. For example, if one rule contains the keyword a~and~b, the statement *** a>1 and b>2 can match the keyword, but *** b>2 and a>1 cannot.

                                            Empty characters before and after each keyword will be ignored, for example, spaces, '\n', '\r', and '\t'.

                                            Max. Concurrency

                                            +

                                            Max. Concurrent Requests

                                            If the number of concurrent SQL statements matching the keyword exceeds this limit, the SQL statements will not be executed. The value ranges from 0ms to 1,000,000,000ms.

                                            Kill existing sessions that match this rule

                                            If this option is selected, all sessions generated by users subject to this concurrency control rule will be killed.

                                            -

                                            For details about the versions where user root is not subject to concurrency control rules, see Table 2.

                                            +

                                            If this option is selected, all sessions generated by users subject to this SQL throttling rule will be killed.

                                            +

                                            For details about the versions where user root is not subject to SQL throttling rules, see Version Constraints.
                                            Table 1 Subscription parameters

                                            Parameter

                                            +

                                            Subscribing to Diagnosis Reports

                                            1. On the Instances page, click the DB instance name.
                                            2. In the navigation pane, choose Daily Reports under DBA Assistant.
                                            3. In the upper right corner of the page, click Subscribe to Daily Reports and set subscription parameters. For details about the parameters, see Table 1.

                                              +

                                              - - - - - - - diff --git a/docs/rds/umn/rds_08_0037.html b/docs/rds/umn/rds_08_0037.html index 6b7dd0cdf..88b115875 100644 --- a/docs/rds/umn/rds_08_0037.html +++ b/docs/rds/umn/rds_08_0037.html @@ -3,7 +3,7 @@

                                              Function Overview

                                              Description

                                              DBA Assistant provides visualized database O&M and intelligent diagnosis for developers and database administrators (DBAs), making database O&M easy and efficient. By analyzing alarms, resources, health data, performance metrics, and storage usage, it helps users quickly locate faults and keep track of instance status.

                                              -

                                              Scenarios

                                              • Setting a slow session threshold can help you quickly identify abnormal sessions and kill the sessions when an exception occurs in your instance, so that your instance can recover quickly and ensure database availability.
                                              • If your DB instance is unstable due to a large number of concurrent SQL requests from new services, you can set concurrency control rules for SQL statements to limit concurrent SQL statements and ensure instance stability.
                                              • If your instance storage is full, you can learn about the storage usage and disk space distribution on the Storage Analysis page. You can enable storage autoscaling. When the available storage of your instance drops to the threshold, autoscaling is triggered. For details, see Storage Autoscaling.
                                              • You can configure auto flow control to limit active connections in high burst traffic or abnormal read/write scenarios to ensure the availability of core workloads.
                                              +

                                              Scenarios

                                              • Setting a slow session threshold can help you quickly identify abnormal sessions and kill the sessions when an exception occurs in your instance, so that your instance can recover quickly and ensure database availability.
                                              • If your DB instance is unstable due to a large number of concurrent SQL requests from new services, you can set SQL throttling rules for SQL statements to limit concurrent SQL statements and ensure instance stability.
                                              • If your instance storage is full, you can learn about the storage usage and disk space distribution on the Storage Analysis page. You can enable storage autoscaling. When the available storage of your instance drops to the threshold, autoscaling is triggered. For details, see Storage Autoscaling.
                                              • You can configure auto flow control to limit active connections in high burst traffic or abnormal read/write scenarios to ensure the availability of core workloads.

                                              Functions

                                              Table 1 lists the functions supported by DBA Assistant.

                                              @@ -17,35 +17,35 @@
                                              - - - - - @@ -57,9 +57,9 @@ - - diff --git a/docs/rds/umn/rds_08_0039.html b/docs/rds/umn/rds_08_0039.html index 1f3768a45..d88ada1ad 100644 --- a/docs/rds/umn/rds_08_0039.html +++ b/docs/rds/umn/rds_08_0039.html @@ -6,9 +6,8 @@

                                              Constraints

                                              • The snapshot of historical transactions only lists the transactions that are currently being executed. It does not include those that started and committed during a collection interval.
                                              • To collect historical transactions, enable Collect Slow Query Logs or Collect All SQL Statements first.
                                              • A maximum of 10,000 records generated in the past 7 days can be displayed.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target instance name.
                                              5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                              6. Click the Historical Transactions tab.
                                              7. In the upper part of the page, click Log Settings, enable Collect Slow Query Logs or Collect All SQL Statements, and click OK.
                                              8. Enable Collect Historical Transactions and view historical transactions.
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target instance name.
                                              5. In the navigation pane, choose Locks & Transactions under DBA Assistant.
                                              6. Click the Historical Transactions tab.
                                              7. Enable Collect Historical Transactions and view historical transactions.
                                              -

                                              diff --git a/docs/rds/umn/rds_09_0024.html b/docs/rds/umn/rds_09_0024.html index 7e66bd4d2..92099a9ab 100644 --- a/docs/rds/umn/rds_09_0024.html +++ b/docs/rds/umn/rds_09_0024.html @@ -5,7 +5,7 @@

                                              Constraints

                                              • If the DB instance status is Abnormal, the reboot may fail.
                                              • Rebooting a DB instance will cause service interruptions. During this period, the DB instance status is Rebooting.
                                              • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, locate the target DB instance, or click in the front of a DB instance and then locate the target read replica. Choose More > Reboot in the Operation column.

                                                Alternatively, click the target DB instance on the Instances page to go to the Overview page. Click and choose Reboot in the upper right corner.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, locate the target DB instance, or click in the front of a DB instance and then locate the target read replica. Choose More > Reboot in the Operation column.

                                                  Alternatively, click the target DB instance on the Instances page to go to the Summary page. Click and choose Reboot in the upper right corner.

                                                  For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

                                                5. In the displayed dialog box, select a scheduled time, and click Yes.
                                                6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
                                                diff --git a/docs/rds/umn/rds_09_0026.html b/docs/rds/umn/rds_09_0026.html index 8c347ad9d..16ebb52d2 100644 --- a/docs/rds/umn/rds_09_0026.html +++ b/docs/rds/umn/rds_09_0026.html @@ -3,7 +3,7 @@

                                                Changing a Security Group

                                                Scenarios

                                                This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target primary DB instance or read replica.
                                                5. On the Overview page, click Configure under Security Group.
                                                6. In the displayed dialog box, select one from the drop-down list.
                                                7. Click OK to submit the modification.
                                                8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Overview page to view the results.
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target primary DB instance or read replica.
                                                5. On the Summary page, click Configure under Security Group.
                                                6. In the displayed dialog box, select one from the drop-down list.
                                                7. Click OK to submit the modification.
                                                8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Summary page to view the results.
                                                diff --git a/docs/rds/umn/rds_09_0065.html b/docs/rds/umn/rds_09_0065.html index 3ba8e8314..21ca08e62 100644 --- a/docs/rds/umn/rds_09_0065.html +++ b/docs/rds/umn/rds_09_0065.html @@ -1,38 +1,38 @@

                                                rds_pg_sql_ccl

                                                -

                                                Introduction

                                                To prevent highly concurrent SQL statements that consume too many resources from causing instance instability, RDS for PostgreSQL provides rds_pg_sql_ccl, ccl is short for concurrent control. SQL statement concurrency control can ensure instance stability, optimize performance, and guarantee resources for critical tasks in the following scenarios:

                                                +

                                                Introduction

                                                To prevent highly concurrent SQL statements that consume too many resources from causing instance instability, RDS for PostgreSQL provides rds_pg_sql_ccl, ccl is short for concurrent control. SQL throttling can ensure instance stability, optimize performance, and guarantee resources for critical tasks in the following scenarios:

                                                • When workloads increase sharply, the instance stability is ensured by limiting the execution of a certain type of SQL statements.
                                                • When there are not enough resources, the success of core tasks is ensured by limiting the execution of other SQL statements to reduce resource consumption.
                                                -

                                                This extension provides two concurrency control methods:

                                                -
                                                • Method 1: It limits the number of SQL statements that can be executed at the same time. This number is specified by the rds_pg_sql_ccl.max_concurrent_sql parameter. If the parameter value is less than or equal to 0, the number is not limited.
                                                • Method 2: It limits the number of a certain type of SQL statements (with the same query ID) that can be executed at the same time. This number is specified by concurrency control rules. For details about concurrency control rules, see below.
                                                +

                                                This extension provides two SQL throttling methods:

                                                +
                                                • Method 1: It limits the number of SQL statements that can be executed at the same time. This number is specified by the rds_pg_sql_ccl.max_concurrent_sql parameter. If the parameter value is less than or equal to 0, the number is not limited.
                                                • Method 2: It limits the number of a certain type of SQL statements (with the same query ID) that can be executed at the same time. This number is specified by SQL throttling rules. For details about SQL throttling rules, see below.

                                                Supported Versions

                                                This extension is available to the latest minor versions of RDS for PostgreSQL 12.15, 13.11, 14.8, 15.4, 16.2, and above. You can run the following SQL statement to check whether your DB instance supports this extension:

                                                SELECT * FROM pg_available_extension_versions WHERE name = 'rds_pg_sql_ccl';

                                                If this extension is not supported, upgrade the minor version of your DB instance.

                                                To see more extensions supported by RDS for PostgreSQL, go to Supported Plugins.

                                                -

                                                Notes

                                                SQL statement concurrency control rules must be configured based on workloads and resource usage.

                                                +

                                                Notes

                                                SQL throttling rules must be configured based on workloads and resource usage.

                                                -

                                                Creating Rules

                                                1. In any given database, each rule must have a unique query ID, but rules in different databases can have the same query ID.
                                                2. A rule does not take effect immediately after being created. You need to call the enable_ccl_rule function to make it applied.
                                                3. The get_query_id function cannot obtain the query IDs of SQL statements using bind variables, and the add_ccl_rule_by_query function cannot limit the execution of such SQL statements.
                                                4. You can obtain the query ID of a SQL statement with bind variables using the pg_stat_statements extension. Then, you can use add_ccl_rule_by_queryid to create rules. For details, see "Concurrency Control for SQL Statements with Bind Variables".
                                                +

                                                Creating Rules

                                                1. In any given database, each rule must have a unique query ID, but rules in different databases can have the same query ID.
                                                2. A rule does not take effect immediately after being created. You need to call the enable_ccl_rule function to make it applied.
                                                3. The get_query_id function cannot obtain the query IDs of SQL statements using bind variables, and the add_ccl_rule_by_query function cannot limit the execution of such SQL statements.
                                                4. You can obtain the query ID of a SQL statement with bind variables using the pg_stat_statements extension. Then, you can use add_ccl_rule_by_queryid to create rules. For details, see "SQL throttling for Statements with Bind Variables".

                                                How Rules Take Effect

                                                1. Method 1 limits the number of SQL statements that can be concurrently executed. Rules creating using this method take effect preferentially. On the basis of method 1, you can use method 2 to further limit concurrent execution of a specific type of SQL statements.
                                                2. After an instance reboot, none of the rules are applied.
                                                3. Read replicas synchronize the rules of the primary instance and call the enable_ccl_rule function to make the rules apply.
                                                4. A rule is only applied to SQL statements executed after the rule was enabled.
                                                -

                                                Concurrency Control for SQL Statements Without Bind Variables

                                                Prerequisites:

                                                +

                                                SQL throttling for Statements Without Bind Variables

                                                Prerequisites:

                                                1. Install the kernel extension rds_pg_sql_ccl on the console or by running SQL statements.
                                                  SELECT control_extension ('create', 'rds_pg_sql_ccl');
                                                2. Set kernel parameters.
                                                  rds_pg_sql_ccl.enable_ccl = on

                                                Then, perform the following operations:

                                                -
                                                1. On the Instances page, click the instance name to go to the Overview page.
                                                2. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                                3. Choose SQL Explorer > Concurrency Control.
                                                4. Toggle on the concurrency control switch.
                                                5. Click Add Rule and configure required parameters.
                                                  • Locate the rule and click Enable in the Operation column to enable the rule.
                                                  • To disable a rule, click Disable.
                                                  • To delete a rule, click Delete. After a concurrency control rule that is enabled is deleted, the rule is not applied anymore.
                                                  +
                                                  1. On the Instances page, click the instance name to go to the Summary page.
                                                  2. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                                  3. Click the SQL Throttling tab.
                                                  4. Toggle on the SQL throttling switch . SQL throttling rules take effect only after SQL throttling is enabled.
                                                  5. Click Add Rule and configure required parameters.
                                                    • Locate the rule and click Enable in the Operation column to enable the rule.
                                                    • To disable a rule, click Disable.
                                                    • To delete a rule, click Delete. After a SQL throttling rule that is enabled is deleted, the rule is not applied anymore.
                                                -

                                                Concurrency Control for SQL Statements with Bind Variables

                                                Drivers such as JDBC support prepared statements. They precompile parameterized SQL statements and execute them after parameters are entered. In the pg_stat_statements view, the statements are displayed as bind variables. For SQL statements using bind variables, the query IDs calculated by the kernel are different from those of the same statements using actual parameter values. The concurrent execution of such statements cannot be limited by adding the statements.

                                                -

                                                Such SQL statements can only be limited by executing them first and then adding concurrency control rules.

                                                +

                                                SQL throttling for Statements with Bind Variables

                                                Drivers such as JDBC support prepared statements. They precompile parameterized SQL statements and execute them after parameters are entered. In the pg_stat_statements view, the statements are displayed as bind variables. For SQL statements using bind variables, the query IDs calculated by the kernel are different from those of the same statements using actual parameter values. The concurrent execution of such statements cannot be limited by adding the statements.

                                                +

                                                Such SQL statements can only be limited by executing them first and then adding SQL throttling rules.

                                                1. Execute a SQL statement with bind variables. In this way, the kernel calculates its query ID. An example of the JDBC-based prepared statement program is as follows:
                                                  String sql = "select pg_sleep(?);";
 PreparedStatement preparedStatement = conn.prepareStatement(sql);
 preparedStatement.setInt(1, 500);
 ResultSet resultSet = preparedStatement.executeQuery();
                                                2. Query the query ID of the SQL statement in the pg_stat_statements view.
                                                  select queryid from pg_stat_statements where query ilike '%SELECT pg_sleep%';
                                                  -
                                                3. Add a concurrency control rule based on the query ID.
                                                  select rds_pg_sql_ccl.add_ccl_rule_by_queryid($queryid);
                                                  +
                                                4. Add a SQL throttling rule based on the query ID.
                                                  select rds_pg_sql_ccl.add_ccl_rule_by_queryid($queryid);
                                                5. Enable the rule based on the return value (rule_id) of the previous SQL statement.
                                                  select rds_pg_sql_ccl.enable_ccl_rule($rule_id);
                                                6. Obtain all rules applied from the get_all_enabled_rule view provided by the extension.
                                                  select * from rds_pg_sql_ccl.get_all_enabled_rule;
                                                @@ -62,7 +62,7 @@ ResultSet resultSet = preparedStatement.executeQuery();
                                              - - - - - - - @@ -231,7 +231,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              max_concurrency int,

                                              max_wait int

                                              - - diff --git a/docs/rds/umn/rds_11_0006.html b/docs/rds/umn/rds_11_0006.html index 10f80a017..f1b5ee0cc 100644 --- a/docs/rds/umn/rds_11_0006.html +++ b/docs/rds/umn/rds_11_0006.html @@ -5,7 +5,7 @@

                                              Constraints

                                              • If the database service status is abnormal, you can forcibly reboot the DB instance, but this will interrupt uncommitted transactions.
                                              • Rebooting DB instances will cause service interruptions. During the reboot process, the DB instance status is Rebooting.
                                              • Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

                                                Alternatively, click the target DB instance on the Instances page to go to the Overview page. Click and choose Reboot in the upper right corner.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

                                                  Alternatively, click the target DB instance on the Instances page to go to the Summary page. Click and choose Reboot in the upper right corner.

                                                  For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

                                                5. In the displayed dialog box, select a reboot mode. If you select Forceful, select the checkbox before Confirm forcible reboot and click Yes.
                                                6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
                                                diff --git a/docs/rds/umn/rds_11_0015.html b/docs/rds/umn/rds_11_0015.html index d2c957bab..cfae2a122 100644 --- a/docs/rds/umn/rds_11_0015.html +++ b/docs/rds/umn/rds_11_0015.html @@ -1,7 +1,7 @@

                                                Managing a Read Replica

                                                -

                                                Entering the Management Interface Through a Read Replica

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Overview page.
                                                +

                                                Entering the Management Interface Through a Read Replica

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Summary page.

                                                Deleting a Read Replica

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
                                                diff --git a/docs/rds/umn/rds_11_0017.html b/docs/rds/umn/rds_11_0017.html index e959f272a..0128ded11 100644 --- a/docs/rds/umn/rds_11_0017.html +++ b/docs/rds/umn/rds_11_0017.html @@ -5,7 +5,7 @@

                                                Precautions

                                                Keep in mind the following notes on database proxies:
                                                • Before enabling database proxy, ensure that you have purchased an RDS for MySQL instance.
                                                • Both the primary instance and read replicas must be available.
                                                -

                                                Enabling a Single Proxy

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance. The Overview page is displayed.
                                                5. In the navigation pane on the left, choose Database Proxy.

                                                  Alternatively, in the Connectivity area on the Overview page, click Configure in the Read/Write Splitting Address field.

                                                  +

                                                  Enabling a Single Proxy

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                  4. On the Instances page, click the target DB instance. The Summary page is displayed.
                                                  5. In the navigation pane on the left, choose Database Proxy.

                                                    Alternatively, in the Connectivity area on the Summary page, click Configure in the Read/Write Splitting Address field.

                                                  6. On the displayed page, click Create Database Proxy.
                                                  7. Configure parameters and click Next.

                                              Table 1 Subscription parameters

                                              Parameter

                                              Description

                                              +

                                              Description

                                              Subscription

                                              +

                                              Subscription

                                              Select By topic or By email.

                                              +

                                              Select By topic or By email.

                                              Topics

                                              +

                                              Topics

                                              A topic is used to publish messages and subscribe to notifications. It serves as a message transmission channel between publishers and subscribers.

                                              +

                                              A topic is used to publish messages and subscribe to notifications. It serves as a message transmission channel between publishers and subscribers.

                                              Email Addresses

                                              +

                                              Email Addresses

                                              If you select By email for Subscription, you need to specify Email Addresses.

                                              +

                                              If you select By email for Subscription, you need to specify Email Addresses.

                                              An email will be sent to the specified email address only when risks are identified after a diagnosis is performed. You can enter up to 15 email addresses and separate each email address with a semicolon (;).

                                              Sessions

                                              The Sessions page displays slow sessions, active sessions, and total sessions. You can quickly filter slow sessions or active sessions by user, host IP address, or database name. Kill Session and Concurrency Control can be used for urgent instance recovery to ensure database availability.

                                              +

                                              It displays session statistics. You can quickly filter slow sessions or active sessions by user, host IP address, or database name. Kill Session and SQL Throttling can be used for urgent instance recovery to ensure database availability.

                                              Managing Real-Time Sessions

                                              Performance

                                              The Performance page displays key metrics of your instance and provides metric comparison between different days. You can keep track of metric changes and detect exceptions in a timely manner.

                                              +

                                              It displays key metrics of your instance and provides metric comparison between different days. You can keep track of metric changes and detect exceptions in a timely manner.

                                              Viewing Performance Metrics of a DB Instance

                                              Storage Analysis

                                              Storage occupied by data and logs and historical changes of storage usage are important for database performance. The Storage Analysis page displays storage overview and disk space distribution of your instance. In addition, DBA Assistant can estimate the available days of your storage based on historical data and intelligent algorithms, so that you can scale up storage in a timely manner. Scale, Abnormal Tables, Top 50 Databases, and Top 50 Tables are also available on this page.

                                              +

                                              Storage occupied by data and logs and historical changes of storage usage are important for database performance. DBA Assistant shows the storage summary and storage space usages of your instance. It estimates the available days of your storage based on historical data and intelligent algorithms, helping you scale up storage before it runs out. Top 50 Databases, and Top 50 Tables are also available on this page.

                                              Managing Storage Capacity

                                              Locks & Transactions

                                              The Locks & Transactions page displays metadata locks and InnoDB locks. You can manage blocked transactions, optimize your workloads, and reduce lock conflicts based on the lock information.

                                              +

                                              It analyzes metadata locks and InnoDB locks. You can manage blocked transactions using metadata lock views and InnoDB lock topologies to reduce lock conflicts.

                                              Managing Locks & Transactions

                                              Slow Query Log

                                              Displays slow queries within a specified time period. You can view top 5 slow query logs by user or IP address, sort statistics, and identify sources of slow SQL statements.

                                              +

                                              It displays slow queries within a specified time period. You can sort top slow queries by user or client IP address, view slow query statistics, and sort them by specific dimensions to identify the sources of slow SQL queries.

                                              Viewing Slow Query Logs of a DB Instance

                                              Concurrency Control

                                              +

                                              SQL Throttling

                                              Concurrency Control restricts the execution of SQL statements based on specified rules when there are SQL statements that cannot be optimized timely or a resource (for example, vCPU) bottleneck occurs.

                                              +

                                              SQL Throttling restricts the execution of SQL statements based on specified rules when there are SQL statements that cannot be optimized timely or a resource (for example, vCPU) bottleneck occurs.

                                              Creating a SQL Throttling Rule

                                              -

                                              Whether to enable a concurrency control rule.

                                              +

                                              Whether to enable a SQL throttling rule.

                                              rds_pg_sql_ccl.max_enabled_rules

                                              @@ -131,7 +131,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              ruleid

                                              Adds a concurrency control rule using SQL statements.

                                              +

                                              Adds a SQL throttling rule using SQL statements.

                                              3

                                              @@ -145,7 +145,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              ruleid

                                              Adds a concurrency control rule based on the query ID.

                                              +

                                              Adds a SQL throttling rule based on the query ID.

                                              5

                                              @@ -156,7 +156,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              bool

                                              Enables a concurrency control rule based on the rule ID.

                                              +

                                              Enables a SQL throttling rule based on the rule ID.

                                              6

                                              @@ -167,7 +167,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              bool

                                              Disables a concurrency control rule based on the rule ID.

                                              +

                                              Disables a SQL throttling rule based on the rule ID.

                                              7

                                              @@ -189,7 +189,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              void

                                              Deletes a concurrency control rule based on the rule ID.

                                              +

                                              Deletes a SQL throttling rule based on the rule ID.

                                              9

                                              @@ -202,7 +202,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              void

                                              Updates a concurrency control rule based on the rule ID.

                                              +

                                              Updates a SQL throttling rule based on the rule ID.

                                              Displays all concurrency control rules applied.

                                              +

                                              Displays all SQL throttling rules applied.

                                              2

                                              @@ -259,7 +259,7 @@ ResultSet resultSet = preparedStatement.executeQuery();

                                              create_time timestamptz,

                                              enabled bool

                                              Displays the concurrency control rules created for the current database (whether applied or not).

                                              +

                                              Displays the SQL throttling rules created for the current database (whether applied or not).
                                              @@ -51,7 +51,7 @@
                                              • Read/write splitting maintains database connectivity but splits read and write requests. If read/write splitting is enabled, an additional address called a read/write splitting address is provided. To use read/write splitting, switch your applications to this address.
                                              • Read/write splitting address: You can connect to databases through the read/write splitting address, with read and write requests distributed to different databases automatically.

                                                The read/write splitting address and the floating IP address of the primary DB instance are in the same VPC and subnet and are independent from each other.

                                              • Delay threshold: You can set the delay threshold after read/write splitting is enabled. For details, see Configuring the Delay Threshold and Routing Policy.
                                              • DB instances for load balancing: You can select DB instances for load balancing after read/write splitting is enabled.

                                            4. Confirm the database proxy configuration.

                                              • To modify the configuration, click Previous.
                                              • If there is no need to change the settings, click Submit.
                                              -

                                            5. View and manage the proxy on the Database Proxy page.

                                              You can view the read/write splitting address on the Overview page. Read and write requests can be split through the read/write splitting address.

                                              +

                                            6. View and manage the proxy on the Database Proxy page.

                                              You can view the read/write splitting address on the Summary page. Read and write requests can be split through the read/write splitting address.

                                              The read/write splitting address and the floating IP address of the DB instance are in the same VPC and subnet and are independent from each other.

                                              7. diff --git a/docs/rds/umn/rds_11_0019.html b/docs/rds/umn/rds_11_0019.html index 2ce53b0d1..9cda1c1ac 100644 --- a/docs/rds/umn/rds_11_0019.html +++ b/docs/rds/umn/rds_11_0019.html @@ -2,7 +2,7 @@

                                              Disabling Read/Write Splitting

                                              You can disable read/write splitting as required.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance. The Overview page is displayed.
                                              5. In the navigation pane on the left, choose Database Proxy.
                                              6. In the proxy instance area, click Delete Proxy. In the displayed dialog box, click OK.

                                                • If the database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address are interrupted. You need to switch your applications to the instance address.
                                                • After read/write splitting is disabled, read replicas are still be billed. You can release them if they are not required for your workloads anymore.
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance. The Summary page is displayed.
                                                5. In the navigation pane on the left, choose Database Proxy.
                                                6. In the proxy instance area, click Delete Proxy. In the displayed dialog box, click OK.

                                                  • If the database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting address are interrupted. You need to switch your applications to the instance address.
                                                  • After read/write splitting is disabled, read replicas are still be billed. You can release them if they are not required for your workloads anymore.

                                                diff --git a/docs/rds/umn/rds_11_0026.html b/docs/rds/umn/rds_11_0026.html index 09b4c55ed..0660d0534 100644 --- a/docs/rds/umn/rds_11_0026.html +++ b/docs/rds/umn/rds_11_0026.html @@ -9,7 +9,7 @@

                                                Procedure

                                                You can change the read/write splitting address for DB instances with read/write splitting enabled.

                                                -
                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance.
                                                5. In the Connectivity area on the Overview page, click Modify next to the Read/Write Splitting Address field.

                                                  Alternatively, click Database Proxy in the navigation pane on the left. On the displayed page, click Modify next to the Read/Write Splitting Address field.

                                                  +
                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                  4. On the Instances page, click the target DB instance.
                                                  5. In the Connectivity area on the Summary page, click Modify next to the Read/Write Splitting Address field.

                                                    Alternatively, click Database Proxy in the navigation pane on the left. On the displayed page, click Modify next to the Read/Write Splitting Address field.

                                                  6. In the displayed dialog box, enter a new address. Click OK.

                                                    In-use IP addresses cannot be used as read/write splitting addresses.

                                                diff --git a/docs/rds/umn/rds_11_0032.html b/docs/rds/umn/rds_11_0032.html index 657a74a15..cd5d8afc0 100644 --- a/docs/rds/umn/rds_11_0032.html +++ b/docs/rds/umn/rds_11_0032.html @@ -3,7 +3,7 @@

                                                Changing a Security Group

                                                Scenarios

                                                This section describes how to change the security group of a primary DB instance or read replica. For primary/standby DB instances, changing the security group of the primary DB instance will cause the security group of the standby DB instance to also be changed accordingly.

                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target primary DB instance or read replica.
                                                5. On the Overview page, click Configure under Security Group.
                                                6. In the displayed dialog box, select one from the drop-down list.
                                                7. Click OK to submit the modification.
                                                8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Overview page to view the results.
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target primary DB instance or read replica.
                                                5. On the Summary page, click Configure under Security Group.
                                                6. In the displayed dialog box, select one from the drop-down list.
                                                7. Click OK to submit the modification.
                                                8. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Summary page to view the results.
                                                diff --git a/docs/rds/umn/rds_11_0047.html b/docs/rds/umn/rds_11_0047.html index e3ba36193..7f5f92cbb 100644 --- a/docs/rds/umn/rds_11_0047.html +++ b/docs/rds/umn/rds_11_0047.html @@ -11,7 +11,7 @@

                                                Configuring Transaction Splitting

                                                Contact customer service to disable or enable transaction splitting at any time if necessary.

                                                Transaction splitting takes effect only for connections established after this feature is enabled or disabled.

                                                -
                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the primary instance name. The Overview page is displayed.
                                                5. In the navigation pane on the left, click Database Proxy.
                                                6. On the displayed page, click next to Transaction Splitting.
                                                7. In the displayed dialog box, click OK.
                                                +
                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the primary instance name. The Summary page is displayed.
                                                5. In the navigation pane on the left, click Database Proxy.
                                                6. On the displayed page, click next to Transaction Splitting.
                                                7. In the displayed dialog box, click OK.
                                                diff --git a/docs/rds/umn/rds_add_read_replica_pg.html b/docs/rds/umn/rds_add_read_replica_pg.html index f48d174c7..0d8ed5774 100644 --- a/docs/rds/umn/rds_add_read_replica_pg.html +++ b/docs/rds/umn/rds_add_read_replica_pg.html @@ -42,7 +42,7 @@
                                              + + + + + + - - - - - + + +
                                              Table 1 Parameter description

                                              Parameter

                                              Storage Type

                                              Determines the DB instance read/write speed. The higher the maximum throughput is, the higher the DB instance read/write speed can be.

                                              -
                                              • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                                              • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                                              +
                                              • Cloud SSD: cloud drives used to decouple storage from compute. The maximum throughput is 350 MB/s.
                                              • Extreme SSD: uses 25GE network and RDMA technologies to provide you with up to 1,000 MB/s throughput per disk and sub-millisecond latency.
                                              • Flexible SSD: decouples capacity from performance and allows for tailored IOPS and throughput for your business requirements. This storage type is ideal for mainstream interactive applications that require high performance and low latency.

                                              AZ

                                              @@ -73,6 +73,18 @@

                                              By default, storage space of a read replica is the same as that of the primary DB instance.

                                              IOPS

                                              +

                                              This parameter is required when the storage type is Flexible SSD.

                                              +

                                              The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                                              +

                                              Throughput

                                              +

                                              This parameter is required when the storage type is Flexible SSD.

                                              +

                                              The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                                              +

                                              Disk Encryption

                                              Enabling disk encryption enhances data security but reduces the database's read and write performance by 5%.

                                              diff --git a/docs/rds/umn/rds_change_database_port.html b/docs/rds/umn/rds_change_database_port.html index f617ef4cb..a3f7f1f80 100644 --- a/docs/rds/umn/rds_change_database_port.html +++ b/docs/rds/umn/rds_change_database_port.html @@ -6,12 +6,12 @@

                                              Constraints

                                              When the database port of a DB instance is being changed, you cannot:

                                              • Bind an EIP to the DB instance.
                                              • Delete the DB instance.
                                              • Create a backup for the DB instance.
                                              • Restore from backup data or from a specific point in time to the original DB instance.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                              5. On the Overview page, find Database Port and click Configure under it.

                                                A MySQL database can use ports 2100 to 9500.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                                5. On the Summary page, find Database Port and click Configure under it.

                                                  A MySQL database can use ports 2100 to 9500.

                                                  • In the displayed dialog box, enter a new port and click OK.
                                                    • If you change the database port of the primary DB instance, that of the standby DB instance will also be changed.
                                                    • This process takes 1-5 minutes.
                                                  • In the dialog box, click No to cancel the modification.
                                                  -

                                                6. View the results on the Overview page.
                                                +

                                              6. View the results on the Summary page.
                                              diff --git a/docs/rds/umn/rds_faq_0036.html b/docs/rds/umn/rds_faq_0036.html index 1ea3c31e2..205297a85 100644 --- a/docs/rds/umn/rds_faq_0036.html +++ b/docs/rds/umn/rds_faq_0036.html @@ -9,7 +9,7 @@

                                              Measures:

                                              • If a CPU or memory alarm is reported, you can scale up the vCPUs or memory by changing the DB instance class.

                                                For details, see Changing a DB Instance Class.

                                                -
                                              • If a storage space usage alarm is reported, you can:
                                                • Check the storage space consumption to see if any space can be freed up by deleting data from DB instances or by dumping the data to another system.
                                                • Scale up the storage space.

                                                  For details, see Scaling up Storage Space.

                                                  +
                                                • If a storage space usage alarm is reported, you can:
                                                  • Check the storage space consumption to see if any space can be freed up by deleting data from DB instances or by dumping the data to another system.
                                                  • Scale up the storage space.

                                                    For details, see Scaling Up Storage Space.

                                                diff --git a/docs/rds/umn/rds_faq_0050.html b/docs/rds/umn/rds_faq_0050.html index 6929b4732..0ff72914e 100644 --- a/docs/rds/umn/rds_faq_0050.html +++ b/docs/rds/umn/rds_faq_0050.html @@ -8,7 +8,7 @@

                                                Obtaining and Using JDBC

                                                Connection with the SSL Certificate

                                                Download the SSL certificate and verify the certificate before connecting to databases.

                                                -

                                                On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.

                                                +

                                                On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.

                                                1. Connect to the RDS PostgreSQL DB instance through JDBC.

                                                  jdbc:postgresql://<instance_ip>:<instance_port>/<database_name>?sslmode=verify-full&sslrootcert=<ca.pem>
                                                  @@ -20,7 +20,7 @@

                                              <instance_ip>

                                              If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Overview page of the DB instance to which you intend to connect.

                                              +

                                              If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Summary page of the DB instance to which you intend to connect.

                                              If you attempt to access the RDS DB instance through an EIP, set instance_ip to the EIP that has been bound to the DB instance.

                                              @@ -28,7 +28,7 @@

                                              <instance_port>

                                              Enter the database port displayed on the Overview page. Default value: 5432

                                              +

                                              Enter the database port displayed on the Summary page. Default value: 5432

                                              <database_name>

                                              @@ -98,7 +98,7 @@ public class MyConnTest {

                                              <instance_ip>

                                              If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Overview page of the DB instance to which you intend to connect.

                                              +

                                              If you attempt to access the RDS DB instance through an ECS, set instance_ip to the floating IP address displayed on the Summary page of the DB instance to which you intend to connect.

                                              If you attempt to access the RDS DB instance through an EIP, set instance_ip to the EIP that has been bound to the DB instance.

                                              @@ -106,7 +106,7 @@ public class MyConnTest {

                                              <instance_port>

                                              Enter the database port displayed on the Overview page. Default value: 5432

                                              +

                                              Enter the database port displayed on the Summary page. Default value: 5432

                                              <database_name>

                                              diff --git a/docs/rds/umn/rds_faq_0051.html b/docs/rds/umn/rds_faq_0051.html index 26f2046ed..1da242cb3 100644 --- a/docs/rds/umn/rds_faq_0051.html +++ b/docs/rds/umn/rds_faq_0051.html @@ -4,7 +4,7 @@

                                              When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:

                                              show status like '%ssl_server%';

                                              Update the root certificate to the latest version before it expires:

                                              -
                                              1. On the Instances page, click the target DB instance. In the Basic Information area on the Overview page, click Download in the SSL field to download the root certificate or certificate bundle.
                                              2. Reboot the DB instance for the new certificate to take effect.
                                              3. Connect to the DB instance using the new certificate or certificate bundle. +
                                                1. On the Instances page, click the target DB instance. Click Download under SSL to download the Certificate Download package, and extract the root certificate ca.pem and bundle ca-bundle.pem from the package.
                                                2. Reboot the DB instance for the new certificate to take effect.
                                                3. Connect to the DB instance using the new certificate or certificate bundle.

                                                  If a certificate is about to expire, replace it with an officially issued certificate to improve system security.

                                                diff --git a/docs/rds/umn/rds_faq_0065.html b/docs/rds/umn/rds_faq_0065.html index 5ace7b07d..f6833a313 100644 --- a/docs/rds/umn/rds_faq_0065.html +++ b/docs/rds/umn/rds_faq_0065.html @@ -5,7 +5,7 @@

                                                Failover

                                                Also called an unplanned handover. If the primary DB instance fails, the system will automatically switch to the standby DB instance within 5 minutes. No human intervention is required. The connection IP address remains unchanged. DB instances cannot be accessed during the failover. You need to configure automatic reconnections between applications and RDS DB instances to ensure near-continuous availability.

                                                Switchover (Manual)

                                                Also called a planned handover. When a DB instance is running properly, you can manually perform a primary/standby switchover if it is needed.

                                                -
                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance name to go to the Overview page.
                                                5. Under DB Instance Type, click Switch.

                                                  A primary/standby switchover may cause service interruption for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, perform a switchover during off-peak hours.

                                                  +
                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                  4. On the Instances page, click the target DB instance name to go to the Summary page.
                                                  5. Under DB Instance Type, click Switch.

                                                    A primary/standby switchover may cause service interruption for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, perform a switchover during off-peak hours.

                                                  6. In the displayed dialog box, click Yes to switch between the primary and standby DB instances.

                                                    If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

                                                  7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

                                                    • During the switchover process, the DB instance status is Switchover in progress.
                                                    • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is complete, the DB instance status will become Available
                                                    diff --git a/docs/rds/umn/rds_faq_0076.html b/docs/rds/umn/rds_faq_0076.html index 8cf1b616d..1d7aabb1d 100644 --- a/docs/rds/umn/rds_faq_0076.html +++ b/docs/rds/umn/rds_faq_0076.html @@ -1,7 +1,10 @@ -

                                                    Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?

                                                    -

                                                    No. After an RDS DB instance is created, the storage type cannot be changed.

                                                    +

                                                    Can I Change the Storage Type of an RDS DB Instance?

                                                    +

                                                    Yes. After an RDS DB instance is created, you can change its storage type.

                                                    +

                                                    For RDS for MySQL instances, see Changing a Storage Type.

                                                    +

                                                    For RDS for PostgreSQL instances, see Changing a Storage Type.

                                                    +

                                                    For RDS for SQL Server instances, see Changing a Storage Type.

                                                    diff --git a/docs/rds/umn/rds_faq_0100.html b/docs/rds/umn/rds_faq_0100.html index 3f7d4d1f7..061faf16f 100644 --- a/docs/rds/umn/rds_faq_0100.html +++ b/docs/rds/umn/rds_faq_0100.html @@ -7,7 +7,7 @@
                                                    • Check whether the IP address and port are correct.

                                                      Use a colon to separate the IP address and port.

                                                    • Check whether the RDS service is running properly.
                                                    • Check whether the username and password are correct. You can reset the password.
                                                    • Reboot the RDS DB instance and check whether it can be connected through an ECS.
                                                    -

                                                    Solution

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target DB instance. On the Connectivity & Security and Backups & Restorations pages, check connection and backup information.
                                                    5. On the Overview page, check the administrator.
                                                    6. Download an SQL Server Management Studio installation package and install it on an ECS.
                                                    7. Connect to the RDS DB instance through an ECS.
                                                    +

                                                    Solution

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target DB instance. On the Connectivity & Security and Backups & Restorations pages, check connection and backup information.
                                                    5. On the Summary page, check the administrator.
                                                    6. Download an SQL Server Management Studio installation package and install it on an ECS.
                                                    7. Connect to the RDS DB instance through an ECS.
                                                    diff --git a/docs/rds/umn/rds_faq_0119.html b/docs/rds/umn/rds_faq_0119.html index a78d95292..d5dcf7975 100644 --- a/docs/rds/umn/rds_faq_0119.html +++ b/docs/rds/umn/rds_faq_0119.html @@ -1,7 +1,7 @@

                                                    Does RDS for PostgreSQL Support the test_decoding Plugin?

                                                    -

                                                    PostgreSQL 12 supports test_decoding. For more information about test_decoding, see test_decoding introduction.

                                                    +

                                                    For more information about test_decoding, see test_decoding introduction.

                                                    To use test_decoding, set wal_level to logical.

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target DB instance.
                                                    5. In the navigation pane on the left, choose Parameters. On the Parameters tab page, locate wal_level and change its value to logical.
                                                    6. Click Save. In the displayed dialog box, click Yes.
                                                    diff --git a/docs/rds/umn/rds_faq_0144.html b/docs/rds/umn/rds_faq_0144.html index c66b5cf71..22b1abf39 100644 --- a/docs/rds/umn/rds_faq_0144.html +++ b/docs/rds/umn/rds_faq_0144.html @@ -8,7 +8,7 @@
                                                  8. What Is the RDS DB Instance Storage Configuration?
                                                    9. -
                                                  9. Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?
                                                    +
                                                  10. Can I Change the Storage Type of an RDS DB Instance?
                                                  11. What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?
                                                    12. diff --git a/docs/rds/umn/rds_history_0008.html b/docs/rds/umn/rds_history_0008.html index 71507324a..c8fb8ad04 100644 --- a/docs/rds/umn/rds_history_0008.html +++ b/docs/rds/umn/rds_history_0008.html @@ -8,7 +8,13 @@

                                              2025-10-10

                                              +

                                              2026-02-10

                                              +

                                              Modified the following content:

                                              +

                                              Supported the Flexible SSD storage type (General Purpose SSD V2), see DB Instance Storage Types.

                                              +

                                              2025-10-10

                                              Modified the following content:

                                              Added Changing a Storage Type.

                                              @@ -36,7 +42,7 @@

                                              2024-10-12

                                              Modified the following content:

                                              - +

                                              2024-08-26

                                              @@ -196,7 +202,7 @@

                                              2019-09-12

                                              Modified the following content:

                                              -

                                              Modified the content in the following sections: Comparison Between RDS and Self-Built Databases, Downloading a Backup File, Applying a Parameter Template, Key Operations Supported by CTS, Scaling up Storage Space, Rebooting DB Instances or Read Replicas, Restoring from Backup Files to RDS for PostgreSQL, Configuring Displayed Metrics, Key Operations Supported by CTS, Installing and Uninstalling a Plugin Using SQL Commands, Configuring Displayed Metrics, Key Operations Supported by CTS, Does RDS Support Cross-AZ High Availability?, and Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?

                                              +

                                              Modified the content in the following sections: Comparison Between RDS and Self-Built Databases, Downloading a Backup File, Applying a Parameter Template, Key Operations Supported by CTS, Scaling Up Storage Space, Rebooting DB Instances or Read Replicas, Restoring from Backup Files to RDS for PostgreSQL, Configuring Displayed Metrics, Key Operations Supported by CTS, Installing and Uninstalling a Plugin Using SQL Commands, Configuring Displayed Metrics, Key Operations Supported by CTS, Does RDS Support Cross-AZ High Availability?, and Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?

                                              2019-08-15

                                              @@ -231,7 +237,7 @@

                                              2019-02-25

                                              Modified the following content:

                                              -
                                              • Added the description in section Exporting a Parameter Template: An exported parameter group has initially a blank change history.
                                              • Supported the file name with a maximum of 81 characters when exporting a parameter group to a file in section Exporting a Parameter Template.
                                              • Added the description in the scenario in section Viewing Parameter Change History: An exported or custom parameter group has initially a blank change history.
                                              • Added the description in section Scaling up Storage Space: The DB instance is in Scaling up state when its storage space is being scaled up. For Microsoft SQL Server DB instances, backups cannot be created during the scale-up process. For MySQL and PostgreSQL DB instances, backup creation is not affected.
                                              +
                                              • Added the description in section Exporting a Parameter Template: An exported parameter group has initially a blank change history.
                                              • Supported the file name with a maximum of 81 characters when exporting a parameter group to a file in section Exporting a Parameter Template.
                                              • Added the description in the scenario in section Viewing Parameter Change History: An exported or custom parameter group has initially a blank change history.
                                              • Added the description in section Scaling Up Storage Space: The DB instance is in Scaling up state when its storage space is being scaled up. For Microsoft SQL Server DB instances, backups cannot be created during the scale-up process. For MySQL and PostgreSQL DB instances, backup creation is not affected.

                                              2019-02-15

                                              diff --git a/docs/rds/umn/rds_modify_availability.html b/docs/rds/umn/rds_modify_availability.html index d8ecd9877..8a669d033 100644 --- a/docs/rds/umn/rds_modify_availability.html +++ b/docs/rds/umn/rds_modify_availability.html @@ -4,7 +4,7 @@

                                              Scenarios

                                              You can configure the failover priority for reliability or for availability, depending on your service requirements.

                                              • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
                                              • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the primary instance name.
                                              5. On the displayed Overview page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                              6. View the results on the Overview page.
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the primary instance name.
                                              5. On the displayed Summary page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                              6. View the results on the Summary page.
                                              diff --git a/docs/rds/umn/rds_modify_instance_name.html b/docs/rds/umn/rds_modify_instance_name.html index bf3458d40..6c56e012f 100644 --- a/docs/rds/umn/rds_modify_instance_name.html +++ b/docs/rds/umn/rds_modify_instance_name.html @@ -3,10 +3,10 @@

                                              Changing a DB Instance Name

                                              Scenarios

                                              You can change the name of a primary DB instance or read replica.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to edit the DB instance name.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                  Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to edit the DB instance name.

                                                  The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

                                                  • To submit the change, click .
                                                  • To cancel the change, click .
                                                  -

                                                5. View the results on the Overview page.
                                                +

                                              5. View the results on the Summary page.
                                              diff --git a/docs/rds/umn/rds_mysql_0001.html b/docs/rds/umn/rds_mysql_0001.html index 2b9fa3cc8..6fb02256d 100644 --- a/docs/rds/umn/rds_mysql_0001.html +++ b/docs/rds/umn/rds_mysql_0001.html @@ -8,11 +8,11 @@
                                              • If SSL is disabled (default), use a non-SSL connection.
                                              • If SSL is enabled, use an SSL connection. SSL encrypts connections to the instance, making in-transit data more secure.

                                              Constraints

                                              Enabling or disabling SSL will cause instances to reboot and interrupt connections. Exercise caution when performing this operation.

                                              -

                                              Enabling SSL

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance.
                                              5. On the Overview page, find SSL and click Enable.

                                                Alternatively, in the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, click in the SSL field.

                                                -

                                              6. In the displayed dialog box, click OK.
                                              7. After a while, check the SSL status on the Overview page. It is enabled.
                                              +

                                              Enabling SSL

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance.
                                              5. On the Summary page, find SSL and click Enable.

                                                Alternatively, in the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, click in the SSL field.

                                                +

                                              6. In the displayed dialog box, click OK.
                                              7. After a while, check the SSL status on the Summary page. It is enabled.
                                              -

                                              Disabling SSL

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance.
                                              5. On the Overview page, find SSL and click Disable.

                                                Alternatively, in the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, click in the SSL field.

                                                -

                                              6. In the displayed dialog box, click OK.
                                              7. After a while, check the SSL status on the Overview page. It is disabled.
                                              +

                                              Disabling SSL

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance.
                                              5. On the Summary page, find SSL and click Disable.

                                                Alternatively, in the navigation pane on the left, choose Connectivity & Security. In the Connection Information area, click in the SSL field.

                                                +

                                              6. In the displayed dialog box, click OK.
                                              7. After a while, check the SSL status on the Summary page. It is disabled.
                                              diff --git a/docs/rds/umn/rds_pg_05_0001.html b/docs/rds/umn/rds_pg_05_0001.html index f1db37c81..a389d4f4e 100644 --- a/docs/rds/umn/rds_pg_05_0001.html +++ b/docs/rds/umn/rds_pg_05_0001.html @@ -18,7 +18,7 @@
                                            7. Changing a DB Instance Class
                                              8. -
                                            8. Scaling up Storage Space
                                              +
                                            9. Scaling Up Storage Space
                                            10. Changing a Storage Type
                                              11. diff --git a/docs/rds/umn/rds_pg_05_0003.html b/docs/rds/umn/rds_pg_05_0003.html index 7d6fe27fa..82fbe035a 100644 --- a/docs/rds/umn/rds_pg_05_0003.html +++ b/docs/rds/umn/rds_pg_05_0003.html @@ -7,7 +7,7 @@

                                              Constraints

                                              • The minor version cannot be upgraded for instances with abnormal nodes.
                                              • The upgrade will be performed immediately upon the submission of your request. Delayed upgrade of minor versions is not supported.
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the primary instance name to go to the Overview page.
                                              5. Under DB Engine Version, click Upgrade Minor Version.
                                              6. In the displayed dialog box, click OK.

                                                RDS upgrades the minor version to the latest version immediately.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the primary instance name to go to the Summary page.
                                                5. Under DB Engine Version, click Upgrade Minor Version.
                                                6. In the displayed dialog box, click OK.

                                                  RDS upgrades the minor version to the latest version immediately.

                                              diff --git a/docs/rds/umn/rds_pg_05_0004.html b/docs/rds/umn/rds_pg_05_0004.html index 5819f9f05..fddeb6fd9 100644 --- a/docs/rds/umn/rds_pg_05_0004.html +++ b/docs/rds/umn/rds_pg_05_0004.html @@ -4,7 +4,7 @@

                                              Scenarios

                                              RDS for PostgreSQL allows you to upgrade the major version of your DB instance in either of the following methods:

                                              • Upgrade without cutover: You can use it to test service compatibility of a new version. Upgrading a major version may cause service compatibility issues. A compatibility test is strongly recommended. After the test is passed, perform an upgrade in cutover mode. An upgrade without service cutover will not affect the original instance.
                                              • Upgrade with cutover: During an upgrade, the original instance is set to read-only and services are interrupted for minutes. After the upgrade is complete, the original and new instances automatically exchange their virtual IP addresses and the application connection will be switched to the new instance. No changes need to be made to your application.
                                              -

                                              Constraints

                                              • Major version upgrades are available to the following versions:
                                                • RDS for PostgreSQL 12: 12.7 or later
                                                • RDS for PostgreSQL 13: 13.3 or later
                                                • RDS for PostgreSQL 14: 14.4 or later
                                                • RDS for PostgreSQL 15: 15.4 or later
                                                • RDS for PostgreSQL 16
                                                • RDS for PostgreSQL 17
                                                +

                                                Constraints

                                                • Major version upgrades are available to the following source versions:
                                                  • RDS for PostgreSQL 12: 12.7 or later
                                                  • RDS for PostgreSQL 13: 13.3 or later
                                                  • RDS for PostgreSQL 14: 14.4 or later
                                                  • RDS for PostgreSQL 15: 15.4 or later
                                                  • RDS for PostgreSQL 16
                                                  • RDS for PostgreSQL 17
                                                • Due to OS restrictions, some instances do not support major version upgrades. To learn which versions your instance can be upgraded to, see the list of available versions on the Major Version Upgrade page.
                                                • DR instances do not support major version upgrades.
                                                • Before a major version upgrade, perform an upgrade check. If there is no successful upgrade check in the validity period, a major version upgrade is not allowed.

                                                Extensions Unsupported for Major Version Upgrades

                                                If any extension listed in Table 1 is detected in the upgrade path during a major version upgrade pre-check, uninstall the extension before the upgrade is performed and reinstall it after the upgrade is complete. If you perform the upgrade without removing this extension, the upgrade will fail, or the extension cannot be used after the instance is upgraded.

                                                diff --git a/docs/rds/umn/rds_pg_05_0024.html b/docs/rds/umn/rds_pg_05_0024.html index 428101fc0..76b014938 100644 --- a/docs/rds/umn/rds_pg_05_0024.html +++ b/docs/rds/umn/rds_pg_05_0024.html @@ -9,7 +9,7 @@

                                                Changing a Floating IP Address

                                                You can change the floating IP address of an existing DB instance.

                                                -
                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance name to go to the Overview page.
                                                5. Under Floating IP Address, click Configure.
                                                6. In the displayed dialog box, enter a new floating IP address and click OK.

                                                  In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

                                                  +
                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                  4. On the Instances page, click the target DB instance name to go to the Summary page.
                                                  5. Under Floating IP Address, click Configure.
                                                  6. In the displayed dialog box, enter a new floating IP address and click OK.

                                                    In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

                                              diff --git a/docs/rds/umn/rds_pg_05_0026.html b/docs/rds/umn/rds_pg_05_0026.html index 58c882edb..f6c9a0bb4 100644 --- a/docs/rds/umn/rds_pg_05_0026.html +++ b/docs/rds/umn/rds_pg_05_0026.html @@ -2,7 +2,7 @@

                                              Changing a Private Domain Name

                                              You can change the private domain name of your DB instance and connect to the instance using the new domain name.

                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. Click in the upper left corner and select a region and a project.
                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                              4. On the Instances page, click the target DB instance name to go to the Overview page.
                                              5. Under Private Domain Name, click Configure.
                                              6. In the displayed dialog box, enter a new private domain name. Click OK.

                                                • Only the prefix of a private domain name can be modified.
                                                • The prefix of a private domain name can contain 8 to 63 characters, and can include only letters and digits.
                                                • The new private domain name must be different from the existing ones.
                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance name to go to the Summary page.
                                                5. Under Private Domain Name, click Configure.
                                                6. In the displayed dialog box, enter a new private domain name. Click OK.

                                                  • Only the prefix of a private domain name can be modified.
                                                  • The prefix of a private domain name can contain 8 to 63 characters, and can include only letters and digits.
                                                  • The new private domain name must be different from the existing ones.

                                                diff --git a/docs/rds/umn/rds_pg_05_0038.html b/docs/rds/umn/rds_pg_05_0038.html index e4e26e363..df4e99f7a 100644 --- a/docs/rds/umn/rds_pg_05_0038.html +++ b/docs/rds/umn/rds_pg_05_0038.html @@ -5,7 +5,7 @@

                                                Precautions

                                                • During the maintenance window, the DB instance will be intermittently disconnected for one or two times. Ensure that your applications support automatic reconnection.
                                                -

                                                Procedure

                                                1. Log in to the management console.
                                                2. Click in the upper left corner and select a region and a project.
                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                4. On the Instances page, click the target DB instance name to go to the Overview page. Under Maintenance Window, click Configure.
                                                5. In the displayed dialog box, select a maintenance window and click OK.

                                                  Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                                                  +

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region and a project.
                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                  4. On the Instances page, click the target DB instance name to go to the Summary page. Under Maintenance Window, click Configure.
                                                  5. In the displayed dialog box, select a maintenance window and click OK.

                                                    Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                                                  diff --git a/docs/rds/umn/rds_pg_05_0039.html b/docs/rds/umn/rds_pg_05_0039.html index 67e087cd2..be37f652d 100644 --- a/docs/rds/umn/rds_pg_05_0039.html +++ b/docs/rds/umn/rds_pg_05_0039.html @@ -6,7 +6,7 @@

                                                  Constraints

                                                  • The maximum allowed storage is 4,000 GB.
                                                  • For a primary/standby DB instance, autoscaling the storage for the primary node will also autoscale the storage for the standby node.
                                                  • Storage autoscaling is unavailable when the DB instance is in any of the following statuses: changing instance class, upgrading a minor version, migrating the standby DB instance, and rebooting.
                                                  -

                                                  Procedure

                                                  1. Log in to the management console.
                                                  2. Click in the upper left corner and select a region.
                                                  3. Click Service List. Under Database, click Relational Database Service.
                                                  4. On the Instances page, click the target DB instance or read replica name (click in front of a DB instance to locate the read replica) to go to the Overview page.
                                                  5. In the Storage & Backup area, toggle on the Storage Autoscaling switch.
                                                  6. In the displayed dialog box, set the following parameters:

                                                    +

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region.
                                                    3. Click Service List. Under Database, click Relational Database Service.
                                                    4. On the Instances page, click the target DB instance or read replica name (click in front of a DB instance to locate the read replica) to go to the Summary page.
                                                    5. In the Storage & Backup area, toggle on the Storage Autoscaling switch.
                                                    6. In the displayed dialog box, set the following parameters:

                                                      - - - - - + + + + - - - - - - + + +
                                                      Table 1 Parameter description

                                                      Parameter

                                                      Description

                                                      diff --git a/docs/rds/umn/rds_pg_05_0060.html b/docs/rds/umn/rds_pg_05_0060.html index 603eff192..2cc386c58 100644 --- a/docs/rds/umn/rds_pg_05_0060.html +++ b/docs/rds/umn/rds_pg_05_0060.html @@ -5,7 +5,7 @@
                                                      • DDL operations and scheduled events will be suspended during migration. To prevent service interruption, perform the migration during off-peak hours.
                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, locate the target DB instance and choose More > Migrate Standby Instance to Another AZ in the Operation column.
                                                      5. On the displayed page, select a target AZ and click Submit.
                                                      6. After the migration is complete, you can view and manage the DB instance on the Instances page.

                                                        • During the migration process, the DB instance status is Migrating standby DB instance. You can view the progress on the Task Center page. For details, see Task Center.
                                                        • In the upper right corner of the DB instance list, click to refresh the list. After the migration is complete, the DB instance status will become Available.
                                                        • On the Overview page, find AZ and check the AZ hosting the standby DB instance.
                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and choose More > Migrate Standby Instance to Another AZ in the Operation column.
                                                        5. On the displayed page, select a target AZ and click Submit.
                                                        6. After the migration is complete, you can view and manage the DB instance on the Instances page.

                                                          • During the migration process, the DB instance status is Migrating standby DB instance. You can view the progress on the Task Center page. For details, see Task Center.
                                                          • In the upper right corner of the DB instance list, click to refresh the list. After the migration is complete, the DB instance status will become Available.
                                                          • On the Summary page, find AZ and check the AZ hosting the standby DB instance.

                                                        diff --git a/docs/rds/umn/rds_pg_05_0084.html b/docs/rds/umn/rds_pg_05_0084.html index fc5126eed..9172181d3 100644 --- a/docs/rds/umn/rds_pg_05_0084.html +++ b/docs/rds/umn/rds_pg_05_0084.html @@ -2,12 +2,75 @@

                                                        Changing a Storage Type

                                                        Scenarios

                                                        If the storage type of your RDS DB instance does not match your workloads, you can change it as needed.

                                                        +

                                                        For details about storage types, see DB Instance Storage Types.

                                                        Constraints

                                                        • If the storage type of a read replica is different from that of its associated DB instance, the data synchronization may be affected. Make sure that the storage type of the read replica has always same or faster than the DB instance.
                                                        -
                                                        • During the storage type change, operations such as changing the instance class and scaling up storage space cannot be performed on the instance.
                                                        • Changing the storage type may affect the disk performance, so you need to change the type during off-peak hours.
                                                        • Changing the storage type may take several minutes, hours, or even days. The time required depends on the throughput, storage space, and original storage type. This operation cannot be paused.
                                                        • In rare cases, the change may fail due to resource problems. If this happens, you are advised to perform the change again.
                                                        +
                                                        • During the storage type change, operations such as changing the instance class and scaling up storage space cannot be performed on the instance.
                                                        • Changing the storage type may affect the disk performance, so you need to change the type during off-peak hours.
                                                        • Changing the storage type may take several minutes, hours, or even days. The time required depends on the throughput, storage space, and original storage type. This operation cannot be paused.
                                                        • In rare cases, the change may fail due to resource problems. If this happens, you are advised to perform the change again.
                                                        • The following table lists the storage types that can be changed. +
                                                          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                          Table 1 Storage types that can be changed

                                                          Instance Type

                                                          +

                                                          Original Storage Type

                                                          +

                                                          Target Storage Type

                                                          +

                                                          Single

                                                          +

                                                          Cloud SSD

                                                          +

                                                          Flexible SSD

                                                          +

                                                          Flexible SSD

                                                          +

                                                          Cloud SSD

                                                          +

                                                          Read Replica

                                                          +

                                                          Cloud SSD

                                                          +

                                                          Extreme SSD or Flexible SSD

                                                          +

                                                          Extreme SSD

                                                          +

                                                          Cloud SSD or Flexible SSD

                                                          +

                                                          Flexible SSD

                                                          +

                                                          Cloud SSD or Extreme SSD

                                                          +

                                                          Primary/Standby

                                                          +

                                                          Cloud SSD

                                                          +

                                                          Extreme SSD or Flexible SSD

                                                          +

                                                          Extreme SSD

                                                          +

                                                          Cloud SSD or Flexible SSD

                                                          +

                                                          Flexible SSD

                                                          +

                                                          Cloud SSD or Extreme SSD

                                                          +
                                                          -

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                            Alternatively, click the target DB instance to go to the Overview page. Under Instance Class, click Configure.

                                                            -

                                                          5. On the displayed page, select a new storage type and click Next.
                                                          6. Confirm the new storage type. Click Submit.
                                                          7. Check the results.

                                                            Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Overview page.

                                                            +
                                                        +
                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                          Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

                                                          +

                                                        5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

                                                          If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

                                                          +
                                                          • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

                                                            This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                                                            +
                                                          • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

                                                            This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                                                            +
                                                          +

                                                        6. Confirm the configurations and Click Submit.
                                                        7. Check the results.

                                                          Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.

                                                        diff --git a/docs/rds/umn/rds_pg_08_0025.html b/docs/rds/umn/rds_pg_08_0025.html index fc56fb427..4bd1f3515 100644 --- a/docs/rds/umn/rds_pg_08_0025.html +++ b/docs/rds/umn/rds_pg_08_0025.html @@ -1,8 +1,8 @@

                                                        Introduction to Instance Overview

                                                        -

                                                        On the Overview page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. DBA Assistant diagnoses instance health using operational data analytics and intelligent algorithms, and provides you with solutions and suggestions for handling detected exceptions.

                                                        -

                                                        Functions

                                                        Table 1 lists the functions provided on the Overview page.

                                                        +

                                                        On the Summary page, you can get knowledge of the overall status of your RDS for PostgreSQL instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. DBA Assistant diagnoses instance health using operational data analytics and intelligent algorithms, and provides you with solutions and suggestions for handling detected exceptions.

                                                        +

                                                        Functions

                                                        Table 1 lists the functions provided on the Summary page.

                                                        @@ -43,7 +43,7 @@
                                                        Table 1 Function description

                                                        Function

                                                        -

                                                        Instance Information

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the target instance name to go to the Overview page.
                                                        5. In the Instance Information area, check the instance information and modify the instance as required.
                                                        +

                                                        Instance Information

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the target instance name to go to the Summary page.
                                                        5. In the Instance Information area, check the instance information and modify the instance as required.

                                                        Alarms

                                                        In the Alarms area, check alarm information of your instance.

                                                        Based on the configured alarm rules, you can see active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.

                                                        diff --git a/docs/rds/umn/rds_pg_08_0026.html b/docs/rds/umn/rds_pg_08_0026.html index b17e7045e..c94918af1 100644 --- a/docs/rds/umn/rds_pg_08_0026.html +++ b/docs/rds/umn/rds_pg_08_0026.html @@ -1,14 +1,16 @@

                                                        Managing Real-Time Sessions

                                                        -

                                                        Scenarios

                                                        You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, and database. Sessions can be killed for urgent instance recovery to ensure database availability.

                                                        +

                                                        Scenarios

                                                        You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, and database.

                                                        +

                                                        Sessions can be killed for urgent instance recovery to ensure database availability. If the maximum number of connections for an instance has been reached and the instance cannot be logged in to, you can view and kill unnecessary sessions.

                                                        Precautions

                                                        Killing a session may cause the application to disconnect from the instance. Your application should be able to reconnect to the instance.

                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the target instance name.
                                                        5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                                        6. Click the Sessions tab. You can perform the following operations on this tab page:

                                                          • Viewing session statistics

                                                            In the session statistics area, you can view the session summary and session statistics by user, source, and database.

                                                            +

                                                            Constraints

                                                            • Do not kill sessions unless you really need to. All your kill operations will be logged.
                                                            • Sessions of sensitive users such rdsAdmin, rdsBackup, rdsMetric, and rdsRepl, and sessions whose username is null cannot be killed.
                                                            • You may fail to refresh the session list if your instance has a heavy load. Minimize the resources occupied by the emergency channel. Wait a few seconds and try again.
                                                            • If the CPU usage reaches 100%, requests to kill sessions may fail. You may have to try more than once.
                                                            +
                                                            +

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target instance name.
                                                            5. In the navigation pane, choose Sessions under DBA Assistant.
                                                            6. Click the Sessions page. You can perform the following operations on this tab page:

                                                              • Viewing session statistics

                                                                In the session statistics area, you can view the session summary and session statistics by user, source, and database.

                                                              • Killing abnormal sessions

                                                                In the session list, select the abnormal session you want to end and click Kill Session to recover the database.

                                                                -
                                                              -
                                                              • Exporting the session list

                                                                To export the session list, click above it.

                                                                +
                                                              • Viewing the CPU/memory usage of databases

                                                                In the session list, click Statistics By Database to view the CPU/memory usage of databases in the instance.

                                                            diff --git a/docs/rds/umn/rds_pg_08_0027.html b/docs/rds/umn/rds_pg_08_0027.html index 96cb66175..032a12793 100644 --- a/docs/rds/umn/rds_pg_08_0027.html +++ b/docs/rds/umn/rds_pg_08_0027.html @@ -3,7 +3,7 @@

                                                            Viewing Performance Metrics of a DB Instance

                                                            Scenarios

                                                            DBA Assistant allows you to view the performance metrics of your DB instance. Historical trends of performance metrics within a specified time period help you learn about the status and resource usage of your DB instance. If any alarm is reported, you can take actions timely.

                                                            -

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target instance name.
                                                            5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                                            6. Click the Performance tab. You can perform the following operations on this tab page:

                                                              • Click View Details to view metric changes of your instance in the same period on different days.

                                                                To view more metrics, see Viewing Monitoring Metrics.

                                                                +

                                                                Procedure

                                                                1. Log in to the management console.
                                                                2. Click in the upper left corner and select a region and a project.
                                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                4. On the Instances page, click the target instance name.
                                                                5. In the navigation pane, choose Performance under DBA Assistant.
                                                                6. On the displayed page, perform the following operations:

                                                                  • Click View Details to view metric changes of your instance in the same period on different days.

                                                                    To view more metrics, see Viewing Monitoring Metrics.

                                                                  • Click Create Alarm Rule to go to the Cloud Eye console and customize alarm rules and notification policies. By this way, you can learn about your instance status in a timely manner.

                                                                    For details, see Setting Alarm Rules.

                                                                diff --git a/docs/rds/umn/rds_pg_08_0030.html b/docs/rds/umn/rds_pg_08_0030.html index 24423bbd8..730279be0 100644 --- a/docs/rds/umn/rds_pg_08_0030.html +++ b/docs/rds/umn/rds_pg_08_0030.html @@ -3,9 +3,9 @@

                                                                Viewing Slow Query Logs of a DB Instance

                                                                Scenarios

                                                                Slow Query Log displays a chart of SQL statements that are taking too long to execute and allows you to sort slow SQL statements by multiple dimensions, such as by user, client IP address, or SQL template. It helps you quickly identify bottlenecks and improve instance performance.

                                                                -

                                                                Procedure

                                                                1. Log in to the management console.
                                                                2. Click in the upper left corner and select a region and a project.
                                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                4. On the Instances page, click the target instance name.
                                                                5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                                                6. Click the Slow Query Log tab.

                                                                  Slow SQL Analysis needs to be purchased separately. To use this function, subscribe to Intelligent O&M first.

                                                                  +

                                                                  Procedure

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the target instance name.
                                                                  5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                                                  6. Click the Slow Query Log tab.

                                                                    Slow SQL Analysis needs to be purchased separately. To use this function, upgrade DBA Assistant first.

                                                                    -

                                                                  7. Click Subscribe. In the displayed dialog box, you can learn about Intelligent O&M functions and pricing.
                                                                  8. After subscribing to Intelligent O&M, view slow queries over time of your instance.
                                                                  9. You can view slow queries over time and you can see the slow log archive history for the last 1 hour, last 3 hours, last 12 hours, or a custom time period (spanning no more than one day).
                                                                  10. View slow query log details and template statistics.

                                                                    • To export slow query log information, click Export.
                                                                    • To view log export history, click View Export List.
                                                                    +

                                                                  11. Click Upgrade DBA Assistant. In the displayed dialog box, you can learn about the enhanced features and billing rules.
                                                                  12. After the upgrade is complete, view slow queries over time of your instance.
                                                                  13. You can view slow queries over time and you can see the slow log archive history for the last 1 hour, last 3 hours, last 12 hours, or a custom time period (spanning no more than one day).
                                                                  14. View slow query log details and template statistics.

                                                                    • To export slow query log information, click Export.
                                                                    • To view log export history, click View Export List.

                                                                  diff --git a/docs/rds/umn/rds_pg_08_0032.html b/docs/rds/umn/rds_pg_08_0032.html index 6f5eaf93b..9d1c4d3ae 100644 --- a/docs/rds/umn/rds_pg_08_0032.html +++ b/docs/rds/umn/rds_pg_08_0032.html @@ -5,7 +5,7 @@

                                                                  Constraints

                                                                  • You need to enable Collect All SQL Statements before using SQL Insights.
                                                                  • After Collect All SQL Statements is disabled, new SQL statements will not be collected anymore and the collected SQL data will be deleted.
                                                                  • Only the tasks created in the last two days can be displayed.
                                                                  -

                                                                  Procedure

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the DB instance name.
                                                                  5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                                                  6. Click SQL Explorer and then SQL Insights.
                                                                  7. Click next to Collect All SQL Statements.

                                                                    To disable this function, click Log Settings in the upper right corner, toggle off the Collect All SQL Statements switch, and click OK.

                                                                    +

                                                                    Procedure

                                                                    1. Log in to the management console.
                                                                    2. Click in the upper left corner and select a region and a project.
                                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                    4. On the Instances page, click the DB instance name.
                                                                    5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                                                    6. Click the SQL Insights tab.
                                                                    7. Click next to Collect All SQL Statements.

                                                                      To disable this function, click Log Settings in the upper right corner, toggle off the Collect All SQL Statements switch, and click OK.

                                                                      Collecting all SQL statements generates a performance loss of no more than 5%.

                                                                    8. Click Create Task. In the displayed dialog box, specify Time Range, Dimension, and other configuration items, and click OK.
                                                                    9. In the task list, click Details in the Operation column to view task details.
                                                                    diff --git a/docs/rds/umn/rds_pg_08_0033.html b/docs/rds/umn/rds_pg_08_0033.html index 2beeaf5cf..afd480520 100644 --- a/docs/rds/umn/rds_pg_08_0033.html +++ b/docs/rds/umn/rds_pg_08_0033.html @@ -10,7 +10,7 @@

                                                                    Constraints

                                                                    • The kernel does not record the SQL statements specified in SQL throttling rules you create using query IDs.
                                                                    • SQL statements executed by built-in users (rdsAdmin, rdsMetric, rdsRepl, and rdsBackup) are not affected by SQL throttling rules.
                                                                    • To use SQL throttling, the rds_pg_sql_ccl extension must be installed. For details, see Installing and Uninstalling a Plugin on the RDS Console.
                                                                    -

                                                                    Procedure

                                                                    1. Log in to the management console.
                                                                    2. Click in the upper left corner and select a region and a project.
                                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                    4. On the Instances page, click the target DB instance name.
                                                                    5. In the navigation pane, choose DBA Assistant > Historical Diagnosis.
                                                                    6. Choose SQL Explorer > SQL Throttling.
                                                                    7. Toggle on the SQL throttling switch .

                                                                      SQL throttling rules take effect only after SQL throttling is enabled.

                                                                      +

                                                                      Procedure

                                                                      1. Log in to the management console.
                                                                      2. Click in the upper left corner and select a region and a project.
                                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                      4. On the Instances page, click the target DB instance name.
                                                                      5. In the navigation pane, choose SQL Analysis and Tuning under DBA Assistant.
                                                                      6. Click the SQL Throttling tab.
                                                                      7. Toggle on the SQL throttling switch .

                                                                        SQL throttling rules take effect only after SQL throttling is enabled.

                                                                      8. Click Add Rule. Configure the parameters listed in Table 1.

                                                                        Configure SQL throttling rules based on workloads and resource usage.

                                                                        @@ -28,7 +28,7 @@

                                                      Max. Concurrency

                                                      +

                                                      Max. Concurrency Requests

                                                      The maximum allowed number of concurrent SQL statements that match the rule. SQL statements exceeding this upper limit will not be executed.

                                                      The value ranges from 0 to 50000. 0 indicates that the concurrency of SQL statements is not limited.

                                                      diff --git a/docs/rds/umn/rds_pg_08_0037.html b/docs/rds/umn/rds_pg_08_0037.html index ea44c8737..914046813 100644 --- a/docs/rds/umn/rds_pg_08_0037.html +++ b/docs/rds/umn/rds_pg_08_0037.html @@ -21,13 +21,6 @@

                                                      Viewing Performance Metrics of a DB Instance

                                                      Killing Sessions

                                                      -

                                                      If the maximum number of connections for an instance has been reached and the instance cannot be logged in to, you can view and kill unnecessary sessions through the emergency channel.

                                                      -

                                                      Killing Sessions

                                                      -

                                                      Sessions

                                                      You can query session snapshots of your instance while sorting, filtering, and displaying the snapshots as needed. You can also view session statistics by user, source, and database. Sessions can be killed for urgent instance recovery to ensure database availability.

                                                      @@ -35,6 +28,13 @@

                                                      Managing Real-Time Sessions

                                                      Historical Session Analysis

                                                      +

                                                      You can query historical sessions, historical wait events, and historical top SQL statements of your DB instance.

                                                      +

                                                      Managing Historical Sessions

                                                      +

                                                      Slow Query Log

                                                      Displays slow queries within a specified time period. You can view top 5 slow query logs by user or client IP address, sort statistics, and identify sources of slow SQL statements.

                                                      diff --git a/docs/rds/umn/rds_pg_08_0039.html b/docs/rds/umn/rds_pg_08_0039.html deleted file mode 100644 index 3d57b24ee..000000000 --- a/docs/rds/umn/rds_pg_08_0039.html +++ /dev/null @@ -1,20 +0,0 @@ - - -

                                                      Killing Sessions

                                                      -

                                                      Scenarios

                                                      You can kill sessions when necessary on the Sessions that Can Be Killed If Necessary tab page. This page covers:

                                                      -
                                                      • Emergency Channel: If the maximum number of connections for an instance has been reached and the instance cannot be logged in to, you can view and kill unnecessary sessions through this channel.
                                                      • History Logs: You can view history logs to learn details of the kill operations that you performed using the emergency channel.
                                                      -
                                                      -

                                                      Precautions

                                                      Killing a session may cause the application to disconnect from the instance. Your application should be able to reconnect to the instance.

                                                      -
                                                      -

                                                      Constraints

                                                      • Do not kill sessions unless you really need to. All your kill operations will be logged.
                                                      • Sessions of sensitive users such rdsAdmin, rdsBackup, rdsMetric, and rdsRepl, and sessions whose username is null cannot be killed.
                                                      • You may fail to refresh the session list if your instance has a heavy load. Minimize the resources occupied by the emergency channel. Wait a few seconds and try again.
                                                      • If the CPU usage reaches 100%, requests to kill sessions may fail. You may have to try more than once.
                                                      -
                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the target instance name.
                                                      5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                                      6. Choose Sessions > Sessions that Can Be Killed If Necessary.

                                                        • To kill a session, click the Emergency Channel tab, select the session, and click Kill Session.
                                                        • To check the kill history, click the History Logs tab.
                                                        -

                                                      -
                                                      -
                                                      -
                                                      -
                                                      -
                                                      Parent topic: Problem Diagnosis
                                                      -
                                                      -
                                                      - diff --git a/docs/rds/umn/rds_pg_08_0057.html b/docs/rds/umn/rds_pg_08_0057.html new file mode 100644 index 000000000..2822f60cc --- /dev/null +++ b/docs/rds/umn/rds_pg_08_0057.html @@ -0,0 +1,16 @@ + + +

                                                      Managing Historical Sessions

                                                      +

                                                      Scenarios

                                                      You can query historical sessions, historical wait events, and historical top SQL statements of your DB instance.

                                                      +
                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the target instance name.
                                                      5. In the navigation pane, choose Sessions under DBA Assistant.
                                                      6. On the History Logs tab page.

                                                        In the session statistics area, you can filter sessions by database name, session ID, or username.

                                                        +

                                                        Above the session list, you can click Export to export sessions on the current page. You can also view all export records.

                                                        +

                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Problem Diagnosis
                                                      +
                                                      +
                                                      + diff --git a/docs/rds/umn/rds_pg_10_0005.html b/docs/rds/umn/rds_pg_10_0005.html index eea0c75c9..0ca1f2741 100644 --- a/docs/rds/umn/rds_pg_10_0005.html +++ b/docs/rds/umn/rds_pg_10_0005.html @@ -5,10 +5,10 @@
                                                      diff --git a/docs/rds/umn/rds_pg_11_0004.html b/docs/rds/umn/rds_pg_11_0004.html index e9a494f4d..98dca94dd 100644 --- a/docs/rds/umn/rds_pg_11_0004.html +++ b/docs/rds/umn/rds_pg_11_0004.html @@ -1,7 +1,7 @@

                                                      Managing a Read Replica

                                                      -

                                                      Entering the Management Interface Through a Read Replica

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Overview page.
                                                      +

                                                      Entering the Management Interface Through a Read Replica

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Summary page.

                                                      Deleting a Read Replica

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
                                                      diff --git a/docs/rds/umn/rds_pg_11_0005.html b/docs/rds/umn/rds_pg_11_0005.html index fcf9669e7..c6087060d 100644 --- a/docs/rds/umn/rds_pg_11_0005.html +++ b/docs/rds/umn/rds_pg_11_0005.html @@ -16,7 +16,7 @@

                                                      Figure 3 Connection page

                                                      Parameter description:

                                                      -
                                                      • Host name/address: indicates the IP address of the DB instance you want to connect to. If you connect to a DB instance through a floating IP address, enter the floating IP address displayed in the Connectivity area on the Overview page of your DB instance. If you connect to a DB instance through an EIP, enter the EIP of your DB instance.
                                                      • Port: indicates the database port. By default, the value is 5432.
                                                      • User name: indicates the username. By default, the value is root.
                                                      • Password: indicates the password of the target database username.
                                                      +
                                                      • Host name/address: indicates the IP address of the DB instance you want to connect to. If you connect to a DB instance through a floating IP address, enter the floating IP address displayed in the Connectivity area on the Summary page of your DB instance. If you connect to a DB instance through an EIP, enter the EIP of your DB instance.
                                                      • Port: indicates the database port. By default, the value is 5432.
                                                      • User name: indicates the username. By default, the value is root.
                                                      • Password: indicates the password of the target database username.

                                                    7. In the login window, check that the connection information is correct. The target DB instance is successfully connected.
                                                      8. diff --git a/docs/rds/umn/rds_pg_change_database_port.html b/docs/rds/umn/rds_pg_change_database_port.html index 96918daf0..89b2bd268 100644 --- a/docs/rds/umn/rds_pg_change_database_port.html +++ b/docs/rds/umn/rds_pg_change_database_port.html @@ -3,11 +3,11 @@

                                                      Changing a Database Port

                                                      Scenarios

                                                      This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed accordingly.

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                                      5. On the Overview page, find Database Port and click Configure under it

                                                        A PostgreSQL database can use ports 2100 to 9500.

                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                                        5. On the Summary page, find Database Port and click Configure under it

                                                          A PostgreSQL database can use ports 2100 to 9500.

                                                          • In the displayed dialog box, enter a new port and click Yes.
                                                            • If you change the database port of the primary DB instance, that of the standby DB instance will also be changed.
                                                            • This process takes 1-5 minutes.
                                                          • In the dialog box, click No to cancel the modification.
                                                          -

                                                        6. View the results on the Overview page.
                                                        +

                                                      6. View the results on the Summary page.
                                                      diff --git a/docs/rds/umn/rds_pg_modify_availability.html b/docs/rds/umn/rds_pg_modify_availability.html index 5a3cae891..66be9401c 100644 --- a/docs/rds/umn/rds_pg_modify_availability.html +++ b/docs/rds/umn/rds_pg_modify_availability.html @@ -4,7 +4,7 @@

                                                      Scenarios

                                                      You can configure the failover priority for reliability or for availability, depending on your service requirements.

                                                      • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
                                                      • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the primary instance name.
                                                      5. On the displayed Overview page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                                      6. View the results on the Overview page.
                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the primary instance name.
                                                      5. On the displayed Summary page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                                      6. View the results on the Summary page.
                                                      diff --git a/docs/rds/umn/rds_pg_modify_instance_name.html b/docs/rds/umn/rds_pg_modify_instance_name.html index 0db0b186a..b30fe115d 100644 --- a/docs/rds/umn/rds_pg_modify_instance_name.html +++ b/docs/rds/umn/rds_pg_modify_instance_name.html @@ -3,10 +3,10 @@

                                                      Changing a DB Instance Name

                                                      Scenarios

                                                      You can change the name of a primary DB instance or read replica.

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                        Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to edit the DB instance name.

                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                          Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to edit the DB instance name.

                                                          The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

                                                          • To submit the change, click .
                                                          • To cancel the change, click .
                                                          -

                                                        5. View the results on the Overview page.
                                                        +

                                                      5. View the results on the Summary page.
                                                      diff --git a/docs/rds/umn/rds_pg_reset_password.html b/docs/rds/umn/rds_pg_reset_password.html index 3e4326f65..37af0166b 100644 --- a/docs/rds/umn/rds_pg_reset_password.html +++ b/docs/rds/umn/rds_pg_reset_password.html @@ -13,7 +13,7 @@

                                                      -

                                                      Method 2

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the target DB instance.
                                                      5. On the Overview page, find Administrator and click Reset Password under it.
                                                      6. Enter and confirm a new password.

                                                        Keep this password secure. The system cannot retrieve it.

                                                        +

                                                        Method 2

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the target DB instance.
                                                        5. On the Summary page, find Administrator and click Reset Password under it.
                                                        6. Enter and confirm a new password.

                                                          Keep this password secure. The system cannot retrieve it.

                                                          The new password must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_=+?,). Enter a strong password and periodically change it for security reasons.

                                                          If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
                                                          • To submit the new password, click OK.
                                                          • To cancel the reset operation, click Cancel.
                                                          diff --git a/docs/rds/umn/rds_pg_scale_cluster.html b/docs/rds/umn/rds_pg_scale_cluster.html index b5275af17..6d85e1be7 100644 --- a/docs/rds/umn/rds_pg_scale_cluster.html +++ b/docs/rds/umn/rds_pg_scale_cluster.html @@ -1,9 +1,9 @@ -

                                                          Scaling up Storage Space

                                                          +

                                                          Scaling Up Storage Space

                                                          Scenarios

                                                          If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

                                                          You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

                                                          -

                                                          RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

                                                          +

                                                          Services are not interrupted during storage scale-up.If you need to change the storage type, refer to Changing a Storage Type.

                                                          Instance Becomes Read-Only When Storage Is Full

                                                          For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

                                                          @@ -37,18 +37,18 @@

                                                          Constraints

                                                          • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
                                                          • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
                                                          • You cannot reboot or delete a DB instance that is being scaled up.
                                                          • Storage space can only be scaled up.
                                                          • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.

                                                          Scaling up a Primary DB Instance

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

                                                            You can also perform the following operations to scale up storage space:

                                                            -
                                                            • Click the target DB instance to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
                                                            +
                                                            • Click the target DB instance to enter the Summary page. In the Storage & Backup area, click Scale Storage Space.

                                                          5. On the displayed page, specify the new storage space and click Next.

                                                            The minimum start value of each scaling is 10 GB. A DB instance can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

                                                          6. Confirm specifications.

                                                            • If you need to modify your settings, click Previous.
                                                            • If you do not need to modify your settings, click Submit.
                                                            -

                                                          7. View the scale-up result.

                                                            Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Overview page to verify that the scale-up is successful.

                                                            +

                                                          8. View the scale-up result.

                                                            Scaling up storage space takes 3-5 minutes. During the time period, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Summary page to verify that the scale-up is successful.

                                                          Scaling up a Read Replica

                                                          Scaling up the storage space of a read replica does not affect that of the primary DB instance. Therefore, you can separately scale read replicas to meet service requirements. New storage space of read replicas after scaling up must be greater than or equal to that of the primary DB instance.

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and click in front of it. Locate a read replica to be scaled and choose More > Scale Storage Space in the Operation column.

                                                            You can also perform the following operations to scale up storage space:

                                                            -
                                                            • Click the target DB instance to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
                                                            +
                                                            • Click the target DB instance to enter the Summary page. In the Storage & Backup area, click Scale Storage Space.

                                                          5. On the displayed page, specify the new storage space and click Next.

                                                            The minimum start value of each scaling is 10 GB. A read replica can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

                                                          6. Confirm specifications.

                                                            • If you need to modify your settings, click Previous.
                                                            • If you do not need to modify your settings, click Submit.
                                                            -

                                                          7. View the scale-up result.

                                                            Scaling up storage space takes 3-5 minutes. During this time, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Overview page to verify that the scale-up is successful.

                                                            +

                                                          8. View the scale-up result.

                                                            Scaling up storage space takes 3-5 minutes. During this time, the status of the read replica on the Instances page will be Scaling up. Click the read replica and view the utilization on the displayed Summary page to verify that the scale-up is successful.

                                                          diff --git a/docs/rds/umn/rds_pg_scale_rds.html b/docs/rds/umn/rds_pg_scale_rds.html index d8659c205..704638be2 100644 --- a/docs/rds/umn/rds_pg_scale_rds.html +++ b/docs/rds/umn/rds_pg_scale_rds.html @@ -6,8 +6,8 @@

                                                          Constraints

                                                          • A DB instance cannot be deleted when its instance class is being changed.
                                                          • If the primary DB instance has a read replica, the new DB instance class must be less than or equal to the read replica class. When changing the read replica class, ensure that the selected class is greater than or equal to the current primary instance class.
                                                          • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
                                                          -

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                            Alternatively, click the target DB instance to go to the Overview page. Under Instance Class, click Configure.

                                                            -

                                                          5. On the displayed page, specify the new instance class and click Next.
                                                          6. View the DB instance class change result.

                                                            Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Overview page to check that the change is successful.

                                                            +

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                              Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

                                                              +

                                                            5. On the displayed page, specify the new instance class and click Next.
                                                            6. View the DB instance class change result.

                                                              Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Summary page to check that the change is successful.

                                                              After the CPU or memory of a PostgreSQL DB instance is changed, the system will change the values of the following parameters accordingly:

                                                              • shared_buffers
                                                              • max_connections
                                                              • maintenance_work_mem
                                                              • effective_cache_size
                                                              diff --git a/docs/rds/umn/rds_pg_switch_ha.html b/docs/rds/umn/rds_pg_switch_ha.html index a6515d36e..6d3b0e81f 100644 --- a/docs/rds/umn/rds_pg_switch_ha.html +++ b/docs/rds/umn/rds_pg_switch_ha.html @@ -5,7 +5,7 @@

                                                            Constraints

                                                            • A DB instance is running properly.
                                                            • The replication between the primary and standby instances is normal.
                                                            -

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target primary/standby DB instance.
                                                            5. In the Configurations area on the displayed Overview page, under DB Instance Type, click Switch.

                                                              A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                              +

                                                              Procedure

                                                              1. Log in to the management console.
                                                              2. Click in the upper left corner and select a region and a project.
                                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                              4. On the Instances page, click the target primary/standby DB instance.
                                                              5. In the Configurations area on the displayed Summary page, under DB Instance Type, click Switch.

                                                                A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                              6. In the displayed dialog box, click Yes to switch between the primary and standby DB instances.

                                                                If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

                                                              7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

                                                                • During the switchover process, the DB instance status is Switchover in progress.
                                                                • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.
                                                                diff --git a/docs/rds/umn/rds_reset_password.html b/docs/rds/umn/rds_reset_password.html index 29fbb622e..83bb614bb 100644 --- a/docs/rds/umn/rds_reset_password.html +++ b/docs/rds/umn/rds_reset_password.html @@ -13,7 +13,7 @@

                                                            -

                                                            Method 2

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target DB instance.
                                                            5. On the Overview page, find Administrator and click Reset Password under it.
                                                            6. Enter and confirm a new password.

                                                              Keep this password secure. The system cannot retrieve it.

                                                              +

                                                              Method 2

                                                              1. Log in to the management console.
                                                              2. Click in the upper left corner and select a region and a project.
                                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                              4. On the Instances page, click the target DB instance.
                                                              5. On the Summary page, find Administrator and click Reset Password under it.
                                                              6. Enter and confirm a new password.

                                                                Keep this password secure. The system cannot retrieve it.

                                                                The new password must consist of 8 to 32 characters and contain at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters (~!@#$%^*-_=+?,()&.|). Enter a strong password and periodically change it for security reasons.

                                                                If provided password will be considered by system as weak, you will receive an error and you should provide stronger password.
                                                                • To submit the new password, click OK.
                                                                • To cancel the reset operation, click Cancel.
                                                                diff --git a/docs/rds/umn/rds_sqlserver_0024.html b/docs/rds/umn/rds_sqlserver_0024.html index 20de948fc..c626a88b9 100644 --- a/docs/rds/umn/rds_sqlserver_0024.html +++ b/docs/rds/umn/rds_sqlserver_0024.html @@ -4,10 +4,10 @@

                                                                You can apply for a private domain name and connect to your RDS DB instance through the private domain name.

                                                                Constraints

                                                                After a private domain name is generated, changing the floating IP address will interrupt database connections. Exercise caution when performing this operation.

                                                                -

                                                                Applying for a Private Domain Name

                                                                1. Log in to the management console.
                                                                2. Click in the upper left corner and select a region and a project.
                                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                4. On the Instances page, click the DB instance name to go to the Overview page.
                                                                5. Under Private Domain Name, click Apply.

                                                                  Alternatively, in the navigation pane on the left, choose Connectivity & Security. On the displayed page, click Apply next to the Private Domain Name field.

                                                                  +

                                                                  Applying for a Private Domain Name

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the DB instance name to go to the Summary page.
                                                                  5. Under Private Domain Name, click Apply.

                                                                    Alternatively, in the navigation pane on the left, choose Connectivity & Security. On the displayed page, click Apply next to the Private Domain Name field.

                                                                  6. In the Private Domain Name field, view the generated private domain name.
                                                                  -

                                                                  Changing a Private Domain Name

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the DB instance name to go to the Overview page.
                                                                  5. Under Private Domain Name, click Configure.
                                                                  6. In the displayed dialog box, enter a new private domain name. Click OK.

                                                                    • Only the prefix of a private domain name can be modified.
                                                                    • The prefix of a private domain name can contain 8 to 63 characters, and can include only letters and digits.
                                                                    • The new private domain name must be different from the existing ones.
                                                                    +

                                                                    Changing a Private Domain Name

                                                                    1. Log in to the management console.
                                                                    2. Click in the upper left corner and select a region and a project.
                                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                    4. On the Instances page, click the DB instance name to go to the Summary page.
                                                                    5. Under Private Domain Name, click Configure.
                                                                    6. In the displayed dialog box, enter a new private domain name. Click OK.

                                                                      • Only the prefix of a private domain name can be modified.
                                                                      • The prefix of a private domain name can contain 8 to 63 characters, and can include only letters and digits.
                                                                      • The new private domain name must be different from the existing ones.

                                                                    diff --git a/docs/rds/umn/rds_sqlserver_05_0008.html b/docs/rds/umn/rds_sqlserver_05_0008.html index df0ab73ba..b296a59d8 100644 --- a/docs/rds/umn/rds_sqlserver_05_0008.html +++ b/docs/rds/umn/rds_sqlserver_05_0008.html @@ -18,7 +18,7 @@
                                                                  7. Changing a Storage Type
                                                                    8. -
                                                                  8. Scaling up Storage Space
                                                                    +
                                                                  9. Scaling Up Storage Space
                                                                  10. Configuring Autoscaling
                                                                    11. diff --git a/docs/rds/umn/rds_sqlserver_05_0024.html b/docs/rds/umn/rds_sqlserver_05_0024.html index da3c9be54..0ddc0c28d 100644 --- a/docs/rds/umn/rds_sqlserver_05_0024.html +++ b/docs/rds/umn/rds_sqlserver_05_0024.html @@ -9,7 +9,7 @@

                                                                  Changing a Floating IP Address

                                                                  You can change the floating IP address of an existing DB instance.

                                                                  -
                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the target DB instance name to go to the Overview page.
                                                                  5. Under Floating IP Address, click Configure.
                                                                  6. In the displayed dialog box, select an available IP address and click OK.

                                                                    In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

                                                                    +
                                                                    1. Log in to the management console.
                                                                    2. Click in the upper left corner and select a region and a project.
                                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                    4. On the Instances page, click the target DB instance name to go to the Summary page.
                                                                    5. Under Floating IP Address, click Configure.
                                                                    6. In the displayed dialog box, select an available IP address and click OK.

                                                                      In the in-use IP address list, the IP addresses whose statuses are To be used are occupied and cannot be used.

                                                                diff --git a/docs/rds/umn/rds_sqlserver_05_0038.html b/docs/rds/umn/rds_sqlserver_05_0038.html index a17335351..887067407 100644 --- a/docs/rds/umn/rds_sqlserver_05_0038.html +++ b/docs/rds/umn/rds_sqlserver_05_0038.html @@ -5,7 +5,7 @@

                                                                Precautions

                                                                • During the maintenance window, the DB instance will be intermittently disconnected for one or two times. Ensure that your applications support automatic reconnection.
                                                                -

                                                                Procedure

                                                                1. Log in to the management console.
                                                                2. Click in the upper left corner and select a region and a project.
                                                                3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                4. On the Instances page, click the target DB instance name to go to the Overview page. Under Maintenance Window, click Configure.
                                                                5. In the displayed dialog box, select a maintenance window and click OK.

                                                                  Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                                                                  +

                                                                  Procedure

                                                                  1. Log in to the management console.
                                                                  2. Click in the upper left corner and select a region and a project.
                                                                  3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                                  4. On the Instances page, click the target DB instance name to go to the Summary page. Under Maintenance Window, click Configure.
                                                                  5. In the displayed dialog box, select a maintenance window and click OK.

                                                                    Changing the maintenance window does not affect the execution time of the scheduled tasks in the original maintenance period.

                                                                  diff --git a/docs/rds/umn/rds_sqlserver_05_0050.html b/docs/rds/umn/rds_sqlserver_05_0050.html index 17cce6f5e..9025e2871 100644 --- a/docs/rds/umn/rds_sqlserver_05_0050.html +++ b/docs/rds/umn/rds_sqlserver_05_0050.html @@ -2,6 +2,7 @@

                                                                  Changing a Storage Type

                                                                  Scenarios

                                                                  If the storage type of your DB instance does not match your workloads, you can change it as needed.

                                                                  +

                                                                  For details about storage types, see DB Instance Storage Types.

                                                                  Constraints

                                                                  • If the storage type of a read replica is different from that of its associated DB instance, the data synchronization may be affected. Ensure that the storage type of the read replica is the same as or faster than that of the primary DB instance.
                                                                  • During the storage type change, operations such as changing the instance class and scaling up storage space cannot be performed on the instance.
                                                                  • Changing the storage type may affect storage performance, so the storage type should be changed during off-peak hours.
                                                                  • Changing the storage type may take several minutes, hours, or even days. The time required depends on the throughput, storage space, and original storage type. This operation cannot be paused.
                                                                  • In rare cases, the change may fail due to resource problems. If this happens, you are advised to perform the change again.
                                                                  @@ -13,27 +14,31 @@

                                                      Ultra-high I/O

                                                      +

                                                      Cloud SSD

                                                      Cloud SSD or extreme SSD

                                                      -

                                                      Cloud SSD

                                                      -

                                                      Extreme SSD

                                                      +

                                                      Extreme SSD or Flexible SSD

                                                      Extreme SSD

                                                      Cloud SSD

                                                      +

                                                      Cloud SSD or Flexible SSD

                                                      +

                                                      Flexible SSD

                                                      +

                                                      Cloud SSD or Extreme SSD
                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                      Alternatively, click the target DB instance to go to the Overview page. Under Instance Class, click Configure.

                                                      -

                                                    5. On the displayed page, select a new storage type and click Next.
                                                    6. Confirm the new storage type. Click Submit.
                                                    7. Check the results.

                                                      Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Overview page.

                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                        Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

                                                        +

                                                      5. On the displayed page, select a target Storage Type, for example, Extreme SSD for Storage Type and click Next.

                                                        If the target storage type is Flexible SSD, click Disk QoS under Change Type and enter the IOPS and throughput.

                                                        +
                                                        • IOPS: Flexible SSD decouples capacity from performance and allows for tailored IOPS for your business requirements with fixed capacity.

                                                          This parameter is available only for Flexible SSD. The value range is from 3000 to 128000. The IOPS is limited by the disk size and must be no greater than 500 times the disk capacity.

                                                          +
                                                        • Throughput: Flexible SSD decouples capacity from performance and allows for tailored throughput for your business requirements with fixed capacity.

                                                          This parameter is available only for Flexible SSD. The value ranges from 125 to 1000 (in MiB/s) and must also be no greater than the IOPS divided by 4.

                                                          +
                                                        +

                                                      6. Confirm the configurations and Click Submit.
                                                      7. Check the results.

                                                        Return to the Instances page. A few minutes later, click the instance name and check the new storage type on the displayed Summary page.

                                                    diff --git a/docs/rds/umn/rds_sqlserver_05_0117.html b/docs/rds/umn/rds_sqlserver_05_0117.html index eaf47499f..a6709319b 100644 --- a/docs/rds/umn/rds_sqlserver_05_0117.html +++ b/docs/rds/umn/rds_sqlserver_05_0117.html @@ -1,8 +1,8 @@

                                                    Introduction to Instance Overview

                                                    -

                                                    On the Overview page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. DBA Assistant diagnoses instance health using operational data analytics and intelligent algorithms, and provides you with solutions and suggestions for handling detected exceptions.

                                                    -

                                                    Functions

                                                    Table 1 lists the functions provided on the Overview page.

                                                    +

                                                    On the Summary page, you can get knowledge of the overall status of your RDS for SQL Server instance, including alarms, intelligent anomaly diagnosis, and key performance metrics. DBA Assistant diagnoses instance health using operational data analytics and intelligent algorithms, and provides you with solutions and suggestions for handling detected exceptions.

                                                    +

                                                    Functions

                                                    Table 1 lists the functions provided on the Summary page.

                                                    @@ -33,7 +33,7 @@
                                                    Table 1 Function description

                                                    Function

                                                    -

                                                    Instance Information

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target instance name to go to the Overview page.
                                                    5. In the Instance Information area, check the instance information and modify the instance as required.
                                                    +

                                                    Instance Information

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target instance name to go to the Summary page.
                                                    5. In the Instance Information area, check the instance information and modify the instance as required.

                                                    Alarms

                                                    In the Alarms area, check alarm information of your instance.

                                                    Based on the configured alarm rules, you can see active alarms of your instance, including alarms in the Alarm (metric) or Triggered (event) state.

                                                    diff --git a/docs/rds/umn/rds_sqlserver_11_0004.html b/docs/rds/umn/rds_sqlserver_11_0004.html index c8d1667b0..4d212a730 100644 --- a/docs/rds/umn/rds_sqlserver_11_0004.html +++ b/docs/rds/umn/rds_sqlserver_11_0004.html @@ -1,7 +1,7 @@

                                                    Managing a Read Replica

                                                    -

                                                    Entering the Management Interface Through a Read Replica

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Overview page.
                                                    +

                                                    Entering the Management Interface Through a Read Replica

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. In the DB instance list, click to expand the DB instance details and click the target read replica to go to the Summary page.

                                                    Deleting a Read Replica

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. In the DB instance list, click in front of a DB instance, locate the read replica to be deleted, and choose More > Delete in the Operation column.
                                                    diff --git a/docs/rds/umn/rds_sqlserver_change_database_port.html b/docs/rds/umn/rds_sqlserver_change_database_port.html index 0e94308ac..f3c76bbfe 100644 --- a/docs/rds/umn/rds_sqlserver_change_database_port.html +++ b/docs/rds/umn/rds_sqlserver_change_database_port.html @@ -3,11 +3,11 @@

                                                    Changing a Database Port

                                                    Scenarios

                                                    This section describes how to change the database port of a primary DB instance or a read replica. For primary/standby DB instances, changing the database port of the primary DB instance will cause the database port of the standby DB instance to also be changed accordingly.

                                                    -

                                                    Procedure

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                                    5. On the Overview page, find Database Port and click Configure under it

                                                      For RDS for SQL Server 2022 Enterprise Edition, 2022 Standard Edition, 2019 Enterprise Edition, 2019 Standard Edition, 2017 Enterprise Edition, and 2017 Standard Edition, the port number can be set to 1433 (default) or 2100 to 9500 (excluding 5050, 5353, 5355, 5985, and 5986).

                                                      +

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the target DB instance or click first and then click the target read replica.
                                                      5. On the Summary page, find Database Port and click Configure under it

                                                        For RDS for SQL Server 2022 Enterprise Edition, 2022 Standard Edition, 2019 Enterprise Edition, 2019 Standard Edition, 2017 Enterprise Edition, and 2017 Standard Edition, the port number can be set to 1433 (default) or 2100 to 9500 (excluding 5050, 5353, 5355, 5985, and 5986).

                                                        • In the displayed dialog box, enter a new port and click Yes.
                                                          • If you change the database port of the primary DB instance, that of the standby DB instance will also be changed.
                                                          • This process takes 1-5 minutes.
                                                        • In the dialog box, click No to cancel the modification.
                                                        -

                                                      6. View the results on the Overview page.
                                                      +

                                                    6. View the results on the Summary page.
                                                    diff --git a/docs/rds/umn/rds_sqlserver_dba_02.html b/docs/rds/umn/rds_sqlserver_dba_02.html index d3ae15c89..dc9b2ddda 100644 --- a/docs/rds/umn/rds_sqlserver_dba_02.html +++ b/docs/rds/umn/rds_sqlserver_dba_02.html @@ -3,7 +3,7 @@

                                                    Storage Analysis

                                                    Scenarios

                                                    RDS for SQL Server provides space monitoring and analysis by instance, database, and even table, helping you quickly learn about space information and identify space problems.

                                                    -

                                                    Overview

                                                    1. Log in to the management console.
                                                    2. Click in the upper left corner and select a region and a project.
                                                    3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                    4. On the Instances page, click the DB instance name.
                                                    5. In the navigation pane, choose DBA Assistant > Real-Time Diagnosis.
                                                    6. On the Storage Analysis tab page, view storage usage. If your storage is insufficient, scale it up.

                                                      +

                                                      Overview

                                                      1. Log in to the management console.
                                                      2. Click in the upper left corner and select a region and a project.
                                                      3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                      4. On the Instances page, click the DB instance name.
                                                      5. In the navigation pane, choose Storage Analysis under DBA Assistant.
                                                      6. On the Storage Analysis page, view storage usage. If your storage is insufficient, scale it up.

                                                        Table 1 Parameter description

                                                        Parameter

                                                        Description

                                                        diff --git a/docs/rds/umn/rds_sqlserver_modify_availability.html b/docs/rds/umn/rds_sqlserver_modify_availability.html index 64fca485b..6c7decfb9 100644 --- a/docs/rds/umn/rds_sqlserver_modify_availability.html +++ b/docs/rds/umn/rds_sqlserver_modify_availability.html @@ -4,7 +4,7 @@

                                                        Scenarios

                                                        You can configure the failover priority for reliability or for availability, depending on your service requirements.

                                                        • Reliability: This option is selected by default. Data consistency is preferentially ensured during a primary/standby failover. This is recommended for users whose highest priority is data consistency.
                                                        • Availability: Database availability is preferentially ensured during a primary/standby failover. This is recommended for users who require their databases to provide uninterrupted online services.
                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the primary instance name.
                                                        5. On the displayed Overview page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                                        6. View the results on the Overview page.
                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, click the primary instance name.
                                                        5. On the displayed Summary page, find Failover Priority and click Configure under it. In the displayed dialog box, select a priority and click OK.
                                                        6. View the results on the Summary page.
                                                        diff --git a/docs/rds/umn/rds_sqlserver_modify_instance_name.html b/docs/rds/umn/rds_sqlserver_modify_instance_name.html index 23985c60c..fd0b6b3a5 100644 --- a/docs/rds/umn/rds_sqlserver_modify_instance_name.html +++ b/docs/rds/umn/rds_sqlserver_modify_instance_name.html @@ -3,10 +3,10 @@

                                                        Changing a DB Instance Name

                                                        Scenarios

                                                        You can change the name of a primary DB instance or read replica.

                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                          Alternatively, click the target DB instance to go to the Overview page. Under DB Instance Name, click to edit the DB instance name.

                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and click next to it to edit the DB instance name. Then, click OK.

                                                            Alternatively, click the target DB instance to go to the Summary page. Under DB Instance Name, click to edit the DB instance name.

                                                            The DB instance name must start with a letter and consist of 4 to 64 characters. Only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_) are allowed.

                                                            • To submit the change, click .
                                                            • To cancel the change, click .
                                                            -

                                                          5. View the results on the Overview page.
                                                          +

                                                        5. View the results on the Summary page.
                                                        diff --git a/docs/rds/umn/rds_sqlserver_scale_cluster.html b/docs/rds/umn/rds_sqlserver_scale_cluster.html index a9c238eaf..bb8b32dec 100644 --- a/docs/rds/umn/rds_sqlserver_scale_cluster.html +++ b/docs/rds/umn/rds_sqlserver_scale_cluster.html @@ -1,9 +1,9 @@ -

                                                        Scaling up Storage Space

                                                        +

                                                        Scaling Up Storage Space

                                                        Scenarios

                                                        If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.

                                                        You are advised to set alarm rules for the storage space usage by referring to Setting Alarm Rules.

                                                        -

                                                        RDS allows you to scale up storage space of DB instances but you cannot change the storage type. During the scale-up period, services are not interrupted.

                                                        +

                                                        Services are not interrupted during storage scale-up.If you need to change the storage type, refer to Changing a Storage Type.

                                                        Instance Becomes Read-Only When Storage Is Full

                                                        For details about the causes and solutions of insufficient storage space, see What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?

                                                        @@ -37,10 +37,10 @@

                                                        Constraints

                                                        • DB instances can be scaled up numerous times.
                                                        • The maximum allowed storage is 4,000 GB. There is no limit on the number of scale-ups.
                                                        • For primary/standby DB instances, scaling up the primary DB instance will cause the standby DB instance to also be scaled up accordingly.
                                                        • You cannot reboot or delete a DB instance that is being scaled up.
                                                        • Storage space can only be scaled up.
                                                        • If you scale up a DB instance with disks encrypted, the expanded storage space will be encrypted using the original encryption key.

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and choose More > Scale Storage Space in the Operation column.

                                                          You can also perform the following operations to scale up storage space:

                                                          -
                                                          • Click the target DB instance to enter the Overview page. In the Storage & Backup area, click Scale Storage Space.
                                                          +
                                                          • Click the target DB instance to enter the Summary page. In the Storage & Backup area, click Scale Storage Space.

                                                        5. On the displayed page, specify the new storage space and click Next.

                                                          The minimum start value of each scaling is 10 GB. A DB instance can be scaled up only by a multiple of 10 GB. The allowed maximum storage space is 4,000 GB.

                                                        6. Confirm specifications.

                                                          • If you need to modify your settings, click Previous.
                                                          • If you do not need to modify your settings, click Submit.
                                                          -

                                                        7. View the scale-up result.

                                                          Scaling up storage space takes 3-5 minutes. During this time, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Overview page to verify that the scale-up is successful.

                                                          +

                                                        8. View the scale-up result.

                                                          Scaling up storage space takes 3-5 minutes. During this time, the status of the DB instance on the Instances page will be Scaling up. Click the DB instance and view the utilization on the displayed Summary page to verify that the scale-up is successful.

                                                        diff --git a/docs/rds/umn/rds_sqlserver_scale_rds.html b/docs/rds/umn/rds_sqlserver_scale_rds.html index ff1246441..a556ecab3 100644 --- a/docs/rds/umn/rds_sqlserver_scale_rds.html +++ b/docs/rds/umn/rds_sqlserver_scale_rds.html @@ -7,8 +7,8 @@
                                                        • After you change instance classes, the DB instances will be rebooted and service will be interrupted. Therefore, you are advised to change instance classes during off-peak hours.
                                                        • Set the recovery model of your database to FULL instead of SIMPLE.
                                                          • In the SIMPLE recovery model, no incremental backup is performed for the database, so the database cannot be restored to a specified time point.
                                                          • For primary/standby or cluster instances, if the recovery model is set to SIMPLE, no replication relationship will be established for the instances. As a result, a primary/standby switchover or instance class change cannot be performed.
                                                        -

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. Click in the upper left corner and select a region and a project.
                                                        3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                        4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                          Alternatively, click the target DB instance to go to the Overview page. Under Instance Class, click Configure.

                                                          -

                                                        5. On the displayed page, specify the new instance class and click Next.
                                                        6. View the DB instance class change result.

                                                          Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Overview page to check that the change is successful.

                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, locate the target DB instance and choose More > Change Instance Class in the Operation column.

                                                            Alternatively, click the target DB instance to go to the Summary page. Under Instance Class, click Configure.

                                                            +

                                                          5. On the displayed page, specify the new instance class and click Next.
                                                          6. View the DB instance class change result.

                                                            Changing the DB instance class takes 5–15 minutes. During this period, the status of the DB instance on the Instances page is Changing instance class. After a few minutes, click the DB instance and view the instance class on the displayed Summary page to check that the change is successful.

                                                            After you change a Microsoft SQL Server DB instance class, the value of max server memory will also be changed accordingly. You are advised to set it to a size equal to the memory size minus 520 MB. For example, if there is 1 GB of memory (1,024 MB), you are advised to set max server memory to 504 MB (1,024 MB – 520 MB).

                                                          diff --git a/docs/rds/umn/rds_sqlserver_switch_ha.html b/docs/rds/umn/rds_sqlserver_switch_ha.html index a327b211a..0200e907b 100644 --- a/docs/rds/umn/rds_sqlserver_switch_ha.html +++ b/docs/rds/umn/rds_sqlserver_switch_ha.html @@ -6,7 +6,7 @@

                                                          Constraints

                                                          • A DB instance is running properly.
                                                          • The replication between the primary and standby instances is normal.
                                                          • Set the recovery model of your database to FULL instead of SIMPLE.
                                                            • In the SIMPLE recovery model, no incremental backup is performed for the database, so the database cannot be restored to a specified time point.
                                                            • For primary/standby or cluster instances, if the recovery model is set to SIMPLE, no replication relationship will be established for the instances. As a result, a primary/standby switchover or instance class change cannot be performed.
                                                          -

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Click in the upper left corner and select a region and a project.
                                                          3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                          4. On the Instances page, click the target primary/standby DB instance.
                                                          5. In the Configurations area on the displayed Overview page, under DB Instance Type, click Switch.

                                                            A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                            +

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target primary/standby DB instance.
                                                            5. In the Configurations area on the displayed Summary page, under DB Instance Type, click Switch.

                                                              A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                            6. In the displayed dialog box, click Yes to switch between the primary and standby DB instances.

                                                              If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

                                                            7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

                                                              • During the switchover process, the DB instance status is Switchover in progress.
                                                              • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.
                                                              diff --git a/docs/rds/umn/rds_switch_ha.html b/docs/rds/umn/rds_switch_ha.html index 4210ce47b..f2f791363 100644 --- a/docs/rds/umn/rds_switch_ha.html +++ b/docs/rds/umn/rds_switch_ha.html @@ -5,7 +5,7 @@

                                                            Constraints

                                                            • A DB instance is running properly.
                                                            • The replication between the primary and standby instances is normal.
                                                            -

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. Click in the upper left corner and select a region and a project.
                                                            3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                            4. On the Instances page, click the target primary/standby DB instance.
                                                            5. In the Configurations area on the displayed Overview page, under DB Instance Type, click Switch.

                                                              A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                              +

                                                              Procedure

                                                              1. Log in to the management console.
                                                              2. Click in the upper left corner and select a region and a project.
                                                              3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
                                                              4. On the Instances page, click the target primary/standby DB instance.
                                                              5. In the Configurations area on the displayed Summary page, under DB Instance Type, click Switch.

                                                                A primary/standby switchover may cause service interruptions for some seconds or minutes (depending on the replication delay). If the replication delay is too long, a small amount of data may be lost. To prevent traffic congestion, you are advised to perform a switchover during off-peak hours.

                                                              6. In the displayed dialog box, click Yes to switch between the primary and standby DB instances.

                                                                If the replication status is Available and the replication delay is greater than 300s, the primary/standby switchover task cannot be delivered.

                                                              7. After a switchover is successful, you can view and manage the DB instance on the Instances page.

                                                                • During the switchover process, the DB instance status is Switchover in progress.
                                                                • In the upper right corner of the DB instance list, click to refresh the list. After the switchover is successful, the DB instance status will become Available.