diff --git a/1 b/1 new file mode 100644 index 00000000..dd7ce517 --- /dev/null +++ b/1 @@ -0,0 +1,136 @@ + origin/HEAD -> origin/main + origin/confpy + origin/cts_umn + origin/das_umn + origin/das_umn-20230519 + origin/ddm-api-20230208 + origin/ddm-api-2023020801 + origin/ddm-umn-20230208 + origin/ddm-umn-2023020801 + origin/ddm_api + origin/ddm_test_pull1675844639326 + origin/ddm_umn + origin/dds-api-20230329 + origin/dds-umn-20230329 + origin/dds-umn-20230421 + origin/dds1_api + origin/dds_api + origin/dds_api3 + origin/dds_api_0905 + origin/dds_api_20230817 + origin/dds_api_20230905 + origin/dds_umn + origin/dds_umn3 + origin/dds_umn_20230817 + origin/drs-bestpractice-20230509 + origin/drs-bp-20230511 + origin/drs-umn-20230210 + origin/drs_api + origin/drs_api1 + origin/drs_bp + origin/drs_um4 + origin/drs_umn + origin/drs_umn2 + origin/drs_umn3 + origin/drs_umn4 + origin/fixing_zuul_yaml + origin/gaussdb_api + origin/gaussdb_umn + origin/gaussdb_umn_20221230 + origin/gaussdb_umnmn_20221230 + origin/gaussdbformysql-api-20230315 + origin/gaussdbformysql-umn-20230314 + origin/gaussdbmysql_api + origin/gtema-patch-1 + origin/main + origin/new_folders + origin/nosql-20230322-version + origin/nosql-api-20230322 + origin/nosql-umn-20230206 + origin/nosql-umn-20230207 + origin/nosql-umn-20230210 + origin/nosql_test_pull1675681842331 + origin/nosql_umn + origin/nosql_umn2 + origin/nosql_umn3 + origin/opengauss-umn-20230207 + origin/opengauss_api + origin/opengauss_api2 + origin/opengauss_api_0112 + origin/opengauss_umn + origin/opengauss_umn2 + origin/opengauss_umn3 + origin/opengauss_umn_0112 + origin/rds-api-20230322 + origin/rds-umn-20230206 + origin/rds1_api + origin/rds_api2 + origin/rds_api3 + origin/rds_api4 + origin/rds_umn + origin/rds_umn3 + origin/rds_umn_0112 + upstream/add_apm + upstream/add_apm_metadata + upstream/add_params + upstream/adding_mrs_comp_metadata + upstream/adding_new_docs + upstream/another_special_char + upstream/aom_api + upstream/aom_umn + upstream/apig_dataarts + upstream/apig_dataarts_fix + upstream/cbr_umn_revert_0426 + upstream/ces_umn + upstream/ces_umn_recover + upstream/change_add_dli + upstream/change_obs_pfs_perms + upstream/change_propose_reference + upstream/cleanup + upstream/colon_asterisk_fix + upstream/conversion_link_fixes + upstream/convert + upstream/convert-fname + upstream/convertor_fix + upstream/convertor_th_fix + upstream/cse_addon + upstream/dbss_er_addon + upstream/dollar_char + upstream/drs_umn_revert_fix + upstream/empty_space_fix + upstream/empty_space_v2 + upstream/enabling_cci_metadata + upstream/fg_iam_ecs + upstream/fix_links + upstream/fixing_sfs_name + upstream/gaussb_title_fix + upstream/gaussdb_api_20221230-pr_recreate + upstream/gtema-patch-1 + upstream/gtema-patch-2 + upstream/hss_add_zuul + upstream/hss_fix + upstream/ims_api_0406_reupload + upstream/ims_umn_406_reupload + upstream/kms_api + upstream/lts_api + upstream/lts_umn + upstream/main + upstream/metadata_in_convert_jobs + upstream/new_obs_doc + upstream/new_rds_conversion_fix + upstream/obs_umn_0414_reupload + upstream/pandoc_update + upstream/permissions_pr_fix + upstream/plas_umn + upstream/public-images_on_public + upstream/rts_api + upstream/split-convertor + upstream/strong_fix + upstream/swift_addon + upstream/swift_deprecated_nosql_api_addon + upstream/unit-tests + upstream/vpn_api + upstream/vpn_umn + upstream/waf_and_obs_fix + upstream/wafd_revert_20230423 + upstream/zuul_new_repos diff --git a/docs/rds/umn/ALL_META.TXT.json b/docs/rds/umn/ALL_META.TXT.json index 3b2e0a8c..12f3689f 100644 --- a/docs/rds/umn/ALL_META.TXT.json +++ b/docs/rds/umn/ALL_META.TXT.json @@ -173,7 +173,7 @@ "uri":"rds_01_0012.html", "product_code":"rds", "code":"18", - "des":"RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.For", + "des":"RDS for MySQL, RDS for PostgreSQL, RDS for SQL Server 2019 Enterprise Edition, and 2017 Enterprise Edition DB instances support read replicas to offload read traffic from", "doc_type":"usermanual", "kw":"Read/Write Splitting,Typical Applications,User Guide", "title":"Read/Write Splitting", @@ -190,13 +190,13 @@ "githuburl":"" }, { - "uri":"rds_01_0025.html", + "uri":"rds_01_0017.html", "product_code":"rds", "code":"20", - "des":"RDS provides two types of user permissions by default: user management and resource management.User management permissions cover the management of users, user groups, and", + "des":"If you need to assign different permissions to employees in your enterprise to access your RDS resources, Identity and Access Management (IAM) is a good choice for fine-g", "doc_type":"usermanual", - "kw":"user management,resource management,User Permissions,Introduction,User Guide", - "title":"User Permissions", + "kw":"Permissions Management,Introduction,User Guide", + "title":"Permissions Management", "githuburl":"" }, { @@ -740,11 +740,41 @@ "githuburl":"" }, { - "uri":"rds_05_0000.html", + "uri":"rds_07_0000.html", "product_code":"rds", "code":"75", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", + "kw":"Permissions Management", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"rds_07_0002.html", + "product_code":"rds", + "code":"76", + "des":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", + "doc_type":"usermanual", + "kw":"RDS,RDS,RDS,Creating a User and Granting Permissions,Permissions Management,User Guide", + "title":"Creating a User and Granting Permissions", + "githuburl":"" + }, + { + "uri":"rds_07_0003.html", + "product_code":"rds", + "code":"77", + "des":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", + "doc_type":"usermanual", + "kw":"RDS,RDS Custom Policies,Permissions Management,User Guide", + "title":"RDS Custom Policies", + "githuburl":"" + }, + { + "uri":"rds_05_0000.html", + "product_code":"rds", + "code":"78", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", "kw":"Instance Lifecycle", "title":"Instance Lifecycle", "githuburl":"" @@ -752,7 +782,7 @@ { "uri":"rds_05_0055.html", "product_code":"rds", - "code":"76", + "code":"79", "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", "doc_type":"usermanual", "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", @@ -762,7 +792,7 @@ { "uri":"rds_05_0057.html", "product_code":"rds", - "code":"77", + "code":"80", "des":"If you use DB instances only for routine development, you can temporarily stop pay-per-use DB instances to save money. You can stop a DB instance for up to seven days.If ", "doc_type":"usermanual", "kw":"Stopping a DB Instance,Instance Lifecycle,User Guide", @@ -772,7 +802,7 @@ { "uri":"rds_05_0058.html", "product_code":"rds", - "code":"78", + "code":"81", "des":"You can stop your DB instance temporarily to save money. After stopping your DB instance, you can restart it to begin using it again.If you start a primary DB instance, r", "doc_type":"usermanual", "kw":"Starting a DB Instance,Instance Lifecycle,User Guide", @@ -782,7 +812,7 @@ { "uri":"rds_08_0013.html", "product_code":"rds", - "code":"79", + "code":"82", "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", "doc_type":"usermanual", "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", @@ -792,7 +822,7 @@ { "uri":"rds_08_0022.html", "product_code":"rds", - "code":"80", + "code":"83", "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", "doc_type":"usermanual", "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", @@ -802,7 +832,7 @@ { "uri":"rds_05_0017.html", "product_code":"rds", - "code":"81", + "code":"84", "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", "doc_type":"usermanual", "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", @@ -812,7 +842,7 @@ { "uri":"rds_08_0002.html", "product_code":"rds", - "code":"82", + "code":"85", "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", "doc_type":"usermanual", "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", @@ -822,7 +852,7 @@ { "uri":"rds_mysql_recycle.html", "product_code":"rds", - "code":"83", + "code":"86", "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", "doc_type":"usermanual", "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", @@ -832,7 +862,7 @@ { "uri":"rds_05_0001.html", "product_code":"rds", - "code":"84", + "code":"87", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Modifications", @@ -842,7 +872,7 @@ { "uri":"rds_05_0003.html", "product_code":"rds", - "code":"85", + "code":"88", "des":"RDS for MySQL supports minor version upgrades to improve performance, add new functions, and fix bugs.The upgrade will cause the DB instance to reboot and interrupt servi", "doc_type":"usermanual", "kw":"RDS for MySQL,MySQL,Upgrading a Minor Version,Instance Modifications,User Guide", @@ -852,7 +882,7 @@ { "uri":"rds_modify_instance_name.html", "product_code":"rds", - "code":"86", + "code":"89", "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", @@ -862,7 +892,7 @@ { "uri":"rds_modify_availability.html", "product_code":"rds", - "code":"87", + "code":"90", "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", "doc_type":"usermanual", "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", @@ -872,7 +902,7 @@ { "uri":"en-us_topic_scale_rds.html", "product_code":"rds", - "code":"88", + "code":"91", "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", "doc_type":"usermanual", "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", @@ -882,17 +912,27 @@ { "uri":"en-us_topic_scale_cluster.html", "product_code":"rds", - "code":"89", + "code":"92", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,MySQL,Scaling up Storage Space,Instance Modifications,", "title":"Scaling up Storage Space", "githuburl":"" }, + { + "uri":"rds_05_0039.html", + "product_code":"rds", + "code":"93", + "des":"With storage autoscaling enabled, when RDS detects that you are running out of database space, it automatically scales up your storage.Autoscaling up the storage of a rea", + "doc_type":"usermanual", + "kw":"Storage Autoscaling,Instance Modifications,User Guide", + "title":"Storage Autoscaling", + "githuburl":"" + }, { "uri":"rds_05_0038.html", "product_code":"rds", - "code":"90", + "code":"94", "des":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", "doc_type":"usermanual", "kw":"Changing the Maintenance Window,Instance Modifications,User Guide", @@ -902,7 +942,7 @@ { "uri":"rds_05_0023.html", "product_code":"rds", - "code":"91", + "code":"95", "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the ", "doc_type":"usermanual", "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", @@ -912,17 +952,27 @@ { "uri":"rds_switch_ha.html", "product_code":"rds", - "code":"92", + "code":"96", "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", "doc_type":"usermanual", "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", "title":"Manually Switching Between Primary and Standby DB Instances", "githuburl":"" }, + { + "uri":"rds_05_0060.html", + "product_code":"rds", + "code":"97", + "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.6, 5.7, or 8.0 support standby instanc", + "doc_type":"usermanual", + "kw":"Migrating a Standby DB Instance,Instance Modifications,User Guide", + "title":"Migrating a Standby DB Instance", + "githuburl":"" + }, { "uri":"rds_11_0011.html", "product_code":"rds", - "code":"93", + "code":"98", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Read Replicas", @@ -932,7 +982,7 @@ { "uri":"rds_11_0012.html", "product_code":"rds", - "code":"94", + "code":"99", "des":"RDS for MySQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. ", "doc_type":"usermanual", "kw":"read replicas,MySQL,Introducing Read Replicas,Read Replicas,User Guide", @@ -942,7 +992,7 @@ { "uri":"en-us_topic_add_read_replica.html", "product_code":"rds", - "code":"95", + "code":"100", "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After DB instances are created, you can create read replicas for them.", "doc_type":"usermanual", "kw":"create read replicas,create read replicas,Creating a Read Replica,Read Replicas,User Guide", @@ -952,7 +1002,7 @@ { "uri":"rds_11_0015.html", "product_code":"rds", - "code":"96", + "code":"101", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing a Read Replica,Read Replicas,User Guide", @@ -962,7 +1012,7 @@ { "uri":"rds_05_0034.html", "product_code":"rds", - "code":"97", + "code":"102", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backups and Restorations", @@ -972,7 +1022,7 @@ { "uri":"en-us_topic_backup_restore.html", "product_code":"rds", - "code":"98", + "code":"103", "des":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", "doc_type":"usermanual", "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", @@ -982,7 +1032,7 @@ { "uri":"rds_08_0004.html", "product_code":"rds", - "code":"99", + "code":"104", "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", "doc_type":"usermanual", "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", @@ -992,7 +1042,7 @@ { "uri":"rds_08_0005.html", "product_code":"rds", - "code":"100", + "code":"105", "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", "doc_type":"usermanual", "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", @@ -1002,7 +1052,7 @@ { "uri":"rds_08_0006.html", "product_code":"rds", - "code":"101", + "code":"106", "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for MySQL enables you to download ", "doc_type":"usermanual", "kw":"download a manual or an automated backup file,RDS for MySQL,full backup files,Downloading a Backup F", @@ -1012,7 +1062,7 @@ { "uri":"rds_03_0100.html", "product_code":"rds", - "code":"102", + "code":"107", "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 ", "doc_type":"usermanual", "kw":"binlog backup files,Downloading a Binlog Backup File,Backups and Restorations,User Guide", @@ -1022,7 +1072,7 @@ { "uri":"rds_08_0007.html", "product_code":"rds", - "code":"103", + "code":"108", "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", "doc_type":"usermanual", "kw":"Restoring from Backup Files to DB Instances,Backups and Restorations,User Guide", @@ -1032,7 +1082,7 @@ { "uri":"rds_08_0044.html", "product_code":"rds", - "code":"104", + "code":"109", "des":"You can download backup files by referring to Downloading a Backup File and restore data from them.Backup data cannot be restored to local databases that run the Windows ", "doc_type":"usermanual", "kw":"MySQL,MySQL,MySQL,Restoring from Backup Files to a Self-Built MySQL Database,Backups and Restoration", @@ -1042,7 +1092,7 @@ { "uri":"rds_08_0008.html", "product_code":"rds", - "code":"105", + "code":"110", "des":"You can restore from automated backups to a specified point in time.RDS for MySQL supports restoration to a new, the original, or an existing DB instance.When you enter t", "doc_type":"usermanual", "kw":"RDS for MySQL,restoration to a new, the original,,Restoring a DB Instance to a Point in Time,Backups", @@ -1052,7 +1102,7 @@ { "uri":"rds_08_0009.html", "product_code":"rds", - "code":"106", + "code":"111", "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", "doc_type":"usermanual", "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", @@ -1062,7 +1112,7 @@ { "uri":"rds_08_0010.html", "product_code":"rds", - "code":"107", + "code":"112", "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", "doc_type":"usermanual", "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", @@ -1072,7 +1122,7 @@ { "uri":"rds_08_0011.html", "product_code":"rds", - "code":"108", + "code":"113", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Parameter Template Management", @@ -1082,7 +1132,7 @@ { "uri":"en-us_topic_parameter_group.html", "product_code":"rds", - "code":"109", + "code":"114", "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", "doc_type":"usermanual", "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", @@ -1092,7 +1142,7 @@ { "uri":"rds_configuration.html", "product_code":"rds", - "code":"110", + "code":"115", "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", "doc_type":"usermanual", "kw":"Modifying Parameters,Parameter Template Management,User Guide", @@ -1102,7 +1152,7 @@ { "uri":"rds_08_0042.html", "product_code":"rds", - "code":"111", + "code":"116", "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", "doc_type":"usermanual", "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", @@ -1112,7 +1162,7 @@ { "uri":"rds_08_0012.html", "product_code":"rds", - "code":"112", + "code":"117", "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", "doc_type":"usermanual", "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", @@ -1122,7 +1172,7 @@ { "uri":"rds_05_0099.html", "product_code":"rds", - "code":"113", + "code":"118", "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", "doc_type":"usermanual", "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", @@ -1132,7 +1182,7 @@ { "uri":"rds_08_0014.html", "product_code":"rds", - "code":"114", + "code":"119", "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", "doc_type":"usermanual", "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", @@ -1142,7 +1192,7 @@ { "uri":"rds_08_0015.html", "product_code":"rds", - "code":"115", + "code":"120", "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", "doc_type":"usermanual", "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", @@ -1152,7 +1202,7 @@ { "uri":"rds_05_0018.html", "product_code":"rds", - "code":"116", + "code":"121", "des":"You can apply parameter templates to DB instances as needed.The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications ha", "doc_type":"usermanual", "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", @@ -1162,7 +1212,7 @@ { "uri":"rds_05_0098.html", "product_code":"rds", - "code":"117", + "code":"122", "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", "doc_type":"usermanual", "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", @@ -1172,7 +1222,7 @@ { "uri":"rds_08_0016.html", "product_code":"rds", - "code":"118", + "code":"123", "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", "doc_type":"usermanual", "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", @@ -1182,7 +1232,7 @@ { "uri":"rds_08_0017.html", "product_code":"rds", - "code":"119", + "code":"124", "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", "doc_type":"usermanual", "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", @@ -1192,7 +1242,7 @@ { "uri":"rds_05_0005.html", "product_code":"rds", - "code":"120", + "code":"125", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Connection Management", @@ -1202,7 +1252,7 @@ { "uri":"rds_05_0024.html", "product_code":"rds", - "code":"121", + "code":"126", "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", "doc_type":"usermanual", "kw":"change floating IP addresses,automatically-assigned IP address,change the floating IP address,Config", @@ -1212,7 +1262,7 @@ { "uri":"rds_public_accessibility.html", "product_code":"rds", - "code":"122", + "code":"127", "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", "doc_type":"usermanual", "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", @@ -1222,7 +1272,7 @@ { "uri":"rds_change_database_port.html", "product_code":"rds", - "code":"123", + "code":"128", "des":"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 pri", "doc_type":"usermanual", "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", @@ -1232,17 +1282,147 @@ { "uri":"rds_11_0009.html", "product_code":"rds", - "code":"124", + "code":"129", "des":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", "doc_type":"usermanual", "kw":"security group,RDS,RDS,RDS,RDS,RDS,Configuring a Security Group Rule,Connection Management,User Guid", "title":"Configuring a Security Group Rule", "githuburl":"" }, + { + "uri":"rds_11_0050.html", + "product_code":"rds", + "code":"130", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Database Proxy (Read/Write Splitting)", + "title":"Database Proxy (Read/Write Splitting)", + "githuburl":"" + }, + { + "uri":"rds_11_0035.html", + "product_code":"rds", + "code":"131", + "des":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read rep", + "doc_type":"usermanual", + "kw":"Introducing Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Introducing Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"rds_11_0047.html", + "product_code":"rds", + "code":"132", + "des":"In most cases, an RDS for MySQL proxy instance sends all requests in transactions to the primary DB instance to ensure transaction correctness. However, in some framework", + "doc_type":"usermanual", + "kw":"Configuring Transaction Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Configuring Transaction Splitting", + "githuburl":"" + }, + { + "uri":"rds_11_0017.html", + "product_code":"rds", + "code":"133", + "des":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. This section describes how to enable read/write sp", + "doc_type":"usermanual", + "kw":"Enabling Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Enabling Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"rds_11_0018.html", + "product_code":"rds", + "code":"134", + "des":"After read/write splitting is enabled, you can configure the delay threshold and routing policy as required.The system automatically distributes weights to read replicas,", + "doc_type":"usermanual", + "kw":"Configuring the Delay Threshold and Routing Policy,Database Proxy (Read/Write Splitting),User Guide", + "title":"Configuring the Delay Threshold and Routing Policy", + "githuburl":"" + }, + { + "uri":"rds_11_0026.html", + "product_code":"rds", + "code":"135", + "des":"After read/write splitting is enabled, you can change the read/write splitting address.Changing the read/write splitting address will interrupt database connections and s", + "doc_type":"usermanual", + "kw":"change the read/write splitting address,Changing the Read/Write Splitting Address,Database Proxy (Re", + "title":"Changing the Read/Write Splitting Address", + "githuburl":"" + }, + { + "uri":"rds_11_0028.html", + "product_code":"rds", + "code":"136", + "des":"You can change the instance class (vCPU or memory) of a DB proxy instance as required. If the DB instance status changes from Changing proxy instance class to Available, ", + "doc_type":"usermanual", + "kw":"vCPU or memory,Changing the Instance Class of a DB Proxy Instance,Database Proxy (Read/Write Splitti", + "title":"Changing the Instance Class of a DB Proxy Instance", + "githuburl":"" + }, + { + "uri":"rds_11_0045.html", + "product_code":"rds", + "code":"137", + "des":"After read/write splitting is enabled, you can change the number of proxy nodes as required.Read/write splitting has been enabled.The primary DB instance, read replicas, ", + "doc_type":"usermanual", + "kw":"Changing the Number of Proxy Nodes,Database Proxy (Read/Write Splitting),User Guide", + "title":"Changing the Number of Proxy Nodes", + "githuburl":"" + }, + { + "uri":"rds_11_0024.html", + "product_code":"rds", + "code":"138", + "des":"You can manually upgrade the RDS for MySQL database proxy to the latest kernel version to improve performance, add new functions, and fix problems.Intermittent disconnect", + "doc_type":"usermanual", + "kw":"Upgrading the Kernel Version of Database Proxy,Database Proxy (Read/Write Splitting),User Guide", + "title":"Upgrading the Kernel Version of Database Proxy", + "githuburl":"" + }, + { + "uri":"rds_11_0025.html", + "product_code":"rds", + "code":"139", + "des":"If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant ", + "doc_type":"usermanual", + "kw":"Enabling or Disabling Access Control,Database Proxy (Read/Write Splitting),User Guide", + "title":"Enabling or Disabling Access Control", + "githuburl":"" + }, + { + "uri":"rds_11_0019.html", + "product_code":"rds", + "code":"140", + "des":"You can disable read/write splitting as required.If the database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting addr", + "doc_type":"usermanual", + "kw":"Disabling Read/Write Splitting,Database Proxy (Read/Write Splitting),User Guide", + "title":"Disabling Read/Write Splitting", + "githuburl":"" + }, + { + "uri":"rds_11_0020.html", + "product_code":"rds", + "code":"141", + "des":"This section describes the rules of distributing read weights to DB instances of different specifications.When the system automatically sets the read weights for DB insta", + "doc_type":"usermanual", + "kw":"Rules for Distributing Weights,Database Proxy (Read/Write Splitting),User Guide", + "title":"Rules for Distributing Weights", + "githuburl":"" + }, + { + "uri":"rds_11_0021.html", + "product_code":"rds", + "code":"142", + "des":"After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write split", + "doc_type":"usermanual", + "kw":"Testing Read/Write Splitting Performance,Database Proxy (Read/Write Splitting),User Guide", + "title":"Testing Read/Write Splitting Performance", + "githuburl":"" + }, { "uri":"rds_05_0006.html", "product_code":"rds", - "code":"125", + "code":"143", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Security", @@ -1252,7 +1432,7 @@ { "uri":"rds_reset_password.html", "product_code":"rds", - "code":"126", + "code":"144", "des":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", "doc_type":"usermanual", "kw":"reset the administrator password,RDS,Resetting the Administrator Password,Data Security,User Guide", @@ -1262,7 +1442,7 @@ { "uri":"rds_08_0003.html", "product_code":"rds", - "code":"127", + "code":"145", "des":"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 pri", "doc_type":"usermanual", "kw":"Changing a Security Group,Data Security,User Guide", @@ -1272,7 +1452,7 @@ { "uri":"rds_08_0019.html", "product_code":"rds", - "code":"128", + "code":"146", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Metrics and Alarms", @@ -1282,7 +1462,7 @@ { "uri":"rds_06_0001.html", "product_code":"rds", - "code":"129", + "code":"147", "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the RDS metrics that can be monitored by Cloud Eye as well as their na", "doc_type":"usermanual", "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", @@ -1292,7 +1472,7 @@ { "uri":"rds_06_0002.html", "product_code":"rds", - "code":"130", + "code":"148", "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", "doc_type":"usermanual", "kw":"Setting Alarm Rules,Metrics and Alarms,User Guide", @@ -1302,7 +1482,7 @@ { "uri":"rds_06_0003.html", "product_code":"rds", - "code":"131", + "code":"149", "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", "doc_type":"usermanual", "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", @@ -1312,7 +1492,7 @@ { "uri":"rds_08_0020.html", "product_code":"rds", - "code":"132", + "code":"150", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Interconnection with CTS", @@ -1322,7 +1502,7 @@ { "uri":"rds_06_0004.html", "product_code":"rds", - "code":"133", + "code":"151", "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", "doc_type":"usermanual", "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", @@ -1332,7 +1512,7 @@ { "uri":"rds_06_0005.html", "product_code":"rds", - "code":"134", + "code":"152", "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", "doc_type":"usermanual", "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", @@ -1342,7 +1522,7 @@ { "uri":"rds_08_0021.html", "product_code":"rds", - "code":"135", + "code":"153", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -1352,7 +1532,7 @@ { "uri":"rds_mysql_error_log.html", "product_code":"rds", - "code":"136", + "code":"154", "des":"RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs contain warning- and error-level logs generated during ", "doc_type":"usermanual", "kw":"Viewing Error Logs,Log Management,User Guide", @@ -1362,7 +1542,7 @@ { "uri":"rds_mysql_slow_query_log.html", "product_code":"rds", - "code":"137", + "code":"155", "des":"Slow query logs record statements that exceed long_query_time. You can use these logs to identify and optimize the statements that are executing slowly.RDS supports the f", "doc_type":"usermanual", "kw":"Viewing Slow Query Logs,Log Management,User Guide", @@ -1372,7 +1552,7 @@ { "uri":"rds_switch_log.html", "product_code":"rds", - "code":"138", + "code":"156", "des":"You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.Only failover and switchover logs within 30 days are displayed.", "doc_type":"usermanual", "kw":"MySQL,Viewing Failover/Switchover Logs,Log Management,User Guide", @@ -1382,7 +1562,7 @@ { "uri":"rds_sql_auditing_log.html", "product_code":"rds", - "code":"139", + "code":"157", "des":"After you enable the SQL audit function, all SQL operations will be recorded in log files. You can download audit logs to view log details.By default, SQL audit is disabl", "doc_type":"usermanual", "kw":"Enabling the SQL Audit Function,Log Management,User Guide", @@ -1392,7 +1572,7 @@ { "uri":"rds_download_sql_auditing_log.html", "product_code":"rds", - "code":"140", + "code":"158", "des":"If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. ", "doc_type":"usermanual", "kw":"Downloading SQL Audit Logs,Log Management,User Guide", @@ -1402,7 +1582,7 @@ { "uri":"rds_05_0007.html", "product_code":"rds", - "code":"141", + "code":"159", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Task Center", @@ -1412,7 +1592,7 @@ { "uri":"rds_task_0001.html", "product_code":"rds", - "code":"142", + "code":"160", "des":"You can view the progress and results of scheduled and instant tasks on the Task Center page.RDS allows you to view and manage the following instant tasks:Creating DB ins", "doc_type":"usermanual", "kw":"Viewing a Task,Task Center,User Guide", @@ -1422,7 +1602,7 @@ { "uri":"rds_task_0002.html", "product_code":"rds", - "code":"143", + "code":"161", "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", "doc_type":"usermanual", "kw":"Deleting a Task Record,Task Center,User Guide", @@ -1432,7 +1612,7 @@ { "uri":"rds_tag.html", "product_code":"rds", - "code":"144", + "code":"162", "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", "doc_type":"usermanual", "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for MySQL,User Guide", @@ -1442,7 +1622,7 @@ { "uri":"rds_09_0000.html", "product_code":"rds", - "code":"145", + "code":"163", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Working with RDS for PostgreSQL", @@ -1452,7 +1632,7 @@ { "uri":"rds_pg_05_0001_02.html", "product_code":"rds", - "code":"146", + "code":"164", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Migration", @@ -1462,7 +1642,7 @@ { "uri":"rds_09_0023.html", "product_code":"rds", - "code":"147", + "code":"165", "des":"PostgreSQL supports logical backups. You can use the pg_dump logical backup function to export backup files and then import them to RDS using psql.You can access RDS DB i", "doc_type":"usermanual", "kw":"PostgreSQL,pg_dump,Migrating Data to RDS for PostgreSQL Using psql,Data Migration,User Guide", @@ -1472,7 +1652,7 @@ { "uri":"rds_pg_10_0000.html", "product_code":"rds", - "code":"148", + "code":"166", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Parameter Tuning", @@ -1482,7 +1662,7 @@ { "uri":"rds_pg_10_0001.html", "product_code":"rds", - "code":"149", + "code":"167", "des":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", "doc_type":"usermanual", "kw":"Suggestions on PostgreSQL Parameter Tuning,Parameter Tuning,User Guide", @@ -1490,39 +1670,39 @@ "githuburl":"" }, { - "uri":"rds_04_0001.html", + "uri":"rds_pg_07_0000.html", "product_code":"rds", - "code":"150", + "code":"168", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"PostgreSQL Enhanced Edition", - "title":"PostgreSQL Enhanced Edition", + "kw":"Permissions Management", + "title":"Permissions Management", "githuburl":"" }, { - "uri":"rds_03_0018.html", + "uri":"rds_pg_07_0002.html", "product_code":"rds", - "code":"151", - "des":"PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/S", + "code":"169", + "des":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", "doc_type":"usermanual", - "kw":"PostgreSQL Enhanced Edition,Introduction to PostgreSQL Enhanced Edition,PostgreSQL Enhanced Edition,", - "title":"Introduction to PostgreSQL Enhanced Edition", + "kw":"RDS,RDS,RDS,Creating a User and Granting Permissions,Permissions Management,User Guide", + "title":"Creating a User and Granting Permissions", "githuburl":"" }, { - "uri":"rds_04_0002.html", + "uri":"rds_pg_07_0003.html", "product_code":"rds", - "code":"152", - "des":"This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.", + "code":"170", + "des":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", "doc_type":"usermanual", - "kw":"Functions,PostgreSQL Enhanced Edition,User Guide", - "title":"Functions", + "kw":"RDS,RDS Custom Policies,Permissions Management,User Guide", + "title":"RDS Custom Policies", "githuburl":"" }, { "uri":"rds_pg_05_0000.html", "product_code":"rds", - "code":"153", + "code":"171", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Lifecycle", @@ -1532,7 +1712,7 @@ { "uri":"rds_pg_05_0055.html", "product_code":"rds", - "code":"154", + "code":"172", "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", "doc_type":"usermanual", "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", @@ -1542,7 +1722,7 @@ { "uri":"rds_pg_stop.html", "product_code":"rds", - "code":"155", + "code":"173", "des":"If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to seven days.If you s", "doc_type":"usermanual", "kw":"Stopping an Instance,Instance Lifecycle,User Guide", @@ -1552,7 +1732,7 @@ { "uri":"rds_pg_start.html", "product_code":"rds", - "code":"156", + "code":"174", "des":"You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.If you start a primary instance, read repli", "doc_type":"usermanual", "kw":"Starting an Instance,Instance Lifecycle,User Guide", @@ -1562,7 +1742,7 @@ { "uri":"rds_09_0024.html", "product_code":"rds", - "code":"157", + "code":"175", "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", "doc_type":"usermanual", "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", @@ -1572,7 +1752,7 @@ { "uri":"rds_pg_06_0022.html", "product_code":"rds", - "code":"158", + "code":"176", "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", "doc_type":"usermanual", "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", @@ -1582,7 +1762,7 @@ { "uri":"rds_pg_05_0017.html", "product_code":"rds", - "code":"159", + "code":"177", "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", "doc_type":"usermanual", "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", @@ -1592,7 +1772,7 @@ { "uri":"rds_09_0025.html", "product_code":"rds", - "code":"160", + "code":"178", "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", "doc_type":"usermanual", "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", @@ -1602,7 +1782,7 @@ { "uri":"rds_pg_recycle.html", "product_code":"rds", - "code":"161", + "code":"179", "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", "doc_type":"usermanual", "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", @@ -1612,17 +1792,27 @@ { "uri":"rds_pg_05_0001.html", "product_code":"rds", - "code":"162", + "code":"180", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Modifications", "title":"Instance Modifications", "githuburl":"" }, + { + "uri":"rds_pg_05_0003.html", + "product_code":"rds", + "code":"181", + "des":"RDS for PostgreSQL supports minor version upgrades to improve performance, add new functions, and fix bugs.When any new minor version is released to address vulnerabiliti", + "doc_type":"usermanual", + "kw":"Upgrading a Minor Version,Instance Modifications,User Guide", + "title":"Upgrading a Minor Version", + "githuburl":"" + }, { "uri":"rds_pg_modify_instance_name.html", "product_code":"rds", - "code":"163", + "code":"182", "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", @@ -1632,7 +1822,7 @@ { "uri":"rds_pg_modify_availability.html", "product_code":"rds", - "code":"164", + "code":"183", "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", "doc_type":"usermanual", "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", @@ -1642,7 +1832,7 @@ { "uri":"rds_pg_scale_rds.html", "product_code":"rds", - "code":"165", + "code":"184", "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", "doc_type":"usermanual", "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", @@ -1652,7 +1842,7 @@ { "uri":"rds_pg_scale_cluster.html", "product_code":"rds", - "code":"166", + "code":"185", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", @@ -1662,7 +1852,7 @@ { "uri":"rds_pg_05_0038.html", "product_code":"rds", - "code":"167", + "code":"186", "des":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", "doc_type":"usermanual", "kw":"Changing the Maintenance Window,Instance Modifications,User Guide", @@ -1672,7 +1862,7 @@ { "uri":"rds_pg_05_0023.html", "product_code":"rds", - "code":"168", + "code":"187", "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", "doc_type":"usermanual", "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", @@ -1682,17 +1872,27 @@ { "uri":"rds_pg_switch_ha.html", "product_code":"rds", - "code":"169", + "code":"188", "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", "doc_type":"usermanual", "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", "title":"Manually Switching Between Primary and Standby DB Instances", "githuburl":"" }, + { + "uri":"rds_pg_05_0060.html", + "product_code":"rds", + "code":"189", + "des":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.DDL operations and scheduled events will be suspended during migration. To preve", + "doc_type":"usermanual", + "kw":"Migrating a Standby DB Instance,Instance Modifications,User Guide", + "title":"Migrating a Standby DB Instance", + "githuburl":"" + }, { "uri":"rds_pg_11_0001.html", "product_code":"rds", - "code":"170", + "code":"190", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Read Replicas", @@ -1702,7 +1902,7 @@ { "uri":"rds_pg_11_0002.html", "product_code":"rds", - "code":"171", + "code":"191", "des":"RDS for PostgreSQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affec", "doc_type":"usermanual", "kw":"read replicas,Introducing Read Replicas,Read Replicas,User Guide", @@ -1712,7 +1912,7 @@ { "uri":"rds_add_read_replica_pg.html", "product_code":"rds", - "code":"172", + "code":"192", "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.You can create read replicas as needed.A maximum of five read replicas", "doc_type":"usermanual", "kw":"create read replicas,Creating a Read Replica,Read Replicas,User Guide", @@ -1722,7 +1922,7 @@ { "uri":"rds_pg_11_0004.html", "product_code":"rds", - "code":"173", + "code":"193", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"read replica,Managing a Read Replica,Read Replicas,User Guide", @@ -1732,7 +1932,7 @@ { "uri":"rds_pg_05_0034.html", "product_code":"rds", - "code":"174", + "code":"194", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backups and Restorations", @@ -1742,7 +1942,7 @@ { "uri":"rds_pg_backup_restore.html", "product_code":"rds", - "code":"175", + "code":"195", "des":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", "doc_type":"usermanual", "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", @@ -1752,7 +1952,7 @@ { "uri":"rds_09_0027.html", "product_code":"rds", - "code":"176", + "code":"196", "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", "doc_type":"usermanual", "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", @@ -1762,7 +1962,7 @@ { "uri":"rds_09_0028.html", "product_code":"rds", - "code":"177", + "code":"197", "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", "doc_type":"usermanual", "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", @@ -1772,7 +1972,7 @@ { "uri":"rds_09_0031.html", "product_code":"rds", - "code":"178", + "code":"198", "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", "doc_type":"usermanual", "kw":"download a manual or an automated backup file,full backup files,Downloading a Full Backup File,Backu", @@ -1782,7 +1982,7 @@ { "uri":"rds_pg_05_0138.html", "product_code":"rds", - "code":"179", + "code":"199", "des":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", "doc_type":"usermanual", "kw":"automated backup,incremental backup files,Downloading an Incremental Backup File,Backups and Restora", @@ -1792,27 +1992,17 @@ { "uri":"rds_09_0030.html", "product_code":"rds", - "code":"180", + "code":"200", "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", "doc_type":"usermanual", "kw":"Restoring from Backup Files to RDS for PostgreSQL,Backups and Restorations,User Guide", "title":"Restoring from Backup Files to RDS for PostgreSQL", "githuburl":"" }, - { - "uri":"rds_pg_08_0044.html", - "product_code":"rds", - "code":"181", - "des":"You can download backup files by referring to Downloading a Full Backup File and restore data from them.A tool for decompressing TAR files must be installed in a Unix-lik", - "doc_type":"usermanual", - "kw":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database,Backups and Restorations,User G", - "title":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database", - "githuburl":"" - }, { "uri":"rds_09_0029.html", "product_code":"rds", - "code":"182", + "code":"201", "des":"You can restore from automated backups to a specified point in time.RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.When you en", "doc_type":"usermanual", "kw":"to a specified point in time,RDS for PostgreSQL,restoration to a new, the original,,Restoring a DB I", @@ -1822,7 +2012,7 @@ { "uri":"rds_09_0032.html", "product_code":"rds", - "code":"183", + "code":"202", "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", "doc_type":"usermanual", "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", @@ -1832,7 +2022,7 @@ { "uri":"rds_09_0033.html", "product_code":"rds", - "code":"184", + "code":"203", "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", "doc_type":"usermanual", "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", @@ -1842,7 +2032,7 @@ { "uri":"rds_09_0034.html", "product_code":"rds", - "code":"185", + "code":"204", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Parameter Template Management", @@ -1852,7 +2042,7 @@ { "uri":"rds_pg_parameter_group.html", "product_code":"rds", - "code":"186", + "code":"205", "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", "doc_type":"usermanual", "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", @@ -1862,7 +2052,7 @@ { "uri":"rds_pg_configuration.html", "product_code":"rds", - "code":"187", + "code":"206", "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can change parameter values in custom parameter templates only and canno", "doc_type":"usermanual", "kw":"Modifying Instance Parameters,Parameter Template Management,User Guide", @@ -1872,7 +2062,7 @@ { "uri":"rds_pg_08_0042.html", "product_code":"rds", - "code":"188", + "code":"207", "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", "doc_type":"usermanual", "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", @@ -1882,7 +2072,7 @@ { "uri":"rds_09_0035.html", "product_code":"rds", - "code":"189", + "code":"208", "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", "doc_type":"usermanual", "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", @@ -1892,7 +2082,7 @@ { "uri":"rds_pg_05_0099.html", "product_code":"rds", - "code":"190", + "code":"209", "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", "doc_type":"usermanual", "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", @@ -1902,7 +2092,7 @@ { "uri":"rds_09_0036.html", "product_code":"rds", - "code":"191", + "code":"210", "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", "doc_type":"usermanual", "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", @@ -1912,7 +2102,7 @@ { "uri":"rds_09_0037.html", "product_code":"rds", - "code":"192", + "code":"211", "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", "doc_type":"usermanual", "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", @@ -1922,7 +2112,7 @@ { "uri":"rds_pg_05_0018.html", "product_code":"rds", - "code":"193", + "code":"212", "des":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", "doc_type":"usermanual", "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", @@ -1932,7 +2122,7 @@ { "uri":"rds_pg_05_0098.html", "product_code":"rds", - "code":"194", + "code":"213", "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", "doc_type":"usermanual", "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", @@ -1942,7 +2132,7 @@ { "uri":"rds_09_0038.html", "product_code":"rds", - "code":"195", + "code":"214", "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", "doc_type":"usermanual", "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", @@ -1952,7 +2142,7 @@ { "uri":"rds_09_0039.html", "product_code":"rds", - "code":"196", + "code":"215", "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", "doc_type":"usermanual", "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", @@ -1962,7 +2152,7 @@ { "uri":"rds_pg_05_0005.html", "product_code":"rds", - "code":"197", + "code":"216", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Connection Management", @@ -1972,7 +2162,7 @@ { "uri":"rds_pg_05_0024.html", "product_code":"rds", - "code":"198", + "code":"217", "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", "doc_type":"usermanual", "kw":"change floating IP addresses,automatically-assigned IP address,change the floating IP address,Config", @@ -1982,7 +2172,7 @@ { "uri":"rds_pg_public_accessibility.html", "product_code":"rds", - "code":"199", + "code":"218", "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", "doc_type":"usermanual", "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", @@ -1992,7 +2182,7 @@ { "uri":"rds_pg_change_database_port.html", "product_code":"rds", - "code":"200", + "code":"219", "des":"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 pri", "doc_type":"usermanual", "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", @@ -2002,7 +2192,7 @@ { "uri":"rds_pg_11_0005.html", "product_code":"rds", - "code":"201", + "code":"220", "des":"You can use the pgAdmin client to connect to an RDS DB instance.The pgAdmin version must be 4 or later.Prepare an ECS or a device that can access RDS DB instances.To conn", "doc_type":"usermanual", "kw":"pgAdmin,Connecting to a DB Instance Through pgAdmin,Connection Management,User Guide", @@ -2012,7 +2202,7 @@ { "uri":"rds_09_0046.html", "product_code":"rds", - "code":"202", + "code":"221", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Plugin Management", @@ -2022,7 +2212,7 @@ { "uri":"rds_09_0043.html", "product_code":"rds", - "code":"203", + "code":"222", "des":"RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section", "doc_type":"usermanual", "kw":"Creating or Deleting a Plugin,Plugin Management,User Guide", @@ -2032,7 +2222,7 @@ { "uri":"rds_09_0045.html", "product_code":"rds", - "code":"204", + "code":"223", "des":"The following table lists the plugins supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the plug", "doc_type":"usermanual", "kw":"Supported Plugins,Plugin Management,User Guide", @@ -2042,7 +2232,7 @@ { "uri":"rds_09_0044.html", "product_code":"rds", - "code":"205", + "code":"224", "des":"RDS provides the PostgreSQL tablespace management solution based on user root.# psql --host=--port= --dbname=--username=root -c\"select cont", "doc_type":"usermanual", "kw":"PostgreSQL tablespace,Tablespace Management,Working with RDS for PostgreSQL,User Guide", @@ -2052,7 +2242,7 @@ { "uri":"rds_pg_05_0006.html", "product_code":"rds", - "code":"206", + "code":"225", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Security", @@ -2062,7 +2252,7 @@ { "uri":"rds_pg_reset_password.html", "product_code":"rds", - "code":"207", + "code":"226", "des":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", "doc_type":"usermanual", "kw":"reset the administrator password,RDS,Resetting the Administrator Password,Data Security,User Guide", @@ -2072,7 +2262,7 @@ { "uri":"rds_09_0026.html", "product_code":"rds", - "code":"208", + "code":"227", "des":"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 pri", "doc_type":"usermanual", "kw":"Changing a Security Group,Data Security,User Guide", @@ -2082,7 +2272,7 @@ { "uri":"rds_09_0041.html", "product_code":"rds", - "code":"209", + "code":"228", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Metrics and Alarms", @@ -2092,7 +2282,7 @@ { "uri":"rds_pg_06_0001.html", "product_code":"rds", - "code":"210", + "code":"229", "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", "doc_type":"usermanual", "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", @@ -2102,7 +2292,7 @@ { "uri":"rds_pg_06_0002.html", "product_code":"rds", - "code":"211", + "code":"230", "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", "doc_type":"usermanual", "kw":"alarm rule,Setting Alarm Rules,Metrics and Alarms,User Guide", @@ -2112,7 +2302,7 @@ { "uri":"rds_pg_06_0003.html", "product_code":"rds", - "code":"212", + "code":"231", "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", "doc_type":"usermanual", "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", @@ -2122,7 +2312,7 @@ { "uri":"rds_09_0042.html", "product_code":"rds", - "code":"213", + "code":"232", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Interconnection with CTS", @@ -2132,7 +2322,7 @@ { "uri":"rds_pg_06_0004.html", "product_code":"rds", - "code":"214", + "code":"233", "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", "doc_type":"usermanual", "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", @@ -2142,7 +2332,7 @@ { "uri":"rds_pg_06_0005.html", "product_code":"rds", - "code":"215", + "code":"234", "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", "doc_type":"usermanual", "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", @@ -2152,7 +2342,7 @@ { "uri":"rds_08_001.html", "product_code":"rds", - "code":"216", + "code":"235", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -2162,7 +2352,7 @@ { "uri":"rds_recent_log.html", "product_code":"rds", - "code":"217", + "code":"236", "des":"Error logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner ", "doc_type":"usermanual", "kw":"Viewing Error Logs,Log Management,User Guide", @@ -2172,7 +2362,7 @@ { "uri":"slow_query_log-pg.html", "product_code":"rds", - "code":"218", + "code":"237", "des":"Slow query logs record statements that exceed the log_min_duration_statement value. You can view log details to identify statements that are slowly executed and optimize ", "doc_type":"usermanual", "kw":"Viewing Slow Query Logs,Log Management,User Guide", @@ -2182,7 +2372,7 @@ { "uri":"rds_pg_05_0007.html", "product_code":"rds", - "code":"219", + "code":"238", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Task Center", @@ -2192,7 +2382,7 @@ { "uri":"rds_task_pg_0001.html", "product_code":"rds", - "code":"220", + "code":"239", "des":"You can view the detailed progress and result of the task on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasC", "doc_type":"usermanual", "kw":"Viewing a Task,Task Center,User Guide", @@ -2202,7 +2392,7 @@ { "uri":"rds_task_pg_0002.html", "product_code":"rds", - "code":"221", + "code":"240", "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", "doc_type":"usermanual", "kw":"Deleting a Task Record,Task Center,User Guide", @@ -2212,7 +2402,7 @@ { "uri":"rds_pg_tag.html", "product_code":"rds", - "code":"222", + "code":"241", "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", "doc_type":"usermanual", "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for PostgreSQL,User Guide", @@ -2222,7 +2412,7 @@ { "uri":"rds_10_0000.html", "product_code":"rds", - "code":"223", + "code":"242", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Working with RDS for SQL Server", @@ -2232,7 +2422,7 @@ { "uri":"rds_sqlserver_05_0001_02.html", "product_code":"rds", - "code":"224", + "code":"243", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Migration", @@ -2242,17 +2432,47 @@ { "uri":"rds_10_0035.html", "product_code":"rds", - "code":"225", + "code":"244", "des":"You can access RDS DB instances through an EIP or ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP. To c", "doc_type":"usermanual", "kw":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio,Data Migration,User Guide", "title":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio", "githuburl":"" }, + { + "uri":"rds_sqlserver_07_0000.html", + "product_code":"rds", + "code":"245", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "doc_type":"usermanual", + "kw":"Permissions Management", + "title":"Permissions Management", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_07_0002.html", + "product_code":"rds", + "code":"246", + "des":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", + "doc_type":"usermanual", + "kw":"RDS,RDS,RDS,Creating a User and Granting Permissions,Permissions Management,User Guide", + "title":"Creating a User and Granting Permissions", + "githuburl":"" + }, + { + "uri":"rds_sqlserver_07_0003.html", + "product_code":"rds", + "code":"247", + "des":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", + "doc_type":"usermanual", + "kw":"RDS,RDS Custom Policies,Permissions Management,User Guide", + "title":"RDS Custom Policies", + "githuburl":"" + }, { "uri":"rds_sqlserver_05_0000.html", "product_code":"rds", - "code":"226", + "code":"248", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Lifecycle", @@ -2262,7 +2482,7 @@ { "uri":"rds_sqlserver_05_0055.html", "product_code":"rds", - "code":"227", + "code":"249", "des":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", "doc_type":"usermanual", "kw":"create a DB instance with the same configurations as the selected one,Creating a Same DB Instance as", @@ -2272,7 +2492,7 @@ { "uri":"rds_11_0006.html", "product_code":"rds", - "code":"228", + "code":"250", "des":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", "doc_type":"usermanual", "kw":"Rebooting DB Instances or Read Replicas,Instance Lifecycle,User Guide", @@ -2282,7 +2502,7 @@ { "uri":"rds_sqlserver_06_0022.html", "product_code":"rds", - "code":"229", + "code":"251", "des":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", "doc_type":"usermanual", "kw":"instance items,edit columns,Selecting Displayed Items,Instance Lifecycle,User Guide", @@ -2292,7 +2512,7 @@ { "uri":"rds_sqlserver_05_0017.html", "product_code":"rds", - "code":"230", + "code":"252", "des":"You can export information about all or selected DB instances to view and analyze DB instance information.", "doc_type":"usermanual", "kw":"Exporting DB Instance Information,Instance Lifecycle,User Guide", @@ -2302,7 +2522,7 @@ { "uri":"rds_11_0030.html", "product_code":"rds", - "code":"231", + "code":"253", "des":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", "doc_type":"usermanual", "kw":"Deleting a DB Instance,Deleting a Read Replica,Deleting a DB Instance or Read Replica,Instance Lifec", @@ -2312,7 +2532,7 @@ { "uri":"rds_sqlserver_recycle.html", "product_code":"rds", - "code":"232", + "code":"254", "des":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", "doc_type":"usermanual", "kw":"Read replicas,Recycling a DB Instance,Instance Lifecycle,User Guide", @@ -2322,7 +2542,7 @@ { "uri":"rds_sqlserver_05_0008.html", "product_code":"rds", - "code":"233", + "code":"255", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Instance Modifications", @@ -2332,7 +2552,7 @@ { "uri":"rds_sqlserver_modify_instance_name.html", "product_code":"rds", - "code":"234", + "code":"256", "des":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", "doc_type":"usermanual", "kw":"name,Changing a DB Instance Name,Instance Modifications,User Guide", @@ -2342,7 +2562,7 @@ { "uri":"rds_sqlserver_modify_availability.html", "product_code":"rds", - "code":"235", + "code":"257", "des":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", "doc_type":"usermanual", "kw":"failover priority,Changing the Failover Priority,Instance Modifications,User Guide", @@ -2352,7 +2572,7 @@ { "uri":"rds_sqlserver_scale_rds.html", "product_code":"rds", - "code":"236", + "code":"258", "des":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", "doc_type":"usermanual", "kw":"CPU or memory,Changing a DB Instance Class,Instance Modifications,User Guide", @@ -2362,7 +2582,7 @@ { "uri":"rds_sqlserver_scale_cluster.html", "product_code":"rds", - "code":"237", + "code":"259", "des":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", "doc_type":"usermanual", "kw":"scale up storage space,scale up storage space,Scaling up Storage Space,Instance Modifications,User G", @@ -2372,7 +2592,7 @@ { "uri":"rds_sqlserver_05_0023.html", "product_code":"rds", - "code":"238", + "code":"260", "des":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", "doc_type":"usermanual", "kw":"change single DB instances to primary/standby DB instances,Changing a DB Instance Type from Single t", @@ -2382,7 +2602,7 @@ { "uri":"rds_sqlserver_switch_ha.html", "product_code":"rds", - "code":"239", + "code":"261", "des":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", "doc_type":"usermanual", "kw":"Manually Switching Between Primary and Standby DB Instances,Instance Modifications,User Guide", @@ -2392,7 +2612,7 @@ { "uri":"rds_sqlserver_11_0001.html", "product_code":"rds", - "code":"240", + "code":"262", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Read Replicas", @@ -2402,8 +2622,8 @@ { "uri":"rds_sqlserver_11_0002.html", "product_code":"rds", - "code":"241", - "des":"Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and ser", + "code":"263", + "des":"Only RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.In read-intensive scenarios, a single DB instance may be unable to handl", "doc_type":"usermanual", "kw":"read replicas,Introducing Read Replicas,Read Replicas,User Guide", "title":"Introducing Read Replicas", @@ -2412,7 +2632,7 @@ { "uri":"rds_03_0011.html", "product_code":"rds", - "code":"242", + "code":"264", "des":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After a DB instance has been created, you can create read replicas for", "doc_type":"usermanual", "kw":"create read replicas,read replicas,Creating a Read Replica,Read Replicas,User Guide", @@ -2422,7 +2642,7 @@ { "uri":"rds_sqlserver_11_0004.html", "product_code":"rds", - "code":"243", + "code":"265", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"read replica,Managing a Read Replica,Read Replicas,User Guide", @@ -2432,7 +2652,7 @@ { "uri":"rds_sqlserver_05_0034.html", "product_code":"rds", - "code":"244", + "code":"266", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backups and Restorations", @@ -2442,7 +2662,7 @@ { "uri":"rds_sqlserver_backup_restore.html", "product_code":"rds", - "code":"245", + "code":"267", "des":"RDS supports DB instance backups and restorations to ensure data reliability.Automated backups are created during the backup period of your DB instances. RDS saves automa", "doc_type":"usermanual", "kw":"backups and restorations,Automated backups,Manual backups,Working with Backups,Backups and Restorati", @@ -2452,7 +2672,7 @@ { "uri":"rds_11_0031.html", "product_code":"rds", - "code":"246", + "code":"268", "des":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", "doc_type":"usermanual", "kw":"Configuring an Automated Backup Policy,Backups and Restorations,User Guide", @@ -2462,7 +2682,7 @@ { "uri":"rds_11_0010.html", "product_code":"rds", - "code":"247", + "code":"269", "des":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", "doc_type":"usermanual", "kw":"create manual backups,Creating a Manual Backup,Backups and Restorations,User Guide", @@ -2472,7 +2692,7 @@ { "uri":"rds_11_0013.html", "product_code":"rds", - "code":"248", + "code":"270", "des":"This section describes how to download a manual backup or an automated backup to a local device and restore data from the backup file.If the size of the backup data is gr", "doc_type":"usermanual", "kw":"automated backup,Downloading a Backup File,Backups and Restorations,User Guide", @@ -2482,7 +2702,7 @@ { "uri":"rds_11_0023.html", "product_code":"rds", - "code":"249", + "code":"271", "des":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.Alternatively, click the target DB inst", "doc_type":"usermanual", "kw":"Restoring from Backup Files to RDS for SQL Server,Backups and Restorations,User Guide", @@ -2492,7 +2712,7 @@ { "uri":"rds_05_0044.html", "product_code":"rds", - "code":"250", + "code":"272", "des":"You can download backup files by referring to section Downloading a Backup File and restore data from them. You can use SQL Server Management Studio (SSMS) to connect to ", "doc_type":"usermanual", "kw":"Restoring from Backup Files to a Self-Built SQL Server Database,Backups and Restorations,User Guide", @@ -2502,7 +2722,7 @@ { "uri":"rds_11_0022.html", "product_code":"rds", - "code":"251", + "code":"273", "des":"You can restore from automated backups to a specified point in time.RDS for Microsoft SQL Server supports restoration to a new, the original, or an existing DB instance.I", "doc_type":"usermanual", "kw":"restoration to a new, the original,Restoring a DB Instance to a Point in Time,Backups and Restoratio", @@ -2512,7 +2732,7 @@ { "uri":"rds_10_0055.html", "product_code":"rds", - "code":"252", + "code":"274", "des":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", "doc_type":"usermanual", "kw":"replicate a manual or an automated backup,Replicating a Backup,Backups and Restorations,User Guide", @@ -2522,7 +2742,7 @@ { "uri":"rds_10_0101.html", "product_code":"rds", - "code":"253", + "code":"275", "des":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", "doc_type":"usermanual", "kw":"Deleting a Manual Backup,Backups and Restorations,User Guide", @@ -2532,7 +2752,7 @@ { "uri":"rds_10_0102.html", "product_code":"rds", - "code":"254", + "code":"276", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Parameter Template Management", @@ -2542,7 +2762,7 @@ { "uri":"rds_sqlserver_parameter_group.html", "product_code":"rds", - "code":"255", + "code":"277", "des":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", "doc_type":"usermanual", "kw":"Creating a Parameter Template,Parameter Template Management,User Guide", @@ -2552,7 +2772,7 @@ { "uri":"rds_sqlserver_configuration.html", "product_code":"rds", - "code":"256", + "code":"278", "des":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", "doc_type":"usermanual", "kw":"Modifying Parameters,Parameter Template Management,User Guide", @@ -2562,7 +2782,7 @@ { "uri":"rds_sqlserver_08_0042.html", "product_code":"rds", - "code":"257", + "code":"279", "des":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", "doc_type":"usermanual", "kw":"Exporting a Parameter Template,Parameter Template Management,User Guide", @@ -2572,7 +2792,7 @@ { "uri":"rds_10_0103.html", "product_code":"rds", - "code":"258", + "code":"280", "des":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", "doc_type":"usermanual", "kw":"Compare,Comparing Parameter Templates,Parameter Template Management,User Guide", @@ -2582,7 +2802,7 @@ { "uri":"rds_sqlserver_05_0099.html", "product_code":"rds", - "code":"259", + "code":"281", "des":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", "doc_type":"usermanual", "kw":"Viewing Parameter Change History,Parameter Template Management,User Guide", @@ -2592,7 +2812,7 @@ { "uri":"rds_10_0104.html", "product_code":"rds", - "code":"260", + "code":"282", "des":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", "doc_type":"usermanual", "kw":"Replicating a Parameter Template,Parameter Template Management,User Guide", @@ -2602,7 +2822,7 @@ { "uri":"rds_10_0105.html", "product_code":"rds", - "code":"261", + "code":"283", "des":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", "doc_type":"usermanual", "kw":"Resetting a Parameter Template,Parameter Template Management,User Guide", @@ -2612,7 +2832,7 @@ { "uri":"rds_sqlserver_05_0018.html", "product_code":"rds", - "code":"262", + "code":"284", "des":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", "doc_type":"usermanual", "kw":"Applying a Parameter Template,Parameter Template Management,User Guide", @@ -2622,7 +2842,7 @@ { "uri":"rds_sqlserver_05_0098.html", "product_code":"rds", - "code":"263", + "code":"285", "des":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", "doc_type":"usermanual", "kw":"Viewing Application Records of a Parameter Template,Parameter Template Management,User Guide", @@ -2632,7 +2852,7 @@ { "uri":"rds_10_0106.html", "product_code":"rds", - "code":"264", + "code":"286", "des":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", "doc_type":"usermanual", "kw":"Modifying a Parameter Template Description,Parameter Template Management,User Guide", @@ -2642,7 +2862,7 @@ { "uri":"rds_10_0107.html", "product_code":"rds", - "code":"265", + "code":"287", "des":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", "doc_type":"usermanual", "kw":"Deleting a Parameter Template,Parameter Template Management,User Guide", @@ -2652,7 +2872,7 @@ { "uri":"rds_sqlserver_05_0005.html", "product_code":"rds", - "code":"266", + "code":"288", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Connection Management", @@ -2662,7 +2882,7 @@ { "uri":"rds_sqlserver_05_0024.html", "product_code":"rds", - "code":"267", + "code":"289", "des":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", "doc_type":"usermanual", "kw":"change floating IP addresses,self-configured floating IP address,Configuring and Changing a Floating", @@ -2672,7 +2892,7 @@ { "uri":"rds_sqlserver_0025.html", "product_code":"rds", - "code":"268", + "code":"290", "des":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", "doc_type":"usermanual", "kw":"Binding and Unbinding an EIP,Connection Management,User Guide", @@ -2682,7 +2902,7 @@ { "uri":"rds_sqlserver_change_database_port.html", "product_code":"rds", - "code":"269", + "code":"291", "des":"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 pri", "doc_type":"usermanual", "kw":"change the database port of a primary DB instance or a read replica,Changing a Database Port,Connect", @@ -2692,7 +2912,7 @@ { "uri":"rds_sqlserver_05_0006.html", "product_code":"rds", - "code":"270", + "code":"292", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Security", @@ -2702,7 +2922,7 @@ { "uri":"en-us_topic_sqlserver_reset_password.html", "product_code":"rds", - "code":"271", + "code":"293", "des":"You can reset the administrator password only through the primary DB instance.You can also reset the password of your database account when using RDS.If you have changed ", "doc_type":"usermanual", "kw":"reset the administrator password,Resetting the Administrator Password,Data Security,User Guide", @@ -2712,7 +2932,7 @@ { "uri":"rds_11_0032.html", "product_code":"rds", - "code":"272", + "code":"294", "des":"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 pri", "doc_type":"usermanual", "kw":"Changing a Security Group,Data Security,User Guide", @@ -2722,7 +2942,7 @@ { "uri":"rds_11_0004.html", "product_code":"rds", - "code":"273", + "code":"295", "des":"Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively ", "doc_type":"usermanual", "kw":"Configuring the TDE Function,Data Security,User Guide", @@ -2732,7 +2952,7 @@ { "uri":"rds_sqlserver_01_0001.html", "product_code":"rds", - "code":"274", + "code":"296", "des":"The participator, transaction-supported server, resource server, and transaction manager of a distributed transaction are deployed on different nodes in a distributed sys", "doc_type":"usermanual", "kw":"Distributed Transactions,Working with RDS for SQL Server,User Guide", @@ -2742,7 +2962,7 @@ { "uri":"rds_sqlserver_06_0000.html", "product_code":"rds", - "code":"275", + "code":"297", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Metrics and Alarms", @@ -2752,7 +2972,7 @@ { "uri":"rds_sqlserver_06_0001.html", "product_code":"rds", - "code":"276", + "code":"298", "des":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", "doc_type":"usermanual", "kw":"Configuring Displayed Metrics,Metrics and Alarms,User Guide", @@ -2762,7 +2982,7 @@ { "uri":"rds_sqlserver_06_0002.html", "product_code":"rds", - "code":"277", + "code":"299", "des":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", "doc_type":"usermanual", "kw":"alarm rule,Setting Alarm Rules,Metrics and Alarms,User Guide", @@ -2772,7 +2992,7 @@ { "uri":"rds_sqlserver_06_0003.html", "product_code":"rds", - "code":"278", + "code":"300", "des":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", "doc_type":"usermanual", "kw":"Viewing Monitoring Metrics,Metrics and Alarms,User Guide", @@ -2782,7 +3002,7 @@ { "uri":"rds_sqlserver_01_0000.html", "product_code":"rds", - "code":"279", + "code":"301", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Interconnection with CTS", @@ -2792,7 +3012,7 @@ { "uri":"rds_sqlserver_06_0004.html", "product_code":"rds", - "code":"280", + "code":"302", "des":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", "doc_type":"usermanual", "kw":"Cloud Trace Service (CTS),Key Operations Supported by CTS,Interconnection with CTS,User Guide", @@ -2802,7 +3022,7 @@ { "uri":"rds_sqlserver_06_0005.html", "product_code":"rds", - "code":"281", + "code":"303", "des":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", "doc_type":"usermanual", "kw":"Viewing Tracing Events,Interconnection with CTS,User Guide", @@ -2812,7 +3032,7 @@ { "uri":"rds_sqlserver_log.html", "product_code":"rds", - "code":"282", + "code":"304", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -2822,7 +3042,7 @@ { "uri":"rds_sqlserver_01_0002.html", "product_code":"rds", - "code":"283", + "code":"305", "des":"System logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner", "doc_type":"usermanual", "kw":"Viewing System Logs,Log Management,User Guide", @@ -2832,7 +3052,7 @@ { "uri":"slow_query_log-sqlserver.html", "product_code":"rds", - "code":"284", + "code":"306", "des":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details to identify statements that are executing slowly and optimiz", "doc_type":"usermanual", "kw":"Viewing and Downloading Slow Query Logs,Log Management,User Guide", @@ -2842,7 +3062,7 @@ { "uri":"rds_sqlserver_05_0007.html", "product_code":"rds", - "code":"285", + "code":"307", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Task Center", @@ -2852,7 +3072,7 @@ { "uri":"rds_sqlserver_task_0001.html", "product_code":"rds", - "code":"286", + "code":"308", "des":"You can view the progress and results of tasks on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasChanging sin", "doc_type":"usermanual", "kw":"Viewing a Task,Task Center,User Guide", @@ -2862,7 +3082,7 @@ { "uri":"rds_sqlserver_task_0002.html", "product_code":"rds", - "code":"287", + "code":"309", "des":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", "doc_type":"usermanual", "kw":"Deleting a Task Record,Task Center,User Guide", @@ -2872,7 +3092,7 @@ { "uri":"rds_sqlserver_tag.html", "product_code":"rds", - "code":"288", + "code":"310", "des":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", "doc_type":"usermanual", "kw":"Tag Management Service (TMS),Managing Tags,Working with RDS for SQL Server,User Guide", @@ -2882,7 +3102,7 @@ { "uri":"rds_faq_0000.html", "product_code":"rds", - "code":"289", + "code":"311", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -2892,7 +3112,7 @@ { "uri":"rds_faq_0146.html", "product_code":"rds", - "code":"290", + "code":"312", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Product Consulting", @@ -2902,7 +3122,7 @@ { "uri":"rds_faq_0001.html", "product_code":"rds", - "code":"291", + "code":"313", "des":"DB instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.The backup files stored in Object ", "doc_type":"usermanual", "kw":"What Should I Pay Attention to When Using RDS?,Product Consulting,User Guide", @@ -2912,7 +3132,7 @@ { "uri":"rds_faq_0002.html", "product_code":"rds", - "code":"292", + "code":"314", "des":"Calculation formula for RDS DB instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%", "doc_type":"usermanual", "kw":"What Is the Availability of RDS DB Instances?,Product Consulting,User Guide", @@ -2922,7 +3142,7 @@ { "uri":"rds_faq_0003.html", "product_code":"rds", - "code":"293", + "code":"315", "des":"Currently, DB instance cannot be created using a template.", "doc_type":"usermanual", "kw":"Can I Use a Template to Create DB Instances?,Product Consulting,User Guide", @@ -2932,7 +3152,7 @@ { "uri":"rds_faq_0004.html", "product_code":"rds", - "code":"294", + "code":"316", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"What Are the Differences Between RDS and Other Database Solutions?,Product Consulting,User Guide", @@ -2942,7 +3162,7 @@ { "uri":"rds_faq_0005.html", "product_code":"rds", - "code":"295", + "code":"317", "des":"No. Your RDS DB instances and resources are isolated from other users' DB instances.", "doc_type":"usermanual", "kw":"Will My RDS DB Instances Be Affected by Other User Instances?,Product Consulting,User Guide", @@ -2952,7 +3172,7 @@ { "uri":"rds_faq_0073.html", "product_code":"rds", - "code":"296", + "code":"318", "des":"Yes. RDS supports cross-AZ high availability. When you create primary/standby DB instances, you can select different AZs for them.", "doc_type":"usermanual", "kw":"Does RDS Support Cross-AZ High Availability?,Product Consulting,User Guide", @@ -2962,7 +3182,7 @@ { "uri":"rds_faq_0104.html", "product_code":"rds", - "code":"297", + "code":"319", "des":"No. RDS single DB instances can be changed to primary/standby DB instances, but not the other way around.", "doc_type":"usermanual", "kw":"Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?,Product Consulting,User Guid", @@ -2972,7 +3192,7 @@ { "uri":"rds_faq_0110.html", "product_code":"rds", - "code":"298", + "code":"320", "des":"The default code is utf8. You need to convert the default code to Unicode in the exported Excel file.", "doc_type":"usermanual", "kw":"What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Exce", @@ -2982,7 +3202,7 @@ { "uri":"rds_faq_0008.html", "product_code":"rds", - "code":"299", + "code":"321", "des":"To solve this problem:Check the performance of RDS DB instances on the RDS console.Compare the database connection status of local databases and RDS DB instances. This pr", "doc_type":"usermanual", "kw":"What Can I Do About Slow Respond of Websites When They Use RDS?,Product Consulting,User Guide", @@ -2992,7 +3212,7 @@ { "uri":"rds_faq_0065.html", "product_code":"rds", - "code":"300", + "code":"322", "des":"RDS provides the high availability. Select the primary/standby mode.Also called an unplanned handover. If the primary DB instance fails, the system will automatically swi", "doc_type":"usermanual", "kw":"How Does a Cloud Database Perform a Primary/Standby Switchover?,Product Consulting,User Guide", @@ -3002,7 +3222,7 @@ { "uri":"rds_faq_0013.html", "product_code":"rds", - "code":"301", + "code":"323", "des":"Multiple ECSs can connect to the same RDS DB instance as long as the capability limits of a database are not exceeded.", "doc_type":"usermanual", "kw":"Can Multiple ECSs Connect to the Same RDS DB Instance?,Product Consulting,User Guide", @@ -3012,7 +3232,7 @@ { "uri":"rds_faq_0094.html", "product_code":"rds", - "code":"302", + "code":"324", "des":"An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.The database 'xxx", "doc_type":"usermanual", "kw":"Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB ", @@ -3022,7 +3242,7 @@ { "uri":"rds_faq_0145.html", "product_code":"rds", - "code":"303", + "code":"325", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Resource and Disk Management", @@ -3032,7 +3252,7 @@ { "uri":"rds_faq_0049.html", "product_code":"rds", - "code":"304", + "code":"326", "des":"The following logs and files occupy RDS storage space.If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If d", "doc_type":"usermanual", "kw":"scale up storage space,Which Types of Logs and Files Occupy RDS Storage Space?,Resource and Disk Man", @@ -3042,7 +3262,7 @@ { "uri":"rds_faq_0047.html", "product_code":"rds", - "code":"305", + "code":"327", "des":"Both your common data (excluding backup data) and the data required for the operation of your DB instances (such as system database data, rollback logs, redo logs, and in", "doc_type":"usermanual", "kw":"Which Items Occupy the Storage Space of My RDS DB Instances?,Resource and Disk Management,User Guide", @@ -3052,7 +3272,7 @@ { "uri":"rds_faq_0048.html", "product_code":"rds", - "code":"306", + "code":"328", "des":"The storage space you applied for will include space for the file system overhead required for inode, reserved block, and database operations.", "doc_type":"usermanual", "kw":"What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?,Resource and Disk ", @@ -3062,7 +3282,7 @@ { "uri":"rds_faq_0082.html", "product_code":"rds", - "code":"307", + "code":"329", "des":"Data Definition Language (DDL) operations may increase storage space usage sharply. To ensure that services are running properly, do not perform DDL operations during pea", "doc_type":"usermanual", "kw":"How Much Storage Space Is Required for DDL Operations?,Resource and Disk Management,User Guide", @@ -3072,7 +3292,7 @@ { "uri":"rds_faq_0006.html", "product_code":"rds", - "code":"308", + "code":"330", "des":"There are no limitations on the number of DB instances running on RDS.", "doc_type":"usermanual", "kw":"How Many DB Instances Can Run on RDS?,Resource and Disk Management,User Guide", @@ -3082,7 +3302,7 @@ { "uri":"rds_faq_0007.html", "product_code":"rds", - "code":"309", + "code":"331", "des":"The maximum number of databases that can run on an RDS DB instance depends on the DB engine settings.If there are enough CPU, memory, and storage resources, there are no ", "doc_type":"usermanual", "kw":"How Many Databases Can Run on an RDS DB Instance?,Resource and Disk Management,User Guide", @@ -3092,7 +3312,7 @@ { "uri":"rds_faq_0141.html", "product_code":"rds", - "code":"310", + "code":"332", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Connection", @@ -3102,7 +3322,7 @@ { "uri":"rds_faq_0018.html", "product_code":"rds", - "code":"311", + "code":"333", "des":"For a DB instance that has an EIP bound, you can access it through the EIP.Enable a VPN in a VPC and use the VPN to connect to the RDS DB instance.Create an RDS and an EC", "doc_type":"usermanual", "kw":"Can an External Server Access the RDS Database?,Database Connection,User Guide", @@ -3112,7 +3332,7 @@ { "uri":"rds_faq_0019.html", "product_code":"rds", - "code":"312", + "code":"334", "des":"The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of use", "doc_type":"usermanual", "kw":"What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?,Database Connection,", @@ -3122,7 +3342,7 @@ { "uri":"rds_faq_0055.html", "product_code":"rds", - "code":"313", + "code":"335", "des":"RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_", "doc_type":"usermanual", "kw":"What Is the Maximum Number of Connections to an RDS DB Instance?,Database Connection,User Guide", @@ -3132,7 +3352,7 @@ { "uri":"rds_faq_0057.html", "product_code":"rds", - "code":"314", + "code":"336", "des":"For details about how to create an ECS, see the Elastic Cloud Server User Guide.If you connect to an RDS DB instance through a private network, ensure that the ECS and DB", "doc_type":"usermanual", "kw":"How Can I Create and Connect to an ECS?,Database Connection,User Guide", @@ -3142,7 +3362,7 @@ { "uri":"rds_faq_0020.html", "product_code":"rds", - "code":"315", + "code":"337", "des":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC in which the RDS DB insta", "doc_type":"usermanual", "kw":"What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?,Database ", @@ -3152,7 +3372,7 @@ { "uri":"rds_faq_0021.html", "product_code":"rds", - "code":"316", + "code":"338", "des":"Troubleshoot RDS connection failures caused by a client problem by checking the following items:ECS Security PolicyIn Windows, check whether the RDS instance port is enab", "doc_type":"usermanual", "kw":"What Should I Do If a Database Client Problem Causes a Connection Failure?,Database Connection,User ", @@ -3162,7 +3382,7 @@ { "uri":"rds_faq_0022.html", "product_code":"rds", - "code":"317", + "code":"339", "des":"Check whether any of the following problems occurred on the RDS DB instance.The RDS DB instance is not properly connected.Solution: Check the connection. If you connect t", "doc_type":"usermanual", "kw":"What Should I Do If an RDS Database Problem Causes a Connection Failure?,Database Connection,User Gu", @@ -3172,7 +3392,7 @@ { "uri":"rds_faq_0023.html", "product_code":"rds", - "code":"318", + "code":"340", "des":"Ensure that the ECS in which your applications are located is in the same VPC as the RDS DB instance. If the ECS and the RDS DB instance are in different VPCs, modify the", "doc_type":"usermanual", "kw":"How Do My Applications Access an RDS DB Instance in a VPC?,Database Connection,User Guide", @@ -3182,7 +3402,7 @@ { "uri":"rds_faq_0024.html", "product_code":"rds", - "code":"319", + "code":"341", "des":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", "doc_type":"usermanual", "kw":"Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?,Database Connecti", @@ -3192,7 +3412,7 @@ { "uri":"rds_faq_0050.html", "product_code":"rds", - "code":"320", + "code":"342", "des":"Although the SSL certificate is optional if you choose to connect to a database through Java database connectivity (JDBC), download an SSL certificate to encrypt the conn", "doc_type":"usermanual", "kw":"How Can I Connect to a PostgreSQL Database Through JDBC?,Database Connection,User Guide", @@ -3202,7 +3422,7 @@ { "uri":"rds_faq_0100.html", "product_code":"rds", - "code":"321", + "code":"343", "des":"Check whether the ECS can connect to the RDS DB instance.If the ECS cannot connect to the RDS DB instance, check whether the ECS and RDS DB instance are located in the sa", "doc_type":"usermanual", "kw":"What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?,Database Connect", @@ -3212,7 +3432,7 @@ { "uri":"rds_faq_0101.html", "product_code":"rds", - "code":"322", + "code":"344", "des":"By default, RDS DB instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. ", "doc_type":"usermanual", "kw":"Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?,Database Connection,User", @@ -3222,7 +3442,7 @@ { "uri":"rds_faq_0111.html", "product_code":"rds", - "code":"323", + "code":"345", "des":"For DB instances connected using SSL, a primary/standby switchover or failover does not interrupt the connection because the SSL certificate is still valid for both the p", "doc_type":"usermanual", "kw":"Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?,Da", @@ -3232,7 +3452,7 @@ { "uri":"rds_faq_0070.html", "product_code":"rds", - "code":"324", + "code":"346", "des":"MySQL supports SSL connections. Different from other vendors, RDS for MySQL enables the SSL connection on the database server by default. When you use a client to connect", "doc_type":"usermanual", "kw":"Does MySQL Support SSL Connections?,Database Connection,User Guide", @@ -3242,7 +3462,7 @@ { "uri":"rds_faq_0034.html", "product_code":"rds", - "code":"325", + "code":"347", "des":"You may have restored from a backup before you reset the administrator password.Check whether the DB instance was restored after you reset the administrator password.Log ", "doc_type":"usermanual", "kw":"Why Did the New Password Not Take Effect After I Reset the Administrator Password?,Database Connecti", @@ -3252,7 +3472,7 @@ { "uri":"rds_faq_0155.html", "product_code":"rds", - "code":"326", + "code":"348", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Migration", @@ -3262,7 +3482,7 @@ { "uri":"rds_faq_0026.html", "product_code":"rds", - "code":"327", + "code":"349", "des":"The mysqldump or pg_dump tool is easy to use for data migration. However, when you use this tool, the server is stopped for a long period of time during data migration. O", "doc_type":"usermanual", "kw":"Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?,Database Migration,User Guide", @@ -3272,7 +3492,7 @@ { "uri":"rds_faq_0025.html", "product_code":"rds", - "code":"328", + "code":"350", "des":"Exporting or importing data between DB engines of the same type is called homogeneous database export or import.Exporting or importing data between DB engines of differen", "doc_type":"usermanual", "kw":"What Types of DB Engines Does RDS Support for Importing Data?,Database Migration,User Guide", @@ -3282,7 +3502,7 @@ { "uri":"rds_faq_0154.html", "product_code":"rds", - "code":"329", + "code":"351", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Permission", @@ -3292,7 +3512,7 @@ { "uri":"rds_faq_0075.html", "product_code":"rds", - "code":"330", + "code":"352", "des":"Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands", "doc_type":"usermanual", "kw":"Why Does the Root User Not Have the Super Permissions?,Database Permission,User Guide", @@ -3302,7 +3522,7 @@ { "uri":"rds_faq_0144.html", "product_code":"rds", - "code":"331", + "code":"353", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Storage", @@ -3312,7 +3532,7 @@ { "uri":"rds_faq_0041.html", "product_code":"rds", - "code":"332", + "code":"354", "des":"The database storage engine is a core service for storing, processing, and protecting data. It can be used to control access permissions and rapidly process transactions ", "doc_type":"usermanual", "kw":"What Storage Engines Does the RDS for MySQL Support?,Database Storage,User Guide", @@ -3322,7 +3542,7 @@ { "uri":"rds_faq_0045.html", "product_code":"rds", - "code":"333", + "code":"355", "des":"RDS uses Elastic Volume Service (EVS) disks for storage. For details about EVS disks, see Elastic Volume Service Product Introduction.The RDS backup data is stored in OBS", "doc_type":"usermanual", "kw":"What Is the RDS DB Instance Storage Configuration?,Database Storage,User Guide", @@ -3332,7 +3552,7 @@ { "uri":"rds_faq_0076.html", "product_code":"rds", - "code":"334", + "code":"356", "des":"No. After an RDS DB instance is created, the storage type cannot be changed.", "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", @@ -3342,7 +3562,7 @@ { "uri":"rds_faq_0046.html", "product_code":"rds", - "code":"335", + "code":"357", "des":"There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the dat", "doc_type":"usermanual", "kw":"What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?,Database Storage,Us", @@ -3352,7 +3572,7 @@ { "uri":"rds_faq_0152.html", "product_code":"rds", - "code":"336", + "code":"358", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Client Installation", @@ -3362,7 +3582,7 @@ { "uri":"rds_faq_0027.html", "product_code":"rds", - "code":"337", + "code":"359", "des":"MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package", "doc_type":"usermanual", "kw":"How Can I Install the MySQL Client?,Client Installation,User Guide", @@ -3372,8 +3592,8 @@ { "uri":"rds_faq_0029.html", "product_code":"rds", - "code":"338", - "des":"PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.Ensure that the database clien", + "code":"360", + "des":"PostgreSQL provides client installation methods for different OSs on its official website.The following describes how to install a PostgreSQL 12 client in CentOS.When you", "doc_type":"usermanual", "kw":"How Can I Install the PostgreSQL Client?,Client Installation,User Guide", "title":"How Can I Install the PostgreSQL Client?", @@ -3382,7 +3602,7 @@ { "uri":"rds_faq_0032.html", "product_code":"rds", - "code":"339", + "code":"361", "des":"The Microsoft SQL Server official website provides the SQL Server Management Studio installation package. SQL Server Management Studio applications can run in the Windows", "doc_type":"usermanual", "kw":"How Can I Install SQL Server Management Studio?,Client Installation,User Guide", @@ -3392,7 +3612,7 @@ { "uri":"rds_faq_0098.html", "product_code":"rds", - "code":"340", + "code":"362", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Backup and Restoration", @@ -3402,7 +3622,7 @@ { "uri":"rds_faq_0043.html", "product_code":"rds", - "code":"341", + "code":"363", "des":"Automated backup data is kept based on the backup retention period you specified. There is no limit for the manual backup retention period. You can delete manual backups ", "doc_type":"usermanual", "kw":"How Long Does RDS Store Backup Data For?,Backup and Restoration,User Guide", @@ -3412,7 +3632,7 @@ { "uri":"rds_faq_0044.html", "product_code":"rds", - "code":"342", + "code":"364", "des":"A backup window is a user-specified time during which RDS DB instances are backed up. With these periodic data backups, RDS allows you to restore DB instances to the back", "doc_type":"usermanual", "kw":"Can My Database Be Used in the Backup Window?,Backup and Restoration,User Guide", @@ -3422,7 +3642,7 @@ { "uri":"rds_faq_0042.html", "product_code":"rds", - "code":"343", + "code":"365", "des":"You can back up data to an ECS the same way you export SQL statements. The ECS service does not have restrictions on the types of data to be backed up as long as the data", "doc_type":"usermanual", "kw":"How Can I Back Up an RDS Database to an ECS?,Backup and Restoration,User Guide", @@ -3432,7 +3652,7 @@ { "uri":"rds_faq_0053.html", "product_code":"rds", - "code":"344", + "code":"366", "des":"Automated backups may fail for the following reasons:The network environment is unstable due to issues such as network delay or interruption. RDS will detect these proble", "doc_type":"usermanual", "kw":"Why Has My Automated Backup Failed?,Backup and Restoration,User Guide", @@ -3442,7 +3662,7 @@ { "uri":"rds_faq_0014.html", "product_code":"rds", - "code":"345", + "code":"367", "des":"When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.", "doc_type":"usermanual", "kw":"What Happens to Database Backups After an RDS DB Instance Is Deleted?,Backup and Restoration,User Gu", @@ -3452,7 +3672,7 @@ { "uri":"rds_faq_0015.html", "product_code":"rds", - "code":"346", + "code":"368", "des":"If your cloud account is deleted, both your automated and manual backups are deleted.", "doc_type":"usermanual", "kw":"Will My Backups Be Deleted If I Delete My Cloud Account?,Backup and Restoration,User Guide", @@ -3462,7 +3682,7 @@ { "uri":"rds_faq_0012.html", "product_code":"rds", - "code":"347", + "code":"369", "des":"RDS does not delete or perform any operations on any user data. If this problem occurs, check if there have been any misoperations and restore the data from backup files,", "doc_type":"usermanual", "kw":"Why Is a Table or Data Missing from My Database?,Backup and Restoration,User Guide", @@ -3472,7 +3692,7 @@ { "uri":"rds_faq_0151.html", "product_code":"rds", - "code":"348", + "code":"370", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Monitoring", @@ -3482,7 +3702,7 @@ { "uri":"rds_faq_0036.html", "product_code":"rds", - "code":"349", + "code":"371", "des":"You need to pay attention to CPU, memory, and storage space usage.You can configure the system to report alarms based on service requirements and take measures to handle ", "doc_type":"usermanual", "kw":"Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?,Database Monitoring,User Guide", @@ -3492,7 +3712,7 @@ { "uri":"rds_faq_0150.html", "product_code":"rds", - "code":"350", + "code":"372", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Capacity Expansion and Specification Change", @@ -3502,7 +3722,7 @@ { "uri":"rds_faq_0016.html", "product_code":"rds", - "code":"351", + "code":"373", "des":"Currently, you can scale up storage space and change the CPU or memory of a DB instance.When storage space is being scaled up, RDS DB instances are still available and se", "doc_type":"usermanual", "kw":"Are My RDS DB Instances Available When Scaling?,Capacity Expansion and Specification Change,User Gui", @@ -3512,7 +3732,7 @@ { "uri":"rds_faq_0035.html", "product_code":"rds", - "code":"352", + "code":"374", "des":"The DB instance is in Faulty state after the original database port is changed.The DB instance cannot be connected using the new database port.The submitted database port", "doc_type":"usermanual", "kw":"Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?,Capacity Expansi", @@ -3522,7 +3742,7 @@ { "uri":"rds_faq_0142.html", "product_code":"rds", - "code":"353", + "code":"375", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Database Parameter Modification", @@ -3532,7 +3752,7 @@ { "uri":"rds_faq_0031.html", "product_code":"rds", - "code":"354", + "code":"376", "des":"In the following cases, inappropriate parameter settings cause the database to be unavailable:Parameter value ranges are related to DB instance specifications.The maximum", "doc_type":"usermanual", "kw":"What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?,Database Para", @@ -3542,7 +3762,7 @@ { "uri":"rds_faq_0119.html", "product_code":"rds", - "code":"355", + "code":"377", "des":"PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_", "doc_type":"usermanual", "kw":"Does RDS for PostgreSQL Support the test_decoding Plugin?,Database Parameter Modification,User Guide", @@ -3552,7 +3772,7 @@ { "uri":"rds_faq_0092.html", "product_code":"rds", - "code":"356", + "code":"378", "des":"When you add NDF files of the custom database and the tempdb database, do not place them in the C drive. If you place them in the C drive, the system disk space will be u", "doc_type":"usermanual", "kw":"Where Should I Store the NDF Files for Microsoft SQL Server?,Database Parameter Modification,User Gu", @@ -3562,7 +3782,7 @@ { "uri":"rds_faq_0149.html", "product_code":"rds", - "code":"357", + "code":"379", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Log Management", @@ -3572,7 +3792,7 @@ { "uri":"rds_faq_0078.html", "product_code":"rds", - "code":"358", + "code":"380", "des":"Generally, the delay is 5 minutes. If the size of slow query logs reaches 10 MB within 5 minutes, the logs will be uploaded to OBS.", "doc_type":"usermanual", "kw":"How Long Is the Delay for RDS MySQL Slow Query Logs?,Log Management,User Guide", @@ -3582,7 +3802,7 @@ { "uri":"rds_faq_0077.html", "product_code":"rds", - "code":"359", + "code":"381", "des":"The slow query threshold is 5 seconds.", "doc_type":"usermanual", "kw":"What's the Slow Query Threshold for Microsoft SQL Server?,Log Management,User Guide", @@ -3592,7 +3812,7 @@ { "uri":"rds_faq_0059.html", "product_code":"rds", - "code":"360", + "code":"382", "des":"EXECUTE master.dbo.rds_read_errorlogFileID,LogType,FilterText,FilterBeginTime,FilterEndTimeFileID: indicates the ID of an error log. The value 0 indicates the latest logs", "doc_type":"usermanual", "kw":"How Can I Obtain Microsoft SQL Server Error Logs Using Commands?,Log Management,User Guide", @@ -3602,7 +3822,7 @@ { "uri":"rds_faq_0120.html", "product_code":"rds", - "code":"361", + "code":"383", "des":"Sorry, statistics on RDS slow query logs cannot be exported.", "doc_type":"usermanual", "kw":"Can I Export Statistics on RDS Slow Query Logs?,Log Management,User Guide", @@ -3612,7 +3832,7 @@ { "uri":"rds_faq_0143.html", "product_code":"rds", - "code":"362", + "code":"384", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Network Security", @@ -3622,7 +3842,7 @@ { "uri":"rds_faq_0038.html", "product_code":"rds", - "code":"363", + "code":"385", "des":"RDS runs your DB instances in a VPC, ensuring that the DB instances are isolated from other services.RDS uses security groups to ensure that only trusted sources can acce", "doc_type":"usermanual", "kw":"What Security Protection Policies Does RDS Have?,Network Security,User Guide", @@ -3632,7 +3852,7 @@ { "uri":"rds_faq_0040.html", "product_code":"rds", - "code":"364", + "code":"386", "des":"The VPC security group helps ensure the security of RDS in a VPC. In addition, an ACL can be used to allow or reject I/O network traffic for each subnet.", "doc_type":"usermanual", "kw":"How Can I Ensure the Security of RDS DB Instances in a VPC?,Network Security,User Guide", @@ -3642,7 +3862,7 @@ { "uri":"rds_faq_0039.html", "product_code":"rds", - "code":"365", + "code":"387", "des":"When you access RDS through an EIP, service data will be transmitted on the public network. To prevent any potential data breaches, you are advised to use SSL to encrypt ", "doc_type":"usermanual", "kw":"How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?,Network Secur", @@ -3652,7 +3872,7 @@ { "uri":"rds_faq_0056.html", "product_code":"rds", - "code":"366", + "code":"388", "des":"If you enable public accessibility, your EIP DNS and database port may be vulnerable to hacking. To protect information such as your EIP, DNS, database port, database acc", "doc_type":"usermanual", "kw":"How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?,Network Security,User Guide", @@ -3662,7 +3882,7 @@ { "uri":"rds_faq_0054.html", "product_code":"rds", - "code":"367", + "code":"389", "des":"When you attempt to connect to a DB instance through a private network, check whether the ECS and RDS DB instance are in the same security group.If the ECS and RDS DB ins", "doc_type":"usermanual", "kw":"How Do I Configure a Security Group to Enable Access to RDS DB Instances?,Network Security,User Guid", @@ -3672,7 +3892,7 @@ { "uri":"rds_faq_0052.html", "product_code":"rds", - "code":"368", + "code":"390", "des":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", "doc_type":"usermanual", "kw":"How Can I Import the Root Certificate to a Windows or Linux OS?,Network Security,User Guide", @@ -3682,7 +3902,7 @@ { "uri":"rds_faq_0051.html", "product_code":"rds", - "code":"369", + "code":"391", "des":"When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:Update the root certificate t", "doc_type":"usermanual", "kw":"How Can I Identify the Validity Period of an SSL Root Certificate?,Network Security,User Guide", @@ -3692,7 +3912,7 @@ { "uri":"rds_faq_0011.html", "product_code":"rds", - "code":"370", + "code":"392", "des":"Data tamperingLots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database ta", "doc_type":"usermanual", "kw":"How Can I Identify Data Corruption?,Network Security,User Guide", @@ -3700,9 +3920,9 @@ "githuburl":"" }, { - "uri":"en-us_topic_0000001419863378.html", + "uri":"en-us_topic_0000001191146839.html", "product_code":"rds", - "code":"371", + "code":"393", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", @@ -3712,7 +3932,7 @@ { "uri":"rds_glossary_0001.html", "product_code":"rds", - "code":"372", + "code":"394", "des":"For details about the glossaries in this document, see Glossary.", "doc_type":"usermanual", "kw":"Glossary,User Guide", diff --git a/docs/rds/umn/CLASS.TXT.json b/docs/rds/umn/CLASS.TXT.json index f748c1c7..b3d43cb2 100644 --- a/docs/rds/umn/CLASS.TXT.json +++ b/docs/rds/umn/CLASS.TXT.json @@ -153,7 +153,7 @@ "code":"17" }, { - "desc":"RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.For", + "desc":"RDS for MySQL, RDS for PostgreSQL, RDS for SQL Server 2019 Enterprise Edition, and 2017 Enterprise Edition DB instances support read replicas to offload read traffic from", "product_code":"rds", "title":"Read/Write Splitting", "uri":"rds_01_0012.html", @@ -171,10 +171,10 @@ "code":"19" }, { - "desc":"RDS provides two types of user permissions by default: user management and resource management.User management permissions cover the management of users, user groups, and", + "desc":"If you need to assign different permissions to employees in your enterprise to access your RDS resources, Identity and Access Management (IAM) is a good choice for fine-g", "product_code":"rds", - "title":"User Permissions", - "uri":"rds_01_0025.html", + "title":"Permissions Management", + "uri":"rds_01_0017.html", "doc_type":"usermanual", "p_code":"1", "code":"20" @@ -665,6 +665,33 @@ "p_code":"73", "code":"74" }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Permissions Management", + "uri":"rds_07_0000.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"75" + }, + { + "desc":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", + "product_code":"rds", + "title":"Creating a User and Granting Permissions", + "uri":"rds_07_0002.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"76" + }, + { + "desc":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", + "product_code":"rds", + "title":"RDS Custom Policies", + "uri":"rds_07_0003.html", + "doc_type":"usermanual", + "p_code":"75", + "code":"77" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"rds", @@ -672,7 +699,7 @@ "uri":"rds_05_0000.html", "doc_type":"usermanual", "p_code":"70", - "code":"75" + "code":"78" }, { "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", @@ -680,8 +707,8 @@ "title":"Creating a Same DB Instance as an Existing DB Instance", "uri":"rds_05_0055.html", "doc_type":"usermanual", - "p_code":"75", - "code":"76" + "p_code":"78", + "code":"79" }, { "desc":"If you use DB instances only for routine development, you can temporarily stop pay-per-use DB instances to save money. You can stop a DB instance for up to seven days.If ", @@ -689,8 +716,8 @@ "title":"Stopping a DB Instance", "uri":"rds_05_0057.html", "doc_type":"usermanual", - "p_code":"75", - "code":"77" + "p_code":"78", + "code":"80" }, { "desc":"You can stop your DB instance temporarily to save money. After stopping your DB instance, you can restart it to begin using it again.If you start a primary DB instance, r", @@ -698,8 +725,8 @@ "title":"Starting a DB Instance", "uri":"rds_05_0058.html", "doc_type":"usermanual", - "p_code":"75", - "code":"78" + "p_code":"78", + "code":"81" }, { "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", @@ -707,8 +734,8 @@ "title":"Rebooting DB Instances or Read Replicas", "uri":"rds_08_0013.html", "doc_type":"usermanual", - "p_code":"75", - "code":"79" + "p_code":"78", + "code":"82" }, { "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", @@ -716,8 +743,8 @@ "title":"Selecting Displayed Items", "uri":"rds_08_0022.html", "doc_type":"usermanual", - "p_code":"75", - "code":"80" + "p_code":"78", + "code":"83" }, { "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", @@ -725,8 +752,8 @@ "title":"Exporting DB Instance Information", "uri":"rds_05_0017.html", "doc_type":"usermanual", - "p_code":"75", - "code":"81" + "p_code":"78", + "code":"84" }, { "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", @@ -734,8 +761,8 @@ "title":"Deleting a DB Instance or Read Replica", "uri":"rds_08_0002.html", "doc_type":"usermanual", - "p_code":"75", - "code":"82" + "p_code":"78", + "code":"85" }, { "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", @@ -743,8 +770,8 @@ "title":"Recycling a DB Instance", "uri":"rds_mysql_recycle.html", "doc_type":"usermanual", - "p_code":"75", - "code":"83" + "p_code":"78", + "code":"86" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -753,7 +780,7 @@ "uri":"rds_05_0001.html", "doc_type":"usermanual", "p_code":"70", - "code":"84" + "code":"87" }, { "desc":"RDS for MySQL supports minor version upgrades to improve performance, add new functions, and fix bugs.The upgrade will cause the DB instance to reboot and interrupt servi", @@ -761,8 +788,8 @@ "title":"Upgrading a Minor Version", "uri":"rds_05_0003.html", "doc_type":"usermanual", - "p_code":"84", - "code":"85" + "p_code":"87", + "code":"88" }, { "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", @@ -770,8 +797,8 @@ "title":"Changing a DB Instance Name", "uri":"rds_modify_instance_name.html", "doc_type":"usermanual", - "p_code":"84", - "code":"86" + "p_code":"87", + "code":"89" }, { "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", @@ -779,8 +806,8 @@ "title":"Changing the Failover Priority", "uri":"rds_modify_availability.html", "doc_type":"usermanual", - "p_code":"84", - "code":"87" + "p_code":"87", + "code":"90" }, { "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", @@ -788,8 +815,8 @@ "title":"Changing a DB Instance Class", "uri":"en-us_topic_scale_rds.html", "doc_type":"usermanual", - "p_code":"84", - "code":"88" + "p_code":"87", + "code":"91" }, { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If your storage space usage reaches up to 95% for a disk l", @@ -797,8 +824,17 @@ "title":"Scaling up Storage Space", "uri":"en-us_topic_scale_cluster.html", "doc_type":"usermanual", - "p_code":"84", - "code":"89" + "p_code":"87", + "code":"92" + }, + { + "desc":"With storage autoscaling enabled, when RDS detects that you are running out of database space, it automatically scales up your storage.Autoscaling up the storage of a rea", + "product_code":"rds", + "title":"Storage Autoscaling", + "uri":"rds_05_0039.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"93" }, { "desc":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", @@ -806,8 +842,8 @@ "title":"Changing the Maintenance Window", "uri":"rds_05_0038.html", "doc_type":"usermanual", - "p_code":"84", - "code":"90" + "p_code":"87", + "code":"94" }, { "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the ", @@ -815,8 +851,8 @@ "title":"Changing a DB Instance Type from Single to Primary/Standby", "uri":"rds_05_0023.html", "doc_type":"usermanual", - "p_code":"84", - "code":"91" + "p_code":"87", + "code":"95" }, { "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", @@ -824,8 +860,17 @@ "title":"Manually Switching Between Primary and Standby DB Instances", "uri":"rds_switch_ha.html", "doc_type":"usermanual", - "p_code":"84", - "code":"92" + "p_code":"87", + "code":"96" + }, + { + "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.6, 5.7, or 8.0 support standby instanc", + "product_code":"rds", + "title":"Migrating a Standby DB Instance", + "uri":"rds_05_0060.html", + "doc_type":"usermanual", + "p_code":"87", + "code":"97" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -834,7 +879,7 @@ "uri":"rds_11_0011.html", "doc_type":"usermanual", "p_code":"70", - "code":"93" + "code":"98" }, { "desc":"RDS for MySQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. ", @@ -842,8 +887,8 @@ "title":"Introducing Read Replicas", "uri":"rds_11_0012.html", "doc_type":"usermanual", - "p_code":"93", - "code":"94" + "p_code":"98", + "code":"99" }, { "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After DB instances are created, you can create read replicas for them.", @@ -851,8 +896,8 @@ "title":"Creating a Read Replica", "uri":"en-us_topic_add_read_replica.html", "doc_type":"usermanual", - "p_code":"93", - "code":"95" + "p_code":"98", + "code":"100" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -860,8 +905,8 @@ "title":"Managing a Read Replica", "uri":"rds_11_0015.html", "doc_type":"usermanual", - "p_code":"93", - "code":"96" + "p_code":"98", + "code":"101" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -870,7 +915,7 @@ "uri":"rds_05_0034.html", "doc_type":"usermanual", "p_code":"70", - "code":"97" + "code":"102" }, { "desc":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", @@ -878,8 +923,8 @@ "title":"Working with Backups", "uri":"en-us_topic_backup_restore.html", "doc_type":"usermanual", - "p_code":"97", - "code":"98" + "p_code":"102", + "code":"103" }, { "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", @@ -887,8 +932,8 @@ "title":"Configuring an Automated Backup Policy", "uri":"rds_08_0004.html", "doc_type":"usermanual", - "p_code":"97", - "code":"99" + "p_code":"102", + "code":"104" }, { "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", @@ -896,8 +941,8 @@ "title":"Creating a Manual Backup", "uri":"rds_08_0005.html", "doc_type":"usermanual", - "p_code":"97", - "code":"100" + "p_code":"102", + "code":"105" }, { "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for MySQL enables you to download ", @@ -905,8 +950,8 @@ "title":"Downloading a Backup File", "uri":"rds_08_0006.html", "doc_type":"usermanual", - "p_code":"97", - "code":"101" + "p_code":"102", + "code":"106" }, { "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 ", @@ -914,8 +959,8 @@ "title":"Downloading a Binlog Backup File", "uri":"rds_03_0100.html", "doc_type":"usermanual", - "p_code":"97", - "code":"102" + "p_code":"102", + "code":"107" }, { "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", @@ -923,8 +968,8 @@ "title":"Restoring from Backup Files to DB Instances", "uri":"rds_08_0007.html", "doc_type":"usermanual", - "p_code":"97", - "code":"103" + "p_code":"102", + "code":"108" }, { "desc":"You can download backup files by referring to Downloading a Backup File and restore data from them.Backup data cannot be restored to local databases that run the Windows ", @@ -932,8 +977,8 @@ "title":"Restoring from Backup Files to a Self-Built MySQL Database", "uri":"rds_08_0044.html", "doc_type":"usermanual", - "p_code":"97", - "code":"104" + "p_code":"102", + "code":"109" }, { "desc":"You can restore from automated backups to a specified point in time.RDS for MySQL supports restoration to a new, the original, or an existing DB instance.When you enter t", @@ -941,8 +986,8 @@ "title":"Restoring a DB Instance to a Point in Time", "uri":"rds_08_0008.html", "doc_type":"usermanual", - "p_code":"97", - "code":"105" + "p_code":"102", + "code":"110" }, { "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", @@ -950,8 +995,8 @@ "title":"Replicating a Backup", "uri":"rds_08_0009.html", "doc_type":"usermanual", - "p_code":"97", - "code":"106" + "p_code":"102", + "code":"111" }, { "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", @@ -959,8 +1004,8 @@ "title":"Deleting a Manual Backup", "uri":"rds_08_0010.html", "doc_type":"usermanual", - "p_code":"97", - "code":"107" + "p_code":"102", + "code":"112" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -969,7 +1014,7 @@ "uri":"rds_08_0011.html", "doc_type":"usermanual", "p_code":"70", - "code":"108" + "code":"113" }, { "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", @@ -977,8 +1022,8 @@ "title":"Creating a Parameter Template", "uri":"en-us_topic_parameter_group.html", "doc_type":"usermanual", - "p_code":"108", - "code":"109" + "p_code":"113", + "code":"114" }, { "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", @@ -986,8 +1031,8 @@ "title":"Modifying Parameters", "uri":"rds_configuration.html", "doc_type":"usermanual", - "p_code":"108", - "code":"110" + "p_code":"113", + "code":"115" }, { "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", @@ -995,8 +1040,8 @@ "title":"Exporting a Parameter Template", "uri":"rds_08_0042.html", "doc_type":"usermanual", - "p_code":"108", - "code":"111" + "p_code":"113", + "code":"116" }, { "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", @@ -1004,8 +1049,8 @@ "title":"Comparing Parameter Templates", "uri":"rds_08_0012.html", "doc_type":"usermanual", - "p_code":"108", - "code":"112" + "p_code":"113", + "code":"117" }, { "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", @@ -1013,8 +1058,8 @@ "title":"Viewing Parameter Change History", "uri":"rds_05_0099.html", "doc_type":"usermanual", - "p_code":"108", - "code":"113" + "p_code":"113", + "code":"118" }, { "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", @@ -1022,8 +1067,8 @@ "title":"Replicating a Parameter Template", "uri":"rds_08_0014.html", "doc_type":"usermanual", - "p_code":"108", - "code":"114" + "p_code":"113", + "code":"119" }, { "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", @@ -1031,8 +1076,8 @@ "title":"Resetting a Parameter Template", "uri":"rds_08_0015.html", "doc_type":"usermanual", - "p_code":"108", - "code":"115" + "p_code":"113", + "code":"120" }, { "desc":"You can apply parameter templates to DB instances as needed.The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications ha", @@ -1040,8 +1085,8 @@ "title":"Applying a Parameter Template", "uri":"rds_05_0018.html", "doc_type":"usermanual", - "p_code":"108", - "code":"116" + "p_code":"113", + "code":"121" }, { "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", @@ -1049,8 +1094,8 @@ "title":"Viewing Application Records of a Parameter Template", "uri":"rds_05_0098.html", "doc_type":"usermanual", - "p_code":"108", - "code":"117" + "p_code":"113", + "code":"122" }, { "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", @@ -1058,8 +1103,8 @@ "title":"Modifying a Parameter Template Description", "uri":"rds_08_0016.html", "doc_type":"usermanual", - "p_code":"108", - "code":"118" + "p_code":"113", + "code":"123" }, { "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", @@ -1067,8 +1112,8 @@ "title":"Deleting a Parameter Template", "uri":"rds_08_0017.html", "doc_type":"usermanual", - "p_code":"108", - "code":"119" + "p_code":"113", + "code":"124" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1077,7 +1122,7 @@ "uri":"rds_05_0005.html", "doc_type":"usermanual", "p_code":"70", - "code":"120" + "code":"125" }, { "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", @@ -1085,8 +1130,8 @@ "title":"Configuring and Changing a Floating IP Address", "uri":"rds_05_0024.html", "doc_type":"usermanual", - "p_code":"120", - "code":"121" + "p_code":"125", + "code":"126" }, { "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", @@ -1094,8 +1139,8 @@ "title":"Binding and Unbinding an EIP", "uri":"rds_public_accessibility.html", "doc_type":"usermanual", - "p_code":"120", - "code":"122" + "p_code":"125", + "code":"127" }, { "desc":"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 pri", @@ -1103,8 +1148,8 @@ "title":"Changing a Database Port", "uri":"rds_change_database_port.html", "doc_type":"usermanual", - "p_code":"120", - "code":"123" + "p_code":"125", + "code":"128" }, { "desc":"A security group is a collection of access control rules for ECSs and RDS DB instances that have the same security protection requirements and are mutually trusted in a V", @@ -1112,8 +1157,125 @@ "title":"Configuring a Security Group Rule", "uri":"rds_11_0009.html", "doc_type":"usermanual", - "p_code":"120", - "code":"124" + "p_code":"125", + "code":"129" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Database Proxy (Read/Write Splitting)", + "uri":"rds_11_0050.html", + "doc_type":"usermanual", + "p_code":"70", + "code":"130" + }, + { + "desc":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read rep", + "product_code":"rds", + "title":"Introducing Read/Write Splitting", + "uri":"rds_11_0035.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"131" + }, + { + "desc":"In most cases, an RDS for MySQL proxy instance sends all requests in transactions to the primary DB instance to ensure transaction correctness. However, in some framework", + "product_code":"rds", + "title":"Configuring Transaction Splitting", + "uri":"rds_11_0047.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"132" + }, + { + "desc":"Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. This section describes how to enable read/write sp", + "product_code":"rds", + "title":"Enabling Read/Write Splitting", + "uri":"rds_11_0017.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"133" + }, + { + "desc":"After read/write splitting is enabled, you can configure the delay threshold and routing policy as required.The system automatically distributes weights to read replicas,", + "product_code":"rds", + "title":"Configuring the Delay Threshold and Routing Policy", + "uri":"rds_11_0018.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"134" + }, + { + "desc":"After read/write splitting is enabled, you can change the read/write splitting address.Changing the read/write splitting address will interrupt database connections and s", + "product_code":"rds", + "title":"Changing the Read/Write Splitting Address", + "uri":"rds_11_0026.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"135" + }, + { + "desc":"You can change the instance class (vCPU or memory) of a DB proxy instance as required. If the DB instance status changes from Changing proxy instance class to Available, ", + "product_code":"rds", + "title":"Changing the Instance Class of a DB Proxy Instance", + "uri":"rds_11_0028.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"136" + }, + { + "desc":"After read/write splitting is enabled, you can change the number of proxy nodes as required.Read/write splitting has been enabled.The primary DB instance, read replicas, ", + "product_code":"rds", + "title":"Changing the Number of Proxy Nodes", + "uri":"rds_11_0045.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"137" + }, + { + "desc":"You can manually upgrade the RDS for MySQL database proxy to the latest kernel version to improve performance, add new functions, and fix problems.Intermittent disconnect", + "product_code":"rds", + "title":"Upgrading the Kernel Version of Database Proxy", + "uri":"rds_11_0024.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"138" + }, + { + "desc":"If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant ", + "product_code":"rds", + "title":"Enabling or Disabling Access Control", + "uri":"rds_11_0025.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"139" + }, + { + "desc":"You can disable read/write splitting as required.If the database proxy is disabled, read/write splitting is also disabled and services using the read/write splitting addr", + "product_code":"rds", + "title":"Disabling Read/Write Splitting", + "uri":"rds_11_0019.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"140" + }, + { + "desc":"This section describes the rules of distributing read weights to DB instances of different specifications.When the system automatically sets the read weights for DB insta", + "product_code":"rds", + "title":"Rules for Distributing Weights", + "uri":"rds_11_0020.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"141" + }, + { + "desc":"After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write split", + "product_code":"rds", + "title":"Testing Read/Write Splitting Performance", + "uri":"rds_11_0021.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"142" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1122,7 +1284,7 @@ "uri":"rds_05_0006.html", "doc_type":"usermanual", "p_code":"70", - "code":"125" + "code":"143" }, { "desc":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", @@ -1130,8 +1292,8 @@ "title":"Resetting the Administrator Password", "uri":"rds_reset_password.html", "doc_type":"usermanual", - "p_code":"125", - "code":"126" + "p_code":"143", + "code":"144" }, { "desc":"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 pri", @@ -1139,8 +1301,8 @@ "title":"Changing a Security Group", "uri":"rds_08_0003.html", "doc_type":"usermanual", - "p_code":"125", - "code":"127" + "p_code":"143", + "code":"145" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1149,7 +1311,7 @@ "uri":"rds_08_0019.html", "doc_type":"usermanual", "p_code":"70", - "code":"128" + "code":"146" }, { "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the RDS metrics that can be monitored by Cloud Eye as well as their na", @@ -1157,8 +1319,8 @@ "title":"Configuring Displayed Metrics", "uri":"rds_06_0001.html", "doc_type":"usermanual", - "p_code":"128", - "code":"129" + "p_code":"146", + "code":"147" }, { "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", @@ -1166,8 +1328,8 @@ "title":"Setting Alarm Rules", "uri":"rds_06_0002.html", "doc_type":"usermanual", - "p_code":"128", - "code":"130" + "p_code":"146", + "code":"148" }, { "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", @@ -1175,8 +1337,8 @@ "title":"Viewing Monitoring Metrics", "uri":"rds_06_0003.html", "doc_type":"usermanual", - "p_code":"128", - "code":"131" + "p_code":"146", + "code":"149" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1185,7 +1347,7 @@ "uri":"rds_08_0020.html", "doc_type":"usermanual", "p_code":"70", - "code":"132" + "code":"150" }, { "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", @@ -1193,8 +1355,8 @@ "title":"Key Operations Supported by CTS", "uri":"rds_06_0004.html", "doc_type":"usermanual", - "p_code":"132", - "code":"133" + "p_code":"150", + "code":"151" }, { "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", @@ -1202,8 +1364,8 @@ "title":"Viewing Tracing Events", "uri":"rds_06_0005.html", "doc_type":"usermanual", - "p_code":"132", - "code":"134" + "p_code":"150", + "code":"152" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1212,7 +1374,7 @@ "uri":"rds_08_0021.html", "doc_type":"usermanual", "p_code":"70", - "code":"135" + "code":"153" }, { "desc":"RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.Error logs contain warning- and error-level logs generated during ", @@ -1220,8 +1382,8 @@ "title":"Viewing Error Logs", "uri":"rds_mysql_error_log.html", "doc_type":"usermanual", - "p_code":"135", - "code":"136" + "p_code":"153", + "code":"154" }, { "desc":"Slow query logs record statements that exceed long_query_time. You can use these logs to identify and optimize the statements that are executing slowly.RDS supports the f", @@ -1229,8 +1391,8 @@ "title":"Viewing Slow Query Logs", "uri":"rds_mysql_slow_query_log.html", "doc_type":"usermanual", - "p_code":"135", - "code":"137" + "p_code":"153", + "code":"155" }, { "desc":"You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.Only failover and switchover logs within 30 days are displayed.", @@ -1238,8 +1400,8 @@ "title":"Viewing Failover/Switchover Logs", "uri":"rds_switch_log.html", "doc_type":"usermanual", - "p_code":"135", - "code":"138" + "p_code":"153", + "code":"156" }, { "desc":"After you enable the SQL audit function, all SQL operations will be recorded in log files. You can download audit logs to view log details.By default, SQL audit is disabl", @@ -1247,8 +1409,8 @@ "title":"Enabling the SQL Audit Function", "uri":"rds_sql_auditing_log.html", "doc_type":"usermanual", - "p_code":"135", - "code":"139" + "p_code":"153", + "code":"157" }, { "desc":"If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. ", @@ -1256,8 +1418,8 @@ "title":"Downloading SQL Audit Logs", "uri":"rds_download_sql_auditing_log.html", "doc_type":"usermanual", - "p_code":"135", - "code":"140" + "p_code":"153", + "code":"158" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1266,7 +1428,7 @@ "uri":"rds_05_0007.html", "doc_type":"usermanual", "p_code":"70", - "code":"141" + "code":"159" }, { "desc":"You can view the progress and results of scheduled and instant tasks on the Task Center page.RDS allows you to view and manage the following instant tasks:Creating DB ins", @@ -1274,8 +1436,8 @@ "title":"Viewing a Task", "uri":"rds_task_0001.html", "doc_type":"usermanual", - "p_code":"141", - "code":"142" + "p_code":"159", + "code":"160" }, { "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", @@ -1283,8 +1445,8 @@ "title":"Deleting a Task Record", "uri":"rds_task_0002.html", "doc_type":"usermanual", - "p_code":"141", - "code":"143" + "p_code":"159", + "code":"161" }, { "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", @@ -1293,7 +1455,7 @@ "uri":"rds_tag.html", "doc_type":"usermanual", "p_code":"70", - "code":"144" + "code":"162" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1302,7 +1464,7 @@ "uri":"rds_09_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"145" + "code":"163" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1310,8 +1472,8 @@ "title":"Data Migration", "uri":"rds_pg_05_0001_02.html", "doc_type":"usermanual", - "p_code":"145", - "code":"146" + "p_code":"163", + "code":"164" }, { "desc":"PostgreSQL supports logical backups. You can use the pg_dump logical backup function to export backup files and then import them to RDS using psql.You can access RDS DB i", @@ -1319,8 +1481,8 @@ "title":"Migrating Data to RDS for PostgreSQL Using psql", "uri":"rds_09_0023.html", "doc_type":"usermanual", - "p_code":"146", - "code":"147" + "p_code":"164", + "code":"165" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1328,8 +1490,8 @@ "title":"Parameter Tuning", "uri":"rds_pg_10_0000.html", "doc_type":"usermanual", - "p_code":"145", - "code":"148" + "p_code":"163", + "code":"166" }, { "desc":"Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some", @@ -1337,35 +1499,35 @@ "title":"Suggestions on PostgreSQL Parameter Tuning", "uri":"rds_pg_10_0001.html", "doc_type":"usermanual", - "p_code":"148", - "code":"149" + "p_code":"166", + "code":"167" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"rds", - "title":"PostgreSQL Enhanced Edition", - "uri":"rds_04_0001.html", + "title":"Permissions Management", + "uri":"rds_pg_07_0000.html", "doc_type":"usermanual", - "p_code":"145", - "code":"150" + "p_code":"163", + "code":"168" }, { - "desc":"PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/S", + "desc":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", "product_code":"rds", - "title":"Introduction to PostgreSQL Enhanced Edition", - "uri":"rds_03_0018.html", + "title":"Creating a User and Granting Permissions", + "uri":"rds_pg_07_0002.html", "doc_type":"usermanual", - "p_code":"150", - "code":"151" + "p_code":"168", + "code":"169" }, { - "desc":"This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.", + "desc":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", "product_code":"rds", - "title":"Functions", - "uri":"rds_04_0002.html", + "title":"RDS Custom Policies", + "uri":"rds_pg_07_0003.html", "doc_type":"usermanual", - "p_code":"150", - "code":"152" + "p_code":"168", + "code":"170" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1373,8 +1535,8 @@ "title":"Instance Lifecycle", "uri":"rds_pg_05_0000.html", "doc_type":"usermanual", - "p_code":"145", - "code":"153" + "p_code":"163", + "code":"171" }, { "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", @@ -1382,8 +1544,8 @@ "title":"Creating a Same DB Instance as an Existing DB Instance", "uri":"rds_pg_05_0055.html", "doc_type":"usermanual", - "p_code":"153", - "code":"154" + "p_code":"171", + "code":"172" }, { "desc":"If you use DB instances only for routine development, you can temporarily stop pay-per-use instances to save money. You can stop an instance for up to seven days.If you s", @@ -1391,8 +1553,8 @@ "title":"Stopping an Instance", "uri":"rds_pg_stop.html", "doc_type":"usermanual", - "p_code":"153", - "code":"155" + "p_code":"171", + "code":"173" }, { "desc":"You can stop your instance temporarily to save money. After stopping your instance, you can restart it to begin using it again.If you start a primary instance, read repli", @@ -1400,8 +1562,8 @@ "title":"Starting an Instance", "uri":"rds_pg_start.html", "doc_type":"usermanual", - "p_code":"153", - "code":"156" + "p_code":"171", + "code":"174" }, { "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", @@ -1409,8 +1571,8 @@ "title":"Rebooting DB Instances or Read Replicas", "uri":"rds_09_0024.html", "doc_type":"usermanual", - "p_code":"153", - "code":"157" + "p_code":"171", + "code":"175" }, { "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", @@ -1418,8 +1580,8 @@ "title":"Selecting Displayed Items", "uri":"rds_pg_06_0022.html", "doc_type":"usermanual", - "p_code":"153", - "code":"158" + "p_code":"171", + "code":"176" }, { "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", @@ -1427,8 +1589,8 @@ "title":"Exporting DB Instance Information", "uri":"rds_pg_05_0017.html", "doc_type":"usermanual", - "p_code":"153", - "code":"159" + "p_code":"171", + "code":"177" }, { "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", @@ -1436,8 +1598,8 @@ "title":"Deleting a DB Instance or Read Replica", "uri":"rds_09_0025.html", "doc_type":"usermanual", - "p_code":"153", - "code":"160" + "p_code":"171", + "code":"178" }, { "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", @@ -1445,8 +1607,8 @@ "title":"Recycling a DB Instance", "uri":"rds_pg_recycle.html", "doc_type":"usermanual", - "p_code":"153", - "code":"161" + "p_code":"171", + "code":"179" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1454,8 +1616,17 @@ "title":"Instance Modifications", "uri":"rds_pg_05_0001.html", "doc_type":"usermanual", - "p_code":"145", - "code":"162" + "p_code":"163", + "code":"180" + }, + { + "desc":"RDS for PostgreSQL supports minor version upgrades to improve performance, add new functions, and fix bugs.When any new minor version is released to address vulnerabiliti", + "product_code":"rds", + "title":"Upgrading a Minor Version", + "uri":"rds_pg_05_0003.html", + "doc_type":"usermanual", + "p_code":"180", + "code":"181" }, { "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", @@ -1463,8 +1634,8 @@ "title":"Changing a DB Instance Name", "uri":"rds_pg_modify_instance_name.html", "doc_type":"usermanual", - "p_code":"162", - "code":"163" + "p_code":"180", + "code":"182" }, { "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", @@ -1472,8 +1643,8 @@ "title":"Changing the Failover Priority", "uri":"rds_pg_modify_availability.html", "doc_type":"usermanual", - "p_code":"162", - "code":"164" + "p_code":"180", + "code":"183" }, { "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", @@ -1481,8 +1652,8 @@ "title":"Changing a DB Instance Class", "uri":"rds_pg_scale_rds.html", "doc_type":"usermanual", - "p_code":"162", - "code":"165" + "p_code":"180", + "code":"184" }, { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", @@ -1490,8 +1661,8 @@ "title":"Scaling up Storage Space", "uri":"rds_pg_scale_cluster.html", "doc_type":"usermanual", - "p_code":"162", - "code":"166" + "p_code":"180", + "code":"185" }, { "desc":"The maintenance window is 02:00–06:00 by default and you can change it as required. To prevent service interruptions, you are advised to set the maintenance window to off", @@ -1499,8 +1670,8 @@ "title":"Changing the Maintenance Window", "uri":"rds_pg_05_0038.html", "doc_type":"usermanual", - "p_code":"162", - "code":"167" + "p_code":"180", + "code":"186" }, { "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", @@ -1508,8 +1679,8 @@ "title":"Changing a DB Instance Type from Single to Primary/Standby", "uri":"rds_pg_05_0023.html", "doc_type":"usermanual", - "p_code":"162", - "code":"168" + "p_code":"180", + "code":"187" }, { "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", @@ -1517,8 +1688,17 @@ "title":"Manually Switching Between Primary and Standby DB Instances", "uri":"rds_pg_switch_ha.html", "doc_type":"usermanual", - "p_code":"162", - "code":"169" + "p_code":"180", + "code":"188" + }, + { + "desc":"You can migrate a standby DB instance to another AZ in the same region as the original AZ.DDL operations and scheduled events will be suspended during migration. To preve", + "product_code":"rds", + "title":"Migrating a Standby DB Instance", + "uri":"rds_pg_05_0060.html", + "doc_type":"usermanual", + "p_code":"180", + "code":"189" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1526,8 +1706,8 @@ "title":"Read Replicas", "uri":"rds_pg_11_0001.html", "doc_type":"usermanual", - "p_code":"145", - "code":"170" + "p_code":"163", + "code":"190" }, { "desc":"RDS for PostgreSQL supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affec", @@ -1535,8 +1715,8 @@ "title":"Introducing Read Replicas", "uri":"rds_pg_11_0002.html", "doc_type":"usermanual", - "p_code":"170", - "code":"171" + "p_code":"190", + "code":"191" }, { "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.You can create read replicas as needed.A maximum of five read replicas", @@ -1544,8 +1724,8 @@ "title":"Creating a Read Replica", "uri":"rds_add_read_replica_pg.html", "doc_type":"usermanual", - "p_code":"170", - "code":"172" + "p_code":"190", + "code":"192" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1553,8 +1733,8 @@ "title":"Managing a Read Replica", "uri":"rds_pg_11_0004.html", "doc_type":"usermanual", - "p_code":"170", - "code":"173" + "p_code":"190", + "code":"193" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1562,8 +1742,8 @@ "title":"Backups and Restorations", "uri":"rds_pg_05_0034.html", "doc_type":"usermanual", - "p_code":"145", - "code":"174" + "p_code":"163", + "code":"194" }, { "desc":"RDS supports backups and restorations to ensure data reliability.Automated backups are created during the backup time window for your DB instances. RDS saves automated ba", @@ -1571,8 +1751,8 @@ "title":"Working with Backups", "uri":"rds_pg_backup_restore.html", "doc_type":"usermanual", - "p_code":"174", - "code":"175" + "p_code":"194", + "code":"195" }, { "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", @@ -1580,8 +1760,8 @@ "title":"Configuring an Automated Backup Policy", "uri":"rds_09_0027.html", "doc_type":"usermanual", - "p_code":"174", - "code":"176" + "p_code":"194", + "code":"196" }, { "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", @@ -1589,8 +1769,8 @@ "title":"Creating a Manual Backup", "uri":"rds_09_0028.html", "doc_type":"usermanual", - "p_code":"174", - "code":"177" + "p_code":"194", + "code":"197" }, { "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", @@ -1598,8 +1778,8 @@ "title":"Downloading a Full Backup File", "uri":"rds_09_0031.html", "doc_type":"usermanual", - "p_code":"174", - "code":"178" + "p_code":"194", + "code":"198" }, { "desc":"This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.RDS for PostgreSQL enables you to down", @@ -1607,8 +1787,8 @@ "title":"Downloading an Incremental Backup File", "uri":"rds_pg_05_0138.html", "doc_type":"usermanual", - "p_code":"174", - "code":"179" + "p_code":"194", + "code":"199" }, { "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance ", @@ -1616,17 +1796,8 @@ "title":"Restoring from Backup Files to RDS for PostgreSQL", "uri":"rds_09_0030.html", "doc_type":"usermanual", - "p_code":"174", - "code":"180" - }, - { - "desc":"You can download backup files by referring to Downloading a Full Backup File and restore data from them.A tool for decompressing TAR files must be installed in a Unix-lik", - "product_code":"rds", - "title":"Restoring from Full Backup Files to a Self-Built PostgreSQL Database", - "uri":"rds_pg_08_0044.html", - "doc_type":"usermanual", - "p_code":"174", - "code":"181" + "p_code":"194", + "code":"200" }, { "desc":"You can restore from automated backups to a specified point in time.RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.When you en", @@ -1634,8 +1805,8 @@ "title":"Restoring a DB Instance to a Point in Time", "uri":"rds_09_0029.html", "doc_type":"usermanual", - "p_code":"174", - "code":"182" + "p_code":"194", + "code":"201" }, { "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", @@ -1643,8 +1814,8 @@ "title":"Replicating a Backup", "uri":"rds_09_0032.html", "doc_type":"usermanual", - "p_code":"174", - "code":"183" + "p_code":"194", + "code":"202" }, { "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", @@ -1652,8 +1823,8 @@ "title":"Deleting a Manual Backup", "uri":"rds_09_0033.html", "doc_type":"usermanual", - "p_code":"174", - "code":"184" + "p_code":"194", + "code":"203" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1661,8 +1832,8 @@ "title":"Parameter Template Management", "uri":"rds_09_0034.html", "doc_type":"usermanual", - "p_code":"145", - "code":"185" + "p_code":"163", + "code":"204" }, { "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", @@ -1670,8 +1841,8 @@ "title":"Creating a Parameter Template", "uri":"rds_pg_parameter_group.html", "doc_type":"usermanual", - "p_code":"185", - "code":"186" + "p_code":"204", + "code":"205" }, { "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can change parameter values in custom parameter templates only and canno", @@ -1679,8 +1850,8 @@ "title":"Modifying Instance Parameters", "uri":"rds_pg_configuration.html", "doc_type":"usermanual", - "p_code":"185", - "code":"187" + "p_code":"204", + "code":"206" }, { "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", @@ -1688,8 +1859,8 @@ "title":"Exporting a Parameter Template", "uri":"rds_pg_08_0042.html", "doc_type":"usermanual", - "p_code":"185", - "code":"188" + "p_code":"204", + "code":"207" }, { "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", @@ -1697,8 +1868,8 @@ "title":"Comparing Parameter Templates", "uri":"rds_09_0035.html", "doc_type":"usermanual", - "p_code":"185", - "code":"189" + "p_code":"204", + "code":"208" }, { "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", @@ -1706,8 +1877,8 @@ "title":"Viewing Parameter Change History", "uri":"rds_pg_05_0099.html", "doc_type":"usermanual", - "p_code":"185", - "code":"190" + "p_code":"204", + "code":"209" }, { "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", @@ -1715,8 +1886,8 @@ "title":"Replicating a Parameter Template", "uri":"rds_09_0036.html", "doc_type":"usermanual", - "p_code":"185", - "code":"191" + "p_code":"204", + "code":"210" }, { "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", @@ -1724,8 +1895,8 @@ "title":"Resetting a Parameter Template", "uri":"rds_09_0037.html", "doc_type":"usermanual", - "p_code":"185", - "code":"192" + "p_code":"204", + "code":"211" }, { "desc":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", @@ -1733,8 +1904,8 @@ "title":"Applying a Parameter Template", "uri":"rds_pg_05_0018.html", "doc_type":"usermanual", - "p_code":"185", - "code":"193" + "p_code":"204", + "code":"212" }, { "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", @@ -1742,8 +1913,8 @@ "title":"Viewing Application Records of a Parameter Template", "uri":"rds_pg_05_0098.html", "doc_type":"usermanual", - "p_code":"185", - "code":"194" + "p_code":"204", + "code":"213" }, { "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", @@ -1751,8 +1922,8 @@ "title":"Modifying a Parameter Template Description", "uri":"rds_09_0038.html", "doc_type":"usermanual", - "p_code":"185", - "code":"195" + "p_code":"204", + "code":"214" }, { "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", @@ -1760,8 +1931,8 @@ "title":"Deleting a Parameter Template", "uri":"rds_09_0039.html", "doc_type":"usermanual", - "p_code":"185", - "code":"196" + "p_code":"204", + "code":"215" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1769,8 +1940,8 @@ "title":"Connection Management", "uri":"rds_pg_05_0005.html", "doc_type":"usermanual", - "p_code":"145", - "code":"197" + "p_code":"163", + "code":"216" }, { "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", @@ -1778,8 +1949,8 @@ "title":"Configuring and Changing a Floating IP Address", "uri":"rds_pg_05_0024.html", "doc_type":"usermanual", - "p_code":"197", - "code":"198" + "p_code":"216", + "code":"217" }, { "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", @@ -1787,8 +1958,8 @@ "title":"Binding and Unbinding an EIP", "uri":"rds_pg_public_accessibility.html", "doc_type":"usermanual", - "p_code":"197", - "code":"199" + "p_code":"216", + "code":"218" }, { "desc":"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 pri", @@ -1796,8 +1967,8 @@ "title":"Changing a Database Port", "uri":"rds_pg_change_database_port.html", "doc_type":"usermanual", - "p_code":"197", - "code":"200" + "p_code":"216", + "code":"219" }, { "desc":"You can use the pgAdmin client to connect to an RDS DB instance.The pgAdmin version must be 4 or later.Prepare an ECS or a device that can access RDS DB instances.To conn", @@ -1805,8 +1976,8 @@ "title":"Connecting to a DB Instance Through pgAdmin", "uri":"rds_pg_11_0005.html", "doc_type":"usermanual", - "p_code":"197", - "code":"201" + "p_code":"216", + "code":"220" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1814,8 +1985,8 @@ "title":"Plugin Management", "uri":"rds_09_0046.html", "doc_type":"usermanual", - "p_code":"145", - "code":"202" + "p_code":"163", + "code":"221" }, { "desc":"RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section", @@ -1823,8 +1994,8 @@ "title":"Creating or Deleting a Plugin", "uri":"rds_09_0043.html", "doc_type":"usermanual", - "p_code":"202", - "code":"203" + "p_code":"221", + "code":"222" }, { "desc":"The following table lists the plugins supported by the latest minor versions of RDS for PostgreSQL. You can use SELECT name FROM pg_available_extensions; to view the plug", @@ -1832,8 +2003,8 @@ "title":"Supported Plugins", "uri":"rds_09_0045.html", "doc_type":"usermanual", - "p_code":"202", - "code":"204" + "p_code":"221", + "code":"223" }, { "desc":"RDS provides the PostgreSQL tablespace management solution based on user root.# psql --host=--port= --dbname=--username=root -c\"select cont", @@ -1841,8 +2012,8 @@ "title":"Tablespace Management", "uri":"rds_09_0044.html", "doc_type":"usermanual", - "p_code":"145", - "code":"205" + "p_code":"163", + "code":"224" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1850,8 +2021,8 @@ "title":"Data Security", "uri":"rds_pg_05_0006.html", "doc_type":"usermanual", - "p_code":"145", - "code":"206" + "p_code":"163", + "code":"225" }, { "desc":"You can reset the administrator password of a primary instance.You can also reset the password of your database account when using RDS.If you have changed the administrat", @@ -1859,8 +2030,8 @@ "title":"Resetting the Administrator Password", "uri":"rds_pg_reset_password.html", "doc_type":"usermanual", - "p_code":"206", - "code":"207" + "p_code":"225", + "code":"226" }, { "desc":"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 pri", @@ -1868,8 +2039,8 @@ "title":"Changing a Security Group", "uri":"rds_09_0026.html", "doc_type":"usermanual", - "p_code":"206", - "code":"208" + "p_code":"225", + "code":"227" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1877,8 +2048,8 @@ "title":"Metrics and Alarms", "uri":"rds_09_0041.html", "doc_type":"usermanual", - "p_code":"145", - "code":"209" + "p_code":"163", + "code":"228" }, { "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", @@ -1886,8 +2057,8 @@ "title":"Configuring Displayed Metrics", "uri":"rds_pg_06_0001.html", "doc_type":"usermanual", - "p_code":"209", - "code":"210" + "p_code":"228", + "code":"229" }, { "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", @@ -1895,8 +2066,8 @@ "title":"Setting Alarm Rules", "uri":"rds_pg_06_0002.html", "doc_type":"usermanual", - "p_code":"209", - "code":"211" + "p_code":"228", + "code":"230" }, { "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", @@ -1904,8 +2075,8 @@ "title":"Viewing Monitoring Metrics", "uri":"rds_pg_06_0003.html", "doc_type":"usermanual", - "p_code":"209", - "code":"212" + "p_code":"228", + "code":"231" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1913,8 +2084,8 @@ "title":"Interconnection with CTS", "uri":"rds_09_0042.html", "doc_type":"usermanual", - "p_code":"145", - "code":"213" + "p_code":"163", + "code":"232" }, { "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", @@ -1922,8 +2093,8 @@ "title":"Key Operations Supported by CTS", "uri":"rds_pg_06_0004.html", "doc_type":"usermanual", - "p_code":"213", - "code":"214" + "p_code":"232", + "code":"233" }, { "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", @@ -1931,8 +2102,8 @@ "title":"Viewing Tracing Events", "uri":"rds_pg_06_0005.html", "doc_type":"usermanual", - "p_code":"213", - "code":"215" + "p_code":"232", + "code":"234" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1940,8 +2111,8 @@ "title":"Log Management", "uri":"rds_08_001.html", "doc_type":"usermanual", - "p_code":"145", - "code":"216" + "p_code":"163", + "code":"235" }, { "desc":"Error logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner ", @@ -1949,8 +2120,8 @@ "title":"Viewing Error Logs", "uri":"rds_recent_log.html", "doc_type":"usermanual", - "p_code":"216", - "code":"217" + "p_code":"235", + "code":"236" }, { "desc":"Slow query logs record statements that exceed the log_min_duration_statement value. You can view log details to identify statements that are slowly executed and optimize ", @@ -1958,8 +2129,8 @@ "title":"Viewing Slow Query Logs", "uri":"slow_query_log-pg.html", "doc_type":"usermanual", - "p_code":"216", - "code":"218" + "p_code":"235", + "code":"237" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1967,8 +2138,8 @@ "title":"Task Center", "uri":"rds_pg_05_0007.html", "doc_type":"usermanual", - "p_code":"145", - "code":"219" + "p_code":"163", + "code":"238" }, { "desc":"You can view the detailed progress and result of the task on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasC", @@ -1976,8 +2147,8 @@ "title":"Viewing a Task", "uri":"rds_task_pg_0001.html", "doc_type":"usermanual", - "p_code":"219", - "code":"220" + "p_code":"238", + "code":"239" }, { "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", @@ -1985,8 +2156,8 @@ "title":"Deleting a Task Record", "uri":"rds_task_pg_0002.html", "doc_type":"usermanual", - "p_code":"219", - "code":"221" + "p_code":"238", + "code":"240" }, { "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", @@ -1994,8 +2165,8 @@ "title":"Managing Tags", "uri":"rds_pg_tag.html", "doc_type":"usermanual", - "p_code":"145", - "code":"222" + "p_code":"163", + "code":"241" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2004,7 +2175,7 @@ "uri":"rds_10_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"223" + "code":"242" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2012,8 +2183,8 @@ "title":"Data Migration", "uri":"rds_sqlserver_05_0001_02.html", "doc_type":"usermanual", - "p_code":"223", - "code":"224" + "p_code":"242", + "code":"243" }, { "desc":"You can access RDS DB instances through an EIP or ECS.Prepare an ECS for accessing DB instances in the same VPC or prepare a device for accessing RDS through an EIP. To c", @@ -2021,8 +2192,35 @@ "title":"Migrating Data to RDS for SQL Server Using SQL Server Management Studio", "uri":"rds_10_0035.html", "doc_type":"usermanual", - "p_code":"224", - "code":"225" + "p_code":"243", + "code":"244" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "product_code":"rds", + "title":"Permissions Management", + "uri":"rds_sqlserver_07_0000.html", + "doc_type":"usermanual", + "p_code":"242", + "code":"245" + }, + { + "desc":"This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:Create IAM users ", + "product_code":"rds", + "title":"Creating a User and Granting Permissions", + "uri":"rds_sqlserver_07_0002.html", + "doc_type":"usermanual", + "p_code":"245", + "code":"246" + }, + { + "desc":"Custom policies can be created to supplement the system policies of RDS.You can create custom policies in either of the following two ways:Visual editor: Select cloud ser", + "product_code":"rds", + "title":"RDS Custom Policies", + "uri":"rds_sqlserver_07_0003.html", + "doc_type":"usermanual", + "p_code":"245", + "code":"247" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2030,8 +2228,8 @@ "title":"Instance Lifecycle", "uri":"rds_sqlserver_05_0000.html", "doc_type":"usermanual", - "p_code":"223", - "code":"226" + "p_code":"242", + "code":"248" }, { "desc":"This section describes how to quickly create a DB instance with the same configurations as the selected one.You can create DB instances with the same configurations numer", @@ -2039,8 +2237,8 @@ "title":"Creating a Same DB Instance as an Existing DB Instance", "uri":"rds_sqlserver_05_0055.html", "doc_type":"usermanual", - "p_code":"226", - "code":"227" + "p_code":"248", + "code":"249" }, { "desc":"You may need to reboot a DB instance during maintenance. For example, after modifying some parameters, a reboot is required for the modifications to take effect. You can ", @@ -2048,8 +2246,8 @@ "title":"Rebooting DB Instances or Read Replicas", "uri":"rds_11_0006.html", "doc_type":"usermanual", - "p_code":"226", - "code":"228" + "p_code":"248", + "code":"250" }, { "desc":"You can customize which instance items are displayed on the Instances page.The following items are displayed by default: DB instance name/ID, DB instance type, DB engine ", @@ -2057,8 +2255,8 @@ "title":"Selecting Displayed Items", "uri":"rds_sqlserver_06_0022.html", "doc_type":"usermanual", - "p_code":"226", - "code":"229" + "p_code":"248", + "code":"251" }, { "desc":"You can export information about all or selected DB instances to view and analyze DB instance information.", @@ -2066,8 +2264,8 @@ "title":"Exporting DB Instance Information", "uri":"rds_sqlserver_05_0017.html", "doc_type":"usermanual", - "p_code":"226", - "code":"230" + "p_code":"248", + "code":"252" }, { "desc":"To release resources, you can delete DB instances or read replicas as required on the Instances page.DB instances cannot be deleted when operations are being performed on", @@ -2075,8 +2273,8 @@ "title":"Deleting a DB Instance or Read Replica", "uri":"rds_11_0030.html", "doc_type":"usermanual", - "p_code":"226", - "code":"231" + "p_code":"248", + "code":"253" }, { "desc":"Deleted DB instances can be moved to the recycle bin. You can rebuild DB instances from the recycle bin. The DB engine, DB engine version, and storage type of the new DB ", @@ -2084,8 +2282,8 @@ "title":"Recycling a DB Instance", "uri":"rds_sqlserver_recycle.html", "doc_type":"usermanual", - "p_code":"226", - "code":"232" + "p_code":"248", + "code":"254" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2093,8 +2291,8 @@ "title":"Instance Modifications", "uri":"rds_sqlserver_05_0008.html", "doc_type":"usermanual", - "p_code":"223", - "code":"233" + "p_code":"242", + "code":"255" }, { "desc":"You can change the name of a primary DB instance or read replica.Alternatively, click the target DB instance to go to the Basic Information page. In the DB Instance Name ", @@ -2102,8 +2300,8 @@ "title":"Changing a DB Instance Name", "uri":"rds_sqlserver_modify_instance_name.html", "doc_type":"usermanual", - "p_code":"233", - "code":"234" + "p_code":"255", + "code":"256" }, { "desc":"You can configure the failover priority for reliability or for availability, depending on your service requirements.Reliability: This option is selected by default. Data ", @@ -2111,8 +2309,8 @@ "title":"Changing the Failover Priority", "uri":"rds_sqlserver_modify_availability.html", "doc_type":"usermanual", - "p_code":"233", - "code":"235" + "p_code":"255", + "code":"257" }, { "desc":"You can change the instance class (CPU or memory) of a DB instance as required. If the status of a DB instance changes from Changing instance class to Available, the chan", @@ -2120,8 +2318,8 @@ "title":"Changing a DB Instance Class", "uri":"rds_sqlserver_scale_rds.html", "doc_type":"usermanual", - "p_code":"233", - "code":"236" + "p_code":"255", + "code":"258" }, { "desc":"If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.The DB instance needs to preserve at least 15% of its capa", @@ -2129,8 +2327,8 @@ "title":"Scaling up Storage Space", "uri":"rds_sqlserver_scale_cluster.html", "doc_type":"usermanual", - "p_code":"233", - "code":"237" + "p_code":"255", + "code":"259" }, { "desc":"RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.Primary/standby DB instances support automatic failover. If ", @@ -2138,8 +2336,8 @@ "title":"Changing a DB Instance Type from Single to Primary/Standby", "uri":"rds_sqlserver_05_0023.html", "doc_type":"usermanual", - "p_code":"233", - "code":"238" + "p_code":"255", + "code":"260" }, { "desc":"If you choose to create primary/standby DB instances, RDS will create a primary DB instance and a synchronous standby DB instance in the same region. You can access the p", @@ -2147,8 +2345,8 @@ "title":"Manually Switching Between Primary and Standby DB Instances", "uri":"rds_sqlserver_switch_ha.html", "doc_type":"usermanual", - "p_code":"233", - "code":"239" + "p_code":"255", + "code":"261" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2156,17 +2354,17 @@ "title":"Read Replicas", "uri":"rds_sqlserver_11_0001.html", "doc_type":"usermanual", - "p_code":"223", - "code":"240" + "p_code":"242", + "code":"262" }, { - "desc":"Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and ser", + "desc":"Only RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.In read-intensive scenarios, a single DB instance may be unable to handl", "product_code":"rds", "title":"Introducing Read Replicas", "uri":"rds_sqlserver_11_0002.html", "doc_type":"usermanual", - "p_code":"240", - "code":"241" + "p_code":"262", + "code":"263" }, { "desc":"Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.After a DB instance has been created, you can create read replicas for", @@ -2174,8 +2372,8 @@ "title":"Creating a Read Replica", "uri":"rds_03_0011.html", "doc_type":"usermanual", - "p_code":"240", - "code":"242" + "p_code":"262", + "code":"264" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2183,8 +2381,8 @@ "title":"Managing a Read Replica", "uri":"rds_sqlserver_11_0004.html", "doc_type":"usermanual", - "p_code":"240", - "code":"243" + "p_code":"262", + "code":"265" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2192,8 +2390,8 @@ "title":"Backups and Restorations", "uri":"rds_sqlserver_05_0034.html", "doc_type":"usermanual", - "p_code":"223", - "code":"244" + "p_code":"242", + "code":"266" }, { "desc":"RDS supports DB instance backups and restorations to ensure data reliability.Automated backups are created during the backup period of your DB instances. RDS saves automa", @@ -2201,8 +2399,8 @@ "title":"Working with Backups", "uri":"rds_sqlserver_backup_restore.html", "doc_type":"usermanual", - "p_code":"244", - "code":"245" + "p_code":"266", + "code":"267" }, { "desc":"When you create a DB instance, an automated backup policy is enabled by default. For security purposes, the automated backup policy cannot be disabled. After the DB insta", @@ -2210,8 +2408,8 @@ "title":"Configuring an Automated Backup Policy", "uri":"rds_11_0031.html", "doc_type":"usermanual", - "p_code":"244", - "code":"246" + "p_code":"266", + "code":"268" }, { "desc":"RDS allows you to create manual backups of a running primary DB instance. You can use these backups to restore data.When you delete a DB instance, its automated backups a", @@ -2219,8 +2417,8 @@ "title":"Creating a Manual Backup", "uri":"rds_11_0010.html", "doc_type":"usermanual", - "p_code":"244", - "code":"247" + "p_code":"266", + "code":"269" }, { "desc":"This section describes how to download a manual backup or an automated backup to a local device and restore data from the backup file.If the size of the backup data is gr", @@ -2228,8 +2426,8 @@ "title":"Downloading a Backup File", "uri":"rds_11_0013.html", "doc_type":"usermanual", - "p_code":"244", - "code":"248" + "p_code":"266", + "code":"270" }, { "desc":"This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.Alternatively, click the target DB inst", @@ -2237,8 +2435,8 @@ "title":"Restoring from Backup Files to RDS for SQL Server", "uri":"rds_11_0023.html", "doc_type":"usermanual", - "p_code":"244", - "code":"249" + "p_code":"266", + "code":"271" }, { "desc":"You can download backup files by referring to section Downloading a Backup File and restore data from them. You can use SQL Server Management Studio (SSMS) to connect to ", @@ -2246,8 +2444,8 @@ "title":"Restoring from Backup Files to a Self-Built SQL Server Database", "uri":"rds_05_0044.html", "doc_type":"usermanual", - "p_code":"244", - "code":"250" + "p_code":"266", + "code":"272" }, { "desc":"You can restore from automated backups to a specified point in time.RDS for Microsoft SQL Server supports restoration to a new, the original, or an existing DB instance.I", @@ -2255,8 +2453,8 @@ "title":"Restoring a DB Instance to a Point in Time", "uri":"rds_11_0022.html", "doc_type":"usermanual", - "p_code":"244", - "code":"251" + "p_code":"266", + "code":"273" }, { "desc":"This section describes how to replicate a manual or an automated backup. The new backup name must be different from the original backup name.You can replicate backups and", @@ -2264,8 +2462,8 @@ "title":"Replicating a Backup", "uri":"rds_10_0055.html", "doc_type":"usermanual", - "p_code":"244", - "code":"252" + "p_code":"266", + "code":"274" }, { "desc":"You can delete manual backups to free up backup storage.Deleted manual backups cannot be recovered. Exercise caution when performing this operation.The following backups ", @@ -2273,8 +2471,8 @@ "title":"Deleting a Manual Backup", "uri":"rds_10_0101.html", "doc_type":"usermanual", - "p_code":"244", - "code":"253" + "p_code":"266", + "code":"275" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2282,8 +2480,8 @@ "title":"Parameter Template Management", "uri":"rds_10_0102.html", "doc_type":"usermanual", - "p_code":"223", - "code":"254" + "p_code":"242", + "code":"276" }, { "desc":"You can use database parameter templates to manage the DB engine configuration. A database parameter template acts as a container for engine configuration values that can", @@ -2291,8 +2489,8 @@ "title":"Creating a Parameter Template", "uri":"rds_sqlserver_parameter_group.html", "doc_type":"usermanual", - "p_code":"254", - "code":"255" + "p_code":"276", + "code":"277" }, { "desc":"You can modify parameters in a custom parameter template to optimize RDS database performance.You can only change parameter values in custom parameter templates. You cann", @@ -2300,8 +2498,8 @@ "title":"Modifying Parameters", "uri":"rds_sqlserver_configuration.html", "doc_type":"usermanual", - "p_code":"254", - "code":"256" + "p_code":"276", + "code":"278" }, { "desc":"You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Paramet", @@ -2309,8 +2507,8 @@ "title":"Exporting a Parameter Template", "uri":"rds_sqlserver_08_0042.html", "doc_type":"usermanual", - "p_code":"254", - "code":"257" + "p_code":"276", + "code":"279" }, { "desc":"You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.You can also compare def", @@ -2318,8 +2516,8 @@ "title":"Comparing Parameter Templates", "uri":"rds_10_0103.html", "doc_type":"usermanual", - "p_code":"254", - "code":"258" + "p_code":"276", + "code":"280" }, { "desc":"You can view the change history of DB instance parameters or custom parameter templates.An exported or custom parameter template has initially a blank change history.You ", @@ -2327,8 +2525,8 @@ "title":"Viewing Parameter Change History", "uri":"rds_sqlserver_05_0099.html", "doc_type":"usermanual", - "p_code":"254", - "code":"259" + "p_code":"276", + "code":"281" }, { "desc":"You can replicate a parameter template you have created. When you have already created a parameter template and want to include most of the custom parameters and values f", @@ -2336,8 +2534,8 @@ "title":"Replicating a Parameter Template", "uri":"rds_10_0104.html", "doc_type":"usermanual", - "p_code":"254", - "code":"260" + "p_code":"276", + "code":"282" }, { "desc":"You can reset all parameters in a custom parameter template to their default settings.If the DB instance status is Parameter change. Pending reboot, a reboot is required ", @@ -2345,8 +2543,8 @@ "title":"Resetting a Parameter Template", "uri":"rds_10_0105.html", "doc_type":"usermanual", - "p_code":"254", - "code":"261" + "p_code":"276", + "code":"283" }, { "desc":"You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.If you intend to apply a default", @@ -2354,8 +2552,8 @@ "title":"Applying a Parameter Template", "uri":"rds_sqlserver_05_0018.html", "doc_type":"usermanual", - "p_code":"254", - "code":"262" + "p_code":"276", + "code":"284" }, { "desc":"You can view the application records of a parameter template.You can view the name or ID of the DB instance that the parameter template applies to, as well as the applica", @@ -2363,8 +2561,8 @@ "title":"Viewing Application Records of a Parameter Template", "uri":"rds_sqlserver_05_0098.html", "doc_type":"usermanual", - "p_code":"254", - "code":"263" + "p_code":"276", + "code":"285" }, { "desc":"You can modify the description of a parameter template you have created.You cannot modify the description of a default parameter template.The description consists of a ma", @@ -2372,8 +2570,8 @@ "title":"Modifying a Parameter Template Description", "uri":"rds_10_0106.html", "doc_type":"usermanual", - "p_code":"254", - "code":"264" + "p_code":"276", + "code":"286" }, { "desc":"You can delete a custom parameter template that is no longer in use.Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.Defau", @@ -2381,8 +2579,8 @@ "title":"Deleting a Parameter Template", "uri":"rds_10_0107.html", "doc_type":"usermanual", - "p_code":"254", - "code":"265" + "p_code":"276", + "code":"287" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2390,8 +2588,8 @@ "title":"Connection Management", "uri":"rds_sqlserver_05_0005.html", "doc_type":"usermanual", - "p_code":"223", - "code":"266" + "p_code":"242", + "code":"288" }, { "desc":"You can change floating IP addresses after migrating on-premises databases or other cloud databases to RDS.After a floating IP address is changed, the domain name needs t", @@ -2399,8 +2597,8 @@ "title":"Configuring and Changing a Floating IP Address", "uri":"rds_sqlserver_05_0024.html", "doc_type":"usermanual", - "p_code":"266", - "code":"267" + "p_code":"288", + "code":"289" }, { "desc":"By default, a DB instance is not publicly accessible (not bound with an EIP) after being created. You can bind an EIP to a DB instance for public accessibility, and you c", @@ -2408,8 +2606,8 @@ "title":"Binding and Unbinding an EIP", "uri":"rds_sqlserver_0025.html", "doc_type":"usermanual", - "p_code":"266", - "code":"268" + "p_code":"288", + "code":"290" }, { "desc":"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 pri", @@ -2417,8 +2615,8 @@ "title":"Changing a Database Port", "uri":"rds_sqlserver_change_database_port.html", "doc_type":"usermanual", - "p_code":"266", - "code":"269" + "p_code":"288", + "code":"291" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2426,8 +2624,8 @@ "title":"Data Security", "uri":"rds_sqlserver_05_0006.html", "doc_type":"usermanual", - "p_code":"223", - "code":"270" + "p_code":"242", + "code":"292" }, { "desc":"You can reset the administrator password only through the primary DB instance.You can also reset the password of your database account when using RDS.If you have changed ", @@ -2435,8 +2633,8 @@ "title":"Resetting the Administrator Password", "uri":"en-us_topic_sqlserver_reset_password.html", "doc_type":"usermanual", - "p_code":"270", - "code":"271" + "p_code":"292", + "code":"293" }, { "desc":"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 pri", @@ -2444,8 +2642,8 @@ "title":"Changing a Security Group", "uri":"rds_11_0032.html", "doc_type":"usermanual", - "p_code":"270", - "code":"272" + "p_code":"292", + "code":"294" }, { "desc":"Transparent Data Encryption (TDE) encrypts data files and backup files using certificates to implement real-time I/O encryption and decryption. This function effectively ", @@ -2453,8 +2651,8 @@ "title":"Configuring the TDE Function", "uri":"rds_11_0004.html", "doc_type":"usermanual", - "p_code":"270", - "code":"273" + "p_code":"292", + "code":"295" }, { "desc":"The participator, transaction-supported server, resource server, and transaction manager of a distributed transaction are deployed on different nodes in a distributed sys", @@ -2462,8 +2660,8 @@ "title":"Distributed Transactions", "uri":"rds_sqlserver_01_0001.html", "doc_type":"usermanual", - "p_code":"223", - "code":"274" + "p_code":"242", + "code":"296" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2471,8 +2669,8 @@ "title":"Metrics and Alarms", "uri":"rds_sqlserver_06_0000.html", "doc_type":"usermanual", - "p_code":"223", - "code":"275" + "p_code":"242", + "code":"297" }, { "desc":"The RDS Agent monitors RDS DB instances and collects monitoring metrics only.This section describes the metrics that can be monitored by Cloud Eye as well as their namesp", @@ -2480,8 +2678,8 @@ "title":"Configuring Displayed Metrics", "uri":"rds_sqlserver_06_0001.html", "doc_type":"usermanual", - "p_code":"275", - "code":"276" + "p_code":"297", + "code":"298" }, { "desc":"You can set alarm rules by referring to Setting Alarm Rules to customize the monitored objects and notification policies and keep track of the RDS running status.The RDS ", @@ -2489,8 +2687,8 @@ "title":"Setting Alarm Rules", "uri":"rds_sqlserver_06_0002.html", "doc_type":"usermanual", - "p_code":"275", - "code":"277" + "p_code":"297", + "code":"299" }, { "desc":"Cloud Eye monitors the statuses of RDS DB instances. You can view RDS monitoring metrics on the management console.Monitored data takes some time before it can be display", @@ -2498,8 +2696,8 @@ "title":"Viewing Monitoring Metrics", "uri":"rds_sqlserver_06_0003.html", "doc_type":"usermanual", - "p_code":"275", - "code":"278" + "p_code":"297", + "code":"300" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2507,8 +2705,8 @@ "title":"Interconnection with CTS", "uri":"rds_sqlserver_01_0000.html", "doc_type":"usermanual", - "p_code":"223", - "code":"279" + "p_code":"242", + "code":"301" }, { "desc":"Cloud Trace Service (CTS) records operations related to RDS for further query, audit, and backtrack.", @@ -2516,8 +2714,8 @@ "title":"Key Operations Supported by CTS", "uri":"rds_sqlserver_06_0004.html", "doc_type":"usermanual", - "p_code":"279", - "code":"280" + "p_code":"301", + "code":"302" }, { "desc":"After CTS is enabled, operations on cloud resources are recorded. You can view the operation records of the last 7 days on the CTS console.This section describes how to q", @@ -2525,8 +2723,8 @@ "title":"Viewing Tracing Events", "uri":"rds_sqlserver_06_0005.html", "doc_type":"usermanual", - "p_code":"279", - "code":"281" + "p_code":"301", + "code":"303" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2534,8 +2732,8 @@ "title":"Log Management", "uri":"rds_sqlserver_log.html", "doc_type":"usermanual", - "p_code":"223", - "code":"282" + "p_code":"242", + "code":"304" }, { "desc":"System logs contain logs generated during the database running. These can help you analyze problems with the database.You can select a log level in the upper right corner", @@ -2543,8 +2741,8 @@ "title":"Viewing System Logs", "uri":"rds_sqlserver_01_0002.html", "doc_type":"usermanual", - "p_code":"282", - "code":"283" + "p_code":"304", + "code":"305" }, { "desc":"Slow query logs record statements that exceed long_query_time (1 second by default). You can view log details to identify statements that are executing slowly and optimiz", @@ -2552,8 +2750,8 @@ "title":"Viewing and Downloading Slow Query Logs", "uri":"slow_query_log-sqlserver.html", "doc_type":"usermanual", - "p_code":"282", - "code":"284" + "p_code":"304", + "code":"306" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2561,8 +2759,8 @@ "title":"Task Center", "uri":"rds_sqlserver_05_0007.html", "doc_type":"usermanual", - "p_code":"223", - "code":"285" + "p_code":"242", + "code":"307" }, { "desc":"You can view the progress and results of tasks on the Task Center page.You can view and manage the following tasks:Creating DB instancesCreating read replicasChanging sin", @@ -2570,8 +2768,8 @@ "title":"Viewing a Task", "uri":"rds_sqlserver_task_0001.html", "doc_type":"usermanual", - "p_code":"285", - "code":"286" + "p_code":"307", + "code":"308" }, { "desc":"You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or t", @@ -2579,8 +2777,8 @@ "title":"Deleting a Task Record", "uri":"rds_sqlserver_task_0002.html", "doc_type":"usermanual", - "p_code":"285", - "code":"287" + "p_code":"307", + "code":"309" }, { "desc":"Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags g", @@ -2588,8 +2786,8 @@ "title":"Managing Tags", "uri":"rds_sqlserver_tag.html", "doc_type":"usermanual", - "p_code":"223", - "code":"288" + "p_code":"242", + "code":"310" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2598,7 +2796,7 @@ "uri":"rds_faq_0000.html", "doc_type":"usermanual", "p_code":"", - "code":"289" + "code":"311" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2606,8 +2804,8 @@ "title":"Product Consulting", "uri":"rds_faq_0146.html", "doc_type":"usermanual", - "p_code":"289", - "code":"290" + "p_code":"311", + "code":"312" }, { "desc":"DB instance operating systems (OSs) are invisible to you. Your applications can access a database only through an IP address and a port.The backup files stored in Object ", @@ -2615,8 +2813,8 @@ "title":"What Should I Pay Attention to When Using RDS?", "uri":"rds_faq_0001.html", "doc_type":"usermanual", - "p_code":"290", - "code":"291" + "p_code":"312", + "code":"313" }, { "desc":"Calculation formula for RDS DB instance availability:DB instance availability = (1 – Failure duration/Total service duration) × 100%", @@ -2624,8 +2822,8 @@ "title":"What Is the Availability of RDS DB Instances?", "uri":"rds_faq_0002.html", "doc_type":"usermanual", - "p_code":"290", - "code":"292" + "p_code":"312", + "code":"314" }, { "desc":"Currently, DB instance cannot be created using a template.", @@ -2633,8 +2831,8 @@ "title":"Can I Use a Template to Create DB Instances?", "uri":"rds_faq_0003.html", "doc_type":"usermanual", - "p_code":"290", - "code":"293" + "p_code":"312", + "code":"315" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2642,8 +2840,8 @@ "title":"What Are the Differences Between RDS and Other Database Solutions?", "uri":"rds_faq_0004.html", "doc_type":"usermanual", - "p_code":"290", - "code":"294" + "p_code":"312", + "code":"316" }, { "desc":"No. Your RDS DB instances and resources are isolated from other users' DB instances.", @@ -2651,8 +2849,8 @@ "title":"Will My RDS DB Instances Be Affected by Other User Instances?", "uri":"rds_faq_0005.html", "doc_type":"usermanual", - "p_code":"290", - "code":"295" + "p_code":"312", + "code":"317" }, { "desc":"Yes. RDS supports cross-AZ high availability. When you create primary/standby DB instances, you can select different AZs for them.", @@ -2660,8 +2858,8 @@ "title":"Does RDS Support Cross-AZ High Availability?", "uri":"rds_faq_0073.html", "doc_type":"usermanual", - "p_code":"290", - "code":"296" + "p_code":"312", + "code":"318" }, { "desc":"No. RDS single DB instances can be changed to primary/standby DB instances, but not the other way around.", @@ -2669,8 +2867,8 @@ "title":"Can RDS Primary/Standby DB Instances Be Changed to Single DB Instances?", "uri":"rds_faq_0104.html", "doc_type":"usermanual", - "p_code":"290", - "code":"297" + "p_code":"312", + "code":"319" }, { "desc":"The default code is utf8. You need to convert the default code to Unicode in the exported Excel file.", @@ -2678,8 +2876,8 @@ "title":"What Should I Do If Garbled Characters Are Displayed After SQL Query Results Are Exported to an Excel File?", "uri":"rds_faq_0110.html", "doc_type":"usermanual", - "p_code":"290", - "code":"298" + "p_code":"312", + "code":"320" }, { "desc":"To solve this problem:Check the performance of RDS DB instances on the RDS console.Compare the database connection status of local databases and RDS DB instances. This pr", @@ -2687,8 +2885,8 @@ "title":"What Can I Do About Slow Respond of Websites When They Use RDS?", "uri":"rds_faq_0008.html", "doc_type":"usermanual", - "p_code":"290", - "code":"299" + "p_code":"312", + "code":"321" }, { "desc":"RDS provides the high availability. Select the primary/standby mode.Also called an unplanned handover. If the primary DB instance fails, the system will automatically swi", @@ -2696,8 +2894,8 @@ "title":"How Does a Cloud Database Perform a Primary/Standby Switchover?", "uri":"rds_faq_0065.html", "doc_type":"usermanual", - "p_code":"290", - "code":"300" + "p_code":"312", + "code":"322" }, { "desc":"Multiple ECSs can connect to the same RDS DB instance as long as the capability limits of a database are not exceeded.", @@ -2705,8 +2903,8 @@ "title":"Can Multiple ECSs Connect to the Same RDS DB Instance?", "uri":"rds_faq_0013.html", "doc_type":"usermanual", - "p_code":"290", - "code":"301" + "p_code":"312", + "code":"323" }, { "desc":"An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.The database 'xxx", @@ -2714,8 +2912,8 @@ "title":"Why Is an Error Reported When I Attempt to Delete a Database from RDS SQL Server Primary/Standby DB Instances?", "uri":"rds_faq_0094.html", "doc_type":"usermanual", - "p_code":"290", - "code":"302" + "p_code":"312", + "code":"324" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2723,8 +2921,8 @@ "title":"Resource and Disk Management", "uri":"rds_faq_0145.html", "doc_type":"usermanual", - "p_code":"289", - "code":"303" + "p_code":"311", + "code":"325" }, { "desc":"The following logs and files occupy RDS storage space.If the original storage space is insufficient as your services grow, scale up storage space of your DB instance.If d", @@ -2732,8 +2930,8 @@ "title":"Which Types of Logs and Files Occupy RDS Storage Space?", "uri":"rds_faq_0049.html", "doc_type":"usermanual", - "p_code":"303", - "code":"304" + "p_code":"325", + "code":"326" }, { "desc":"Both your common data (excluding backup data) and the data required for the operation of your DB instances (such as system database data, rollback logs, redo logs, and in", @@ -2741,8 +2939,8 @@ "title":"Which Items Occupy the Storage Space of My RDS DB Instances?", "uri":"rds_faq_0047.html", "doc_type":"usermanual", - "p_code":"303", - "code":"305" + "p_code":"325", + "code":"327" }, { "desc":"The storage space you applied for will include space for the file system overhead required for inode, reserved block, and database operations.", @@ -2750,8 +2948,8 @@ "title":"What Overhead Does the Storage Space Have After I Applied for an RDS DB Instance?", "uri":"rds_faq_0048.html", "doc_type":"usermanual", - "p_code":"303", - "code":"306" + "p_code":"325", + "code":"328" }, { "desc":"Data Definition Language (DDL) operations may increase storage space usage sharply. To ensure that services are running properly, do not perform DDL operations during pea", @@ -2759,8 +2957,8 @@ "title":"How Much Storage Space Is Required for DDL Operations?", "uri":"rds_faq_0082.html", "doc_type":"usermanual", - "p_code":"303", - "code":"307" + "p_code":"325", + "code":"329" }, { "desc":"There are no limitations on the number of DB instances running on RDS.", @@ -2768,8 +2966,8 @@ "title":"How Many DB Instances Can Run on RDS?", "uri":"rds_faq_0006.html", "doc_type":"usermanual", - "p_code":"303", - "code":"308" + "p_code":"325", + "code":"330" }, { "desc":"The maximum number of databases that can run on an RDS DB instance depends on the DB engine settings.If there are enough CPU, memory, and storage resources, there are no ", @@ -2777,8 +2975,8 @@ "title":"How Many Databases Can Run on an RDS DB Instance?", "uri":"rds_faq_0007.html", "doc_type":"usermanual", - "p_code":"303", - "code":"309" + "p_code":"325", + "code":"331" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2786,8 +2984,8 @@ "title":"Database Connection", "uri":"rds_faq_0141.html", "doc_type":"usermanual", - "p_code":"289", - "code":"310" + "p_code":"311", + "code":"332" }, { "desc":"For a DB instance that has an EIP bound, you can access it through the EIP.Enable a VPN in a VPC and use the VPN to connect to the RDS DB instance.Create an RDS and an EC", @@ -2795,8 +2993,8 @@ "title":"Can an External Server Access the RDS Database?", "uri":"rds_faq_0018.html", "doc_type":"usermanual", - "p_code":"310", - "code":"311" + "p_code":"332", + "code":"333" }, { "desc":"The number of database connections indicates the number of applications that can be simultaneously connected to a database, and is irrelevant to the maximum number of use", @@ -2804,8 +3002,8 @@ "title":"What Do I Do If the Number of RDS Database Connections Reaches the Upper Limit?", "uri":"rds_faq_0019.html", "doc_type":"usermanual", - "p_code":"310", - "code":"312" + "p_code":"332", + "code":"334" }, { "desc":"RDS does not have constraints on the number of connections. This number is determined by the default value and value range of the DB engine. For example, you can set max_", @@ -2813,8 +3011,8 @@ "title":"What Is the Maximum Number of Connections to an RDS DB Instance?", "uri":"rds_faq_0055.html", "doc_type":"usermanual", - "p_code":"310", - "code":"313" + "p_code":"332", + "code":"335" }, { "desc":"For details about how to create an ECS, see the Elastic Cloud Server User Guide.If you connect to an RDS DB instance through a private network, ensure that the ECS and DB", @@ -2822,8 +3020,8 @@ "title":"How Can I Create and Connect to an ECS?", "uri":"rds_faq_0057.html", "doc_type":"usermanual", - "p_code":"310", - "code":"314" + "p_code":"332", + "code":"336" }, { "desc":"Perform the following steps to identify the problem:If they are in the same VPC, go to 2.If they are in different VPCs, create an ECS in the VPC in which the RDS DB insta", @@ -2831,8 +3029,8 @@ "title":"What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?", "uri":"rds_faq_0020.html", "doc_type":"usermanual", - "p_code":"310", - "code":"315" + "p_code":"332", + "code":"337" }, { "desc":"Troubleshoot RDS connection failures caused by a client problem by checking the following items:ECS Security PolicyIn Windows, check whether the RDS instance port is enab", @@ -2840,8 +3038,8 @@ "title":"What Should I Do If a Database Client Problem Causes a Connection Failure?", "uri":"rds_faq_0021.html", "doc_type":"usermanual", - "p_code":"310", - "code":"316" + "p_code":"332", + "code":"338" }, { "desc":"Check whether any of the following problems occurred on the RDS DB instance.The RDS DB instance is not properly connected.Solution: Check the connection. If you connect t", @@ -2849,8 +3047,8 @@ "title":"What Should I Do If an RDS Database Problem Causes a Connection Failure?", "uri":"rds_faq_0022.html", "doc_type":"usermanual", - "p_code":"310", - "code":"317" + "p_code":"332", + "code":"339" }, { "desc":"Ensure that the ECS in which your applications are located is in the same VPC as the RDS DB instance. If the ECS and the RDS DB instance are in different VPCs, modify the", @@ -2858,8 +3056,8 @@ "title":"How Do My Applications Access an RDS DB Instance in a VPC?", "uri":"rds_faq_0023.html", "doc_type":"usermanual", - "p_code":"310", - "code":"318" + "p_code":"332", + "code":"340" }, { "desc":"It is recommended that your applications support automatic reconnections to the database. After a database reboot, your applications will automatically reconnect to the d", @@ -2867,8 +3065,8 @@ "title":"Do Applications Need to Support Reconnecting to the RDS DB Instance Automatically?", "uri":"rds_faq_0024.html", "doc_type":"usermanual", - "p_code":"310", - "code":"319" + "p_code":"332", + "code":"341" }, { "desc":"Although the SSL certificate is optional if you choose to connect to a database through Java database connectivity (JDBC), download an SSL certificate to encrypt the conn", @@ -2876,8 +3074,8 @@ "title":"How Can I Connect to a PostgreSQL Database Through JDBC?", "uri":"rds_faq_0050.html", "doc_type":"usermanual", - "p_code":"310", - "code":"320" + "p_code":"332", + "code":"342" }, { "desc":"Check whether the ECS can connect to the RDS DB instance.If the ECS cannot connect to the RDS DB instance, check whether the ECS and RDS DB instance are located in the sa", @@ -2885,8 +3083,8 @@ "title":"What Should I Do If an RDS Microsoft SQL Server DB Instance Failed to Be Connected?", "uri":"rds_faq_0100.html", "doc_type":"usermanual", - "p_code":"310", - "code":"321" + "p_code":"332", + "code":"343" }, { "desc":"By default, RDS DB instances cannot be accessed over an intranet across regions. Cloud services in different regions cannot communicate with each other over an intranet. ", @@ -2894,8 +3092,8 @@ "title":"Can I Access an RDS DB Instance Over an Intranet Connection Across Regions?", "uri":"rds_faq_0101.html", "doc_type":"usermanual", - "p_code":"310", - "code":"322" + "p_code":"332", + "code":"344" }, { "desc":"For DB instances connected using SSL, a primary/standby switchover or failover does not interrupt the connection because the SSL certificate is still valid for both the p", @@ -2903,8 +3101,8 @@ "title":"Is an SSL Connection to a DB Instance Interrupted After a Primary/Standby Switchover or Failover?", "uri":"rds_faq_0111.html", "doc_type":"usermanual", - "p_code":"310", - "code":"323" + "p_code":"332", + "code":"345" }, { "desc":"MySQL supports SSL connections. Different from other vendors, RDS for MySQL enables the SSL connection on the database server by default. When you use a client to connect", @@ -2912,8 +3110,8 @@ "title":"Does MySQL Support SSL Connections?", "uri":"rds_faq_0070.html", "doc_type":"usermanual", - "p_code":"310", - "code":"324" + "p_code":"332", + "code":"346" }, { "desc":"You may have restored from a backup before you reset the administrator password.Check whether the DB instance was restored after you reset the administrator password.Log ", @@ -2921,8 +3119,8 @@ "title":"Why Did the New Password Not Take Effect After I Reset the Administrator Password?", "uri":"rds_faq_0034.html", "doc_type":"usermanual", - "p_code":"310", - "code":"325" + "p_code":"332", + "code":"347" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2930,8 +3128,8 @@ "title":"Database Migration", "uri":"rds_faq_0155.html", "doc_type":"usermanual", - "p_code":"289", - "code":"326" + "p_code":"311", + "code":"348" }, { "desc":"The mysqldump or pg_dump tool is easy to use for data migration. However, when you use this tool, the server is stopped for a long period of time during data migration. O", @@ -2939,8 +3137,8 @@ "title":"Why Do I Need to Use the mysqldump or pg_dump Tools for Migration?", "uri":"rds_faq_0026.html", "doc_type":"usermanual", - "p_code":"326", - "code":"327" + "p_code":"348", + "code":"349" }, { "desc":"Exporting or importing data between DB engines of the same type is called homogeneous database export or import.Exporting or importing data between DB engines of differen", @@ -2948,8 +3146,8 @@ "title":"What Types of DB Engines Does RDS Support for Importing Data?", "uri":"rds_faq_0025.html", "doc_type":"usermanual", - "p_code":"326", - "code":"328" + "p_code":"348", + "code":"350" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2957,8 +3155,8 @@ "title":"Database Permission", "uri":"rds_faq_0154.html", "doc_type":"usermanual", - "p_code":"289", - "code":"329" + "p_code":"311", + "code":"351" }, { "desc":"Most relational database cloud service platforms do not provide super permissions for the root user. The super permissions allow users to execute many management commands", @@ -2966,8 +3164,8 @@ "title":"Why Does the Root User Not Have the Super Permissions?", "uri":"rds_faq_0075.html", "doc_type":"usermanual", - "p_code":"329", - "code":"330" + "p_code":"351", + "code":"352" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -2975,8 +3173,8 @@ "title":"Database Storage", "uri":"rds_faq_0144.html", "doc_type":"usermanual", - "p_code":"289", - "code":"331" + "p_code":"311", + "code":"353" }, { "desc":"The database storage engine is a core service for storing, processing, and protecting data. It can be used to control access permissions and rapidly process transactions ", @@ -2984,8 +3182,8 @@ "title":"What Storage Engines Does the RDS for MySQL Support?", "uri":"rds_faq_0041.html", "doc_type":"usermanual", - "p_code":"331", - "code":"332" + "p_code":"353", + "code":"354" }, { "desc":"RDS uses Elastic Volume Service (EVS) disks for storage. For details about EVS disks, see Elastic Volume Service Product Introduction.The RDS backup data is stored in OBS", @@ -2993,8 +3191,8 @@ "title":"What Is the RDS DB Instance Storage Configuration?", "uri":"rds_faq_0045.html", "doc_type":"usermanual", - "p_code":"331", - "code":"333" + "p_code":"353", + "code":"355" }, { "desc":"No. After an RDS DB instance is created, the storage type cannot be changed.", @@ -3002,8 +3200,8 @@ "title":"Can I Change the Storage Type of an RDS DB Instance from Common I/O to Ultra-high I/O?", "uri":"rds_faq_0076.html", "doc_type":"usermanual", - "p_code":"331", - "code":"334" + "p_code":"353", + "code":"356" }, { "desc":"There is not enough storage available for an RDS DB instance and the DB instance has entered read-only status, or applications can no longer read from or write to the dat", @@ -3011,8 +3209,8 @@ "title":"What Should I Do If My Data Exceeds the Available Storage of an RDS DB Instance?", "uri":"rds_faq_0046.html", "doc_type":"usermanual", - "p_code":"331", - "code":"335" + "p_code":"353", + "code":"357" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3020,8 +3218,8 @@ "title":"Client Installation", "uri":"rds_faq_0152.html", "doc_type":"usermanual", - "p_code":"289", - "code":"336" + "p_code":"311", + "code":"358" }, { "desc":"MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package", @@ -3029,17 +3227,17 @@ "title":"How Can I Install the MySQL Client?", "uri":"rds_faq_0027.html", "doc_type":"usermanual", - "p_code":"336", - "code":"337" + "p_code":"358", + "code":"359" }, { - "desc":"PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.Ensure that the database clien", + "desc":"PostgreSQL provides client installation methods for different OSs on its official website.The following describes how to install a PostgreSQL 12 client in CentOS.When you", "product_code":"rds", "title":"How Can I Install the PostgreSQL Client?", "uri":"rds_faq_0029.html", "doc_type":"usermanual", - "p_code":"336", - "code":"338" + "p_code":"358", + "code":"360" }, { "desc":"The Microsoft SQL Server official website provides the SQL Server Management Studio installation package. SQL Server Management Studio applications can run in the Windows", @@ -3047,8 +3245,8 @@ "title":"How Can I Install SQL Server Management Studio?", "uri":"rds_faq_0032.html", "doc_type":"usermanual", - "p_code":"336", - "code":"339" + "p_code":"358", + "code":"361" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3056,8 +3254,8 @@ "title":"Backup and Restoration", "uri":"rds_faq_0098.html", "doc_type":"usermanual", - "p_code":"289", - "code":"340" + "p_code":"311", + "code":"362" }, { "desc":"Automated backup data is kept based on the backup retention period you specified. There is no limit for the manual backup retention period. You can delete manual backups ", @@ -3065,8 +3263,8 @@ "title":"How Long Does RDS Store Backup Data For?", "uri":"rds_faq_0043.html", "doc_type":"usermanual", - "p_code":"340", - "code":"341" + "p_code":"362", + "code":"363" }, { "desc":"A backup window is a user-specified time during which RDS DB instances are backed up. With these periodic data backups, RDS allows you to restore DB instances to the back", @@ -3074,8 +3272,8 @@ "title":"Can My Database Be Used in the Backup Window?", "uri":"rds_faq_0044.html", "doc_type":"usermanual", - "p_code":"340", - "code":"342" + "p_code":"362", + "code":"364" }, { "desc":"You can back up data to an ECS the same way you export SQL statements. The ECS service does not have restrictions on the types of data to be backed up as long as the data", @@ -3083,8 +3281,8 @@ "title":"How Can I Back Up an RDS Database to an ECS?", "uri":"rds_faq_0042.html", "doc_type":"usermanual", - "p_code":"340", - "code":"343" + "p_code":"362", + "code":"365" }, { "desc":"Automated backups may fail for the following reasons:The network environment is unstable due to issues such as network delay or interruption. RDS will detect these proble", @@ -3092,8 +3290,8 @@ "title":"Why Has My Automated Backup Failed?", "uri":"rds_faq_0053.html", "doc_type":"usermanual", - "p_code":"340", - "code":"344" + "p_code":"362", + "code":"366" }, { "desc":"When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.", @@ -3101,8 +3299,8 @@ "title":"What Happens to Database Backups After an RDS DB Instance Is Deleted?", "uri":"rds_faq_0014.html", "doc_type":"usermanual", - "p_code":"340", - "code":"345" + "p_code":"362", + "code":"367" }, { "desc":"If your cloud account is deleted, both your automated and manual backups are deleted.", @@ -3110,8 +3308,8 @@ "title":"Will My Backups Be Deleted If I Delete My Cloud Account?", "uri":"rds_faq_0015.html", "doc_type":"usermanual", - "p_code":"340", - "code":"346" + "p_code":"362", + "code":"368" }, { "desc":"RDS does not delete or perform any operations on any user data. If this problem occurs, check if there have been any misoperations and restore the data from backup files,", @@ -3119,8 +3317,8 @@ "title":"Why Is a Table or Data Missing from My Database?", "uri":"rds_faq_0012.html", "doc_type":"usermanual", - "p_code":"340", - "code":"347" + "p_code":"362", + "code":"369" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3128,8 +3326,8 @@ "title":"Database Monitoring", "uri":"rds_faq_0151.html", "doc_type":"usermanual", - "p_code":"289", - "code":"348" + "p_code":"311", + "code":"370" }, { "desc":"You need to pay attention to CPU, memory, and storage space usage.You can configure the system to report alarms based on service requirements and take measures to handle ", @@ -3137,8 +3335,8 @@ "title":"Which DB Instance Monitoring Metrics Do I Need to Pay Attention To?", "uri":"rds_faq_0036.html", "doc_type":"usermanual", - "p_code":"348", - "code":"349" + "p_code":"370", + "code":"371" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3146,8 +3344,8 @@ "title":"Capacity Expansion and Specification Change", "uri":"rds_faq_0150.html", "doc_type":"usermanual", - "p_code":"289", - "code":"350" + "p_code":"311", + "code":"372" }, { "desc":"Currently, you can scale up storage space and change the CPU or memory of a DB instance.When storage space is being scaled up, RDS DB instances are still available and se", @@ -3155,8 +3353,8 @@ "title":"Are My RDS DB Instances Available When Scaling?", "uri":"rds_faq_0016.html", "doc_type":"usermanual", - "p_code":"350", - "code":"351" + "p_code":"372", + "code":"373" }, { "desc":"The DB instance is in Faulty state after the original database port is changed.The DB instance cannot be connected using the new database port.The submitted database port", @@ -3164,8 +3362,8 @@ "title":"Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?", "uri":"rds_faq_0035.html", "doc_type":"usermanual", - "p_code":"350", - "code":"352" + "p_code":"372", + "code":"374" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3173,8 +3371,8 @@ "title":"Database Parameter Modification", "uri":"rds_faq_0142.html", "doc_type":"usermanual", - "p_code":"289", - "code":"353" + "p_code":"311", + "code":"375" }, { "desc":"In the following cases, inappropriate parameter settings cause the database to be unavailable:Parameter value ranges are related to DB instance specifications.The maximum", @@ -3182,8 +3380,8 @@ "title":"What Inappropriate Parameter Settings Cause Unavailability of the PostgreSQL Database?", "uri":"rds_faq_0031.html", "doc_type":"usermanual", - "p_code":"353", - "code":"354" + "p_code":"375", + "code":"376" }, { "desc":"PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. For more information about test_decoding, see test_decoding introduction.To use test_", @@ -3191,8 +3389,8 @@ "title":"Does RDS for PostgreSQL Support the test_decoding Plugin?", "uri":"rds_faq_0119.html", "doc_type":"usermanual", - "p_code":"353", - "code":"355" + "p_code":"375", + "code":"377" }, { "desc":"When you add NDF files of the custom database and the tempdb database, do not place them in the C drive. If you place them in the C drive, the system disk space will be u", @@ -3200,8 +3398,8 @@ "title":"Where Should I Store the NDF Files for Microsoft SQL Server?", "uri":"rds_faq_0092.html", "doc_type":"usermanual", - "p_code":"353", - "code":"356" + "p_code":"375", + "code":"378" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3209,8 +3407,8 @@ "title":"Log Management", "uri":"rds_faq_0149.html", "doc_type":"usermanual", - "p_code":"289", - "code":"357" + "p_code":"311", + "code":"379" }, { "desc":"Generally, the delay is 5 minutes. If the size of slow query logs reaches 10 MB within 5 minutes, the logs will be uploaded to OBS.", @@ -3218,8 +3416,8 @@ "title":"How Long Is the Delay for RDS MySQL Slow Query Logs?", "uri":"rds_faq_0078.html", "doc_type":"usermanual", - "p_code":"357", - "code":"358" + "p_code":"379", + "code":"380" }, { "desc":"The slow query threshold is 5 seconds.", @@ -3227,8 +3425,8 @@ "title":"What's the Slow Query Threshold for Microsoft SQL Server?", "uri":"rds_faq_0077.html", "doc_type":"usermanual", - "p_code":"357", - "code":"359" + "p_code":"379", + "code":"381" }, { "desc":"EXECUTE master.dbo.rds_read_errorlogFileID,LogType,FilterText,FilterBeginTime,FilterEndTimeFileID: indicates the ID of an error log. The value 0 indicates the latest logs", @@ -3236,8 +3434,8 @@ "title":"How Can I Obtain Microsoft SQL Server Error Logs Using Commands?", "uri":"rds_faq_0059.html", "doc_type":"usermanual", - "p_code":"357", - "code":"360" + "p_code":"379", + "code":"382" }, { "desc":"Sorry, statistics on RDS slow query logs cannot be exported.", @@ -3245,8 +3443,8 @@ "title":"Can I Export Statistics on RDS Slow Query Logs?", "uri":"rds_faq_0120.html", "doc_type":"usermanual", - "p_code":"357", - "code":"361" + "p_code":"379", + "code":"383" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -3254,8 +3452,8 @@ "title":"Network Security", "uri":"rds_faq_0143.html", "doc_type":"usermanual", - "p_code":"289", - "code":"362" + "p_code":"311", + "code":"384" }, { "desc":"RDS runs your DB instances in a VPC, ensuring that the DB instances are isolated from other services.RDS uses security groups to ensure that only trusted sources can acce", @@ -3263,8 +3461,8 @@ "title":"What Security Protection Policies Does RDS Have?", "uri":"rds_faq_0038.html", "doc_type":"usermanual", - "p_code":"362", - "code":"363" + "p_code":"384", + "code":"385" }, { "desc":"The VPC security group helps ensure the security of RDS in a VPC. In addition, an ACL can be used to allow or reject I/O network traffic for each subnet.", @@ -3272,8 +3470,8 @@ "title":"How Can I Ensure the Security of RDS DB Instances in a VPC?", "uri":"rds_faq_0040.html", "doc_type":"usermanual", - "p_code":"362", - "code":"364" + "p_code":"384", + "code":"386" }, { "desc":"When you access RDS through an EIP, service data will be transmitted on the public network. To prevent any potential data breaches, you are advised to use SSL to encrypt ", @@ -3281,8 +3479,8 @@ "title":"How Can Data Security Be Ensured During Transmission When I Access RDS Through an EIP?", "uri":"rds_faq_0039.html", "doc_type":"usermanual", - "p_code":"362", - "code":"365" + "p_code":"384", + "code":"387" }, { "desc":"If you enable public accessibility, your EIP DNS and database port may be vulnerable to hacking. To protect information such as your EIP, DNS, database port, database acc", @@ -3290,8 +3488,8 @@ "title":"How Can I Prevent Untrusted Source IP Addresses from Accessing RDS?", "uri":"rds_faq_0056.html", "doc_type":"usermanual", - "p_code":"362", - "code":"366" + "p_code":"384", + "code":"388" }, { "desc":"When you attempt to connect to a DB instance through a private network, check whether the ECS and RDS DB instance are in the same security group.If the ECS and RDS DB ins", @@ -3299,8 +3497,8 @@ "title":"How Do I Configure a Security Group to Enable Access to RDS DB Instances?", "uri":"rds_faq_0054.html", "doc_type":"usermanual", - "p_code":"362", - "code":"367" + "p_code":"384", + "code":"389" }, { "desc":"Click Start and choose Run. In the displayed Run dialog box, enter MMC and press Enter.On the displayed console, choose File > Add/Remove Snap-in.In the left Available sn", @@ -3308,8 +3506,8 @@ "title":"How Can I Import the Root Certificate to a Windows or Linux OS?", "uri":"rds_faq_0052.html", "doc_type":"usermanual", - "p_code":"362", - "code":"368" + "p_code":"384", + "code":"390" }, { "desc":"When you connect to an RDS MySQL DB instance using an SSL connection, run the following command to check whether the certificate has expired:Update the root certificate t", @@ -3317,8 +3515,8 @@ "title":"How Can I Identify the Validity Period of an SSL Root Certificate?", "uri":"rds_faq_0051.html", "doc_type":"usermanual", - "p_code":"362", - "code":"369" + "p_code":"384", + "code":"391" }, { "desc":"Data tamperingLots of security measures are provided to ensure that only authenticated users have permissions to perform operations on database table records. Database ta", @@ -3326,17 +3524,17 @@ "title":"How Can I Identify Data Corruption?", "uri":"rds_faq_0011.html", "doc_type":"usermanual", - "p_code":"362", - "code":"370" + "p_code":"384", + "code":"392" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"rds", "title":"Change History", - "uri":"en-us_topic_0000001419863378.html", + "uri":"en-us_topic_0000001191146839.html", "doc_type":"usermanual", "p_code":"", - "code":"371" + "code":"393" }, { "desc":"For details about the glossaries in this document, see Glossary.", @@ -3345,6 +3543,6 @@ "uri":"rds_glossary_0001.html", "doc_type":"usermanual", "p_code":"", - "code":"372" + "code":"394" } ] \ No newline at end of file diff --git a/docs/rds/umn/en-us_image_0000001420181154.png b/docs/rds/umn/en-us_image_0000001145051556.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181154.png rename to docs/rds/umn/en-us_image_0000001145051556.png diff --git a/docs/rds/umn/en-us_image_0000001420340466.png b/docs/rds/umn/en-us_image_0000001145051596.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340466.png rename to docs/rds/umn/en-us_image_0000001145051596.png diff --git a/docs/rds/umn/en-us_image_0000001470140361.png b/docs/rds/umn/en-us_image_0000001145051606.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140361.png rename to docs/rds/umn/en-us_image_0000001145051606.png diff --git a/docs/rds/umn/en-us_image_0000001420023666.png b/docs/rds/umn/en-us_image_0000001145051612.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023666.png rename to docs/rds/umn/en-us_image_0000001145051612.png diff --git a/docs/rds/umn/en-us_image_0000001419863630.jpg b/docs/rds/umn/en-us_image_0000001145051614.jpg similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863630.jpg rename to docs/rds/umn/en-us_image_0000001145051614.jpg diff --git a/docs/rds/umn/en-us_image_0000001420181410.png b/docs/rds/umn/en-us_image_0000001145051618.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181410.png rename to docs/rds/umn/en-us_image_0000001145051618.png diff --git a/docs/rds/umn/en-us_image_0000001420340614.png b/docs/rds/umn/en-us_image_0000001145051626.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340614.png rename to docs/rds/umn/en-us_image_0000001145051626.png diff --git a/docs/rds/umn/en-us_image_0000001469940709.png b/docs/rds/umn/en-us_image_0000001145051640.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940709.png rename to docs/rds/umn/en-us_image_0000001145051640.png diff --git a/docs/rds/umn/en-us_image_0000001419863802.png b/docs/rds/umn/en-us_image_0000001145051660.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863802.png rename to docs/rds/umn/en-us_image_0000001145051660.png diff --git a/docs/rds/umn/en-us_image_0000001469940745.png b/docs/rds/umn/en-us_image_0000001145051704.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940745.png rename to docs/rds/umn/en-us_image_0000001145051704.png diff --git a/docs/rds/umn/en-us_image_0000001470340153.png b/docs/rds/umn/en-us_image_0000001145051706.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340153.png rename to docs/rds/umn/en-us_image_0000001145051706.png diff --git a/docs/rds/umn/en-us_image_0000001420023814.png b/docs/rds/umn/en-us_image_0000001145051720.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023814.png rename to docs/rds/umn/en-us_image_0000001145051720.png diff --git a/docs/rds/umn/en-us_image_0000001469940677.png b/docs/rds/umn/en-us_image_0000001145051730.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940677.png rename to docs/rds/umn/en-us_image_0000001145051730.png diff --git a/docs/rds/umn/en-us_image_0000001419863594.png b/docs/rds/umn/en-us_image_0000001145051736.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863594.png rename to docs/rds/umn/en-us_image_0000001145051736.png diff --git a/docs/rds/umn/en-us_image_0000001419863886.png b/docs/rds/umn/en-us_image_0000001145051738.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863886.png rename to docs/rds/umn/en-us_image_0000001145051738.png diff --git a/docs/rds/umn/en-us_image_0000001420340718.png b/docs/rds/umn/en-us_image_0000001145051740.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340718.png rename to docs/rds/umn/en-us_image_0000001145051740.png diff --git a/docs/rds/umn/en-us_image_0000001420023606.png b/docs/rds/umn/en-us_image_0000001145051748.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023606.png rename to docs/rds/umn/en-us_image_0000001145051748.png diff --git a/docs/rds/umn/en-us_image_0000001469940773.png b/docs/rds/umn/en-us_image_0000001145051752.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940773.png rename to docs/rds/umn/en-us_image_0000001145051752.png diff --git a/docs/rds/umn/en-us_image_0000001470340297.png b/docs/rds/umn/en-us_image_0000001145051772.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340297.png rename to docs/rds/umn/en-us_image_0000001145051772.png diff --git a/docs/rds/umn/en-us_image_0000001469940653.png b/docs/rds/umn/en-us_image_0000001145051794.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940653.png rename to docs/rds/umn/en-us_image_0000001145051794.png diff --git a/docs/rds/umn/en-us_image_0000001419863730.png b/docs/rds/umn/en-us_image_0000001145051802.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863730.png rename to docs/rds/umn/en-us_image_0000001145051802.png diff --git a/docs/rds/umn/en-us_image_0000001419863746.png b/docs/rds/umn/en-us_image_0000001145051804.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863746.png rename to docs/rds/umn/en-us_image_0000001145051804.png diff --git a/docs/rds/umn/en-us_image_0000001419863830.png b/docs/rds/umn/en-us_image_0000001145051822.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863830.png rename to docs/rds/umn/en-us_image_0000001145051822.png diff --git a/docs/rds/umn/en-us_image_0000001420181438.png b/docs/rds/umn/en-us_image_0000001145051824.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181438.png rename to docs/rds/umn/en-us_image_0000001145051824.png diff --git a/docs/rds/umn/en-us_image_0000001420023830.png b/docs/rds/umn/en-us_image_0000001145051826.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023830.png rename to docs/rds/umn/en-us_image_0000001145051826.png diff --git a/docs/rds/umn/en-us_image_0000001420023658.png b/docs/rds/umn/en-us_image_0000001145051850.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023658.png rename to docs/rds/umn/en-us_image_0000001145051850.png diff --git a/docs/rds/umn/en-us_image_0000001420181302.png b/docs/rds/umn/en-us_image_0000001145211348.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181302.png rename to docs/rds/umn/en-us_image_0000001145211348.png diff --git a/docs/rds/umn/en-us_image_0000001469940721.png b/docs/rds/umn/en-us_image_0000001145211356.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940721.png rename to docs/rds/umn/en-us_image_0000001145211356.png diff --git a/docs/rds/umn/en-us_image_0000001469940645.png b/docs/rds/umn/en-us_image_0000001145211382.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940645.png rename to docs/rds/umn/en-us_image_0000001145211382.png diff --git a/docs/rds/umn/en-us_image_0000001419863754.png b/docs/rds/umn/en-us_image_0000001145211388.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863754.png rename to docs/rds/umn/en-us_image_0000001145211388.png diff --git a/docs/rds/umn/en-us_image_0000001470140357.png b/docs/rds/umn/en-us_image_0000001145211412.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140357.png rename to docs/rds/umn/en-us_image_0000001145211412.png diff --git a/docs/rds/umn/en-us_image_0000001420023654.png b/docs/rds/umn/en-us_image_0000001145211414.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023654.png rename to docs/rds/umn/en-us_image_0000001145211414.png diff --git a/docs/rds/umn/en-us_image_0000001420340582.png b/docs/rds/umn/en-us_image_0000001145211428.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340582.png rename to docs/rds/umn/en-us_image_0000001145211428.png diff --git a/docs/rds/umn/en-us_image_0000001420181286.png b/docs/rds/umn/en-us_image_0000001145211434.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181286.png rename to docs/rds/umn/en-us_image_0000001145211434.png diff --git a/docs/rds/umn/en-us_image_0000001420340634.png b/docs/rds/umn/en-us_image_0000001145211446.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340634.png rename to docs/rds/umn/en-us_image_0000001145211446.png diff --git a/docs/rds/umn/en-us_image_0000001420181422.png b/docs/rds/umn/en-us_image_0000001145211470.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181422.png rename to docs/rds/umn/en-us_image_0000001145211470.png diff --git a/docs/rds/umn/en-us_image_0000001470260245.png b/docs/rds/umn/en-us_image_0000001145211472.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260245.png rename to docs/rds/umn/en-us_image_0000001145211472.png diff --git a/docs/rds/umn/en-us_image_0000001469940765.png b/docs/rds/umn/en-us_image_0000001145211482.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940765.png rename to docs/rds/umn/en-us_image_0000001145211482.png diff --git a/docs/rds/umn/en-us_image_0000001420023746.png b/docs/rds/umn/en-us_image_0000001145211492.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023746.png rename to docs/rds/umn/en-us_image_0000001145211492.png diff --git a/docs/rds/umn/en-us_image_0000001469940697.png b/docs/rds/umn/en-us_image_0000001145211498.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940697.png rename to docs/rds/umn/en-us_image_0000001145211498.png diff --git a/docs/rds/umn/en-us_image_0000001420340598.png b/docs/rds/umn/en-us_image_0000001145211504.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340598.png rename to docs/rds/umn/en-us_image_0000001145211504.png diff --git a/docs/rds/umn/en-us_image_0000001420023810.png b/docs/rds/umn/en-us_image_0000001145211526.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023810.png rename to docs/rds/umn/en-us_image_0000001145211526.png diff --git a/docs/rds/umn/en-us_image_0000001470140545.png b/docs/rds/umn/en-us_image_0000001145211530.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140545.png rename to docs/rds/umn/en-us_image_0000001145211530.png diff --git a/docs/rds/umn/en-us_image_0000001419863674.png b/docs/rds/umn/en-us_image_0000001145211550.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863674.png rename to docs/rds/umn/en-us_image_0000001145211550.png diff --git a/docs/rds/umn/en-us_image_0000001469940813.png b/docs/rds/umn/en-us_image_0000001145211620.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940813.png rename to docs/rds/umn/en-us_image_0000001145211620.png diff --git a/docs/rds/umn/en-us_image_0000001470260045.png b/docs/rds/umn/en-us_image_0000001145211626.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260045.png rename to docs/rds/umn/en-us_image_0000001145211626.png diff --git a/docs/rds/umn/en-us_image_0000001420340574.png b/docs/rds/umn/en-us_image_0000001145211644.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340574.png rename to docs/rds/umn/en-us_image_0000001145211644.png diff --git a/docs/rds/umn/en-us_image_0000001419863698.png b/docs/rds/umn/en-us_image_0000001191131291.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863698.png rename to docs/rds/umn/en-us_image_0000001191131291.png diff --git a/docs/rds/umn/en-us_image_0000001420023530.png b/docs/rds/umn/en-us_image_0000001191131295.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023530.png rename to docs/rds/umn/en-us_image_0000001191131295.png diff --git a/docs/rds/umn/en-us_image_0000001470140377.png b/docs/rds/umn/en-us_image_0000001191131297.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140377.png rename to docs/rds/umn/en-us_image_0000001191131297.png diff --git a/docs/rds/umn/en-us_image_0000001420181450.png b/docs/rds/umn/en-us_image_0000001191131307.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181450.png rename to docs/rds/umn/en-us_image_0000001191131307.png diff --git a/docs/rds/umn/en-us_image_0000001420340506.png b/docs/rds/umn/en-us_image_0000001191131309.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340506.png rename to docs/rds/umn/en-us_image_0000001191131309.png diff --git a/docs/rds/umn/en-us_image_0000001420023698.png b/docs/rds/umn/en-us_image_0000001191131321.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023698.png rename to docs/rds/umn/en-us_image_0000001191131321.png diff --git a/docs/rds/umn/en-us_image_0000001470140481.png b/docs/rds/umn/en-us_image_0000001191131329.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140481.png rename to docs/rds/umn/en-us_image_0000001191131329.png diff --git a/docs/rds/umn/en-us_image_0000001419863834.png b/docs/rds/umn/en-us_image_0000001191131343.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863834.png rename to docs/rds/umn/en-us_image_0000001191131343.png diff --git a/docs/rds/umn/en-us_image_0000001469940729.png b/docs/rds/umn/en-us_image_0000001191131351.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940729.png rename to docs/rds/umn/en-us_image_0000001191131351.png diff --git a/docs/rds/umn/en-us_image_0000001420340670.png b/docs/rds/umn/en-us_image_0000001191131359.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420340670.png rename to docs/rds/umn/en-us_image_0000001191131359.png diff --git a/docs/rds/umn/en-us_image_0000001470340225.png b/docs/rds/umn/en-us_image_0000001191131361.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340225.png rename to docs/rds/umn/en-us_image_0000001191131361.png diff --git a/docs/rds/umn/en-us_image_0000001420023754.png b/docs/rds/umn/en-us_image_0000001191131363.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023754.png rename to docs/rds/umn/en-us_image_0000001191131363.png diff --git a/docs/rds/umn/en-us_image_0000001470260077.png b/docs/rds/umn/en-us_image_0000001191131369.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260077.png rename to docs/rds/umn/en-us_image_0000001191131369.png diff --git a/docs/rds/umn/en-us_image_0000001420181394.png b/docs/rds/umn/en-us_image_0000001191131375.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181394.png rename to docs/rds/umn/en-us_image_0000001191131375.png diff --git a/docs/rds/umn/en-us_image_0000001470260185.png b/docs/rds/umn/en-us_image_0000001191131379.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260185.png rename to docs/rds/umn/en-us_image_0000001191131379.png diff --git a/docs/rds/umn/en-us_image_0000001420023730.png b/docs/rds/umn/en-us_image_0000001191131381.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023730.png rename to docs/rds/umn/en-us_image_0000001191131381.png diff --git a/docs/rds/umn/en-us_image_0000001470340205.png b/docs/rds/umn/en-us_image_0000001191131383.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340205.png rename to docs/rds/umn/en-us_image_0000001191131383.png diff --git a/docs/rds/umn/en-us_image_0000001470140445.png b/docs/rds/umn/en-us_image_0000001191131385.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140445.png rename to docs/rds/umn/en-us_image_0000001191131385.png diff --git a/docs/rds/umn/en-us_image_0000001420023642.png b/docs/rds/umn/en-us_image_0000001191131399.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023642.png rename to docs/rds/umn/en-us_image_0000001191131399.png diff --git a/docs/rds/umn/en-us_image_0000001469940669.png b/docs/rds/umn/en-us_image_0000001191131411.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940669.png rename to docs/rds/umn/en-us_image_0000001191131411.png diff --git a/docs/rds/umn/en-us_image_0000001469940849.png b/docs/rds/umn/en-us_image_0000001191131415.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940849.png rename to docs/rds/umn/en-us_image_0000001191131415.png diff --git a/docs/rds/umn/en-us_image_0000001469940797.png b/docs/rds/umn/en-us_image_0000001191131419.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940797.png rename to docs/rds/umn/en-us_image_0000001191131419.png diff --git a/docs/rds/umn/en-us_image_0000001470140461.png b/docs/rds/umn/en-us_image_0000001191131421.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140461.png rename to docs/rds/umn/en-us_image_0000001191131421.png diff --git a/docs/rds/umn/en-us_image_0000001470260157.png b/docs/rds/umn/en-us_image_0000001191131423.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260157.png rename to docs/rds/umn/en-us_image_0000001191131423.png diff --git a/docs/rds/umn/en-us_image_0000001419863814.png b/docs/rds/umn/en-us_image_0000001191131431.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863814.png rename to docs/rds/umn/en-us_image_0000001191131431.png diff --git a/docs/rds/umn/en-us_image_0000001470340109.png b/docs/rds/umn/en-us_image_0000001191131441.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340109.png rename to docs/rds/umn/en-us_image_0000001191131441.png diff --git a/docs/rds/umn/en-us_image_0000001420181290.png b/docs/rds/umn/en-us_image_0000001191131443.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181290.png rename to docs/rds/umn/en-us_image_0000001191131443.png diff --git a/docs/rds/umn/en-us_image_0000001420023822.png b/docs/rds/umn/en-us_image_0000001191131447.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023822.png rename to docs/rds/umn/en-us_image_0000001191131447.png diff --git a/docs/rds/umn/en-us_image_0000001470140409.png b/docs/rds/umn/en-us_image_0000001191131453.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140409.png rename to docs/rds/umn/en-us_image_0000001191131453.png diff --git a/docs/rds/umn/en-us_image_0000001420023750.png b/docs/rds/umn/en-us_image_0000001191131469.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023750.png rename to docs/rds/umn/en-us_image_0000001191131469.png diff --git a/docs/rds/umn/en-us_image_0000001470260089.png b/docs/rds/umn/en-us_image_0000001191131497.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260089.png rename to docs/rds/umn/en-us_image_0000001191131497.png diff --git a/docs/rds/umn/en-us_image_0000001470140389.png b/docs/rds/umn/en-us_image_0000001191211383.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140389.png rename to docs/rds/umn/en-us_image_0000001191211383.png diff --git a/docs/rds/umn/en-us_image_0000001420023546.png b/docs/rds/umn/en-us_image_0000001191211385.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023546.png rename to docs/rds/umn/en-us_image_0000001191211385.png diff --git a/docs/rds/umn/en-us_image_0000001470140341.png b/docs/rds/umn/en-us_image_0000001191211393.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140341.png rename to docs/rds/umn/en-us_image_0000001191211393.png diff --git a/docs/rds/umn/en-us_image_0000001470340005.png b/docs/rds/umn/en-us_image_0000001191211405.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340005.png rename to docs/rds/umn/en-us_image_0000001191211405.png diff --git a/docs/rds/umn/en-us_image_0000001469940665.png b/docs/rds/umn/en-us_image_0000001191211443.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940665.png rename to docs/rds/umn/en-us_image_0000001191211443.png diff --git a/docs/rds/umn/en-us_image_0000001470340125.png b/docs/rds/umn/en-us_image_0000001191211447.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340125.png rename to docs/rds/umn/en-us_image_0000001191211447.png diff --git a/docs/rds/umn/en-us_image_0000001470140289.png b/docs/rds/umn/en-us_image_0000001191211449.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140289.png rename to docs/rds/umn/en-us_image_0000001191211449.png diff --git a/docs/rds/umn/en-us_image_0000001470260029.png b/docs/rds/umn/en-us_image_0000001191211453.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260029.png rename to docs/rds/umn/en-us_image_0000001191211453.png diff --git a/docs/rds/umn/en-us_image_0000001470260141.png b/docs/rds/umn/en-us_image_0000001191211455.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260141.png rename to docs/rds/umn/en-us_image_0000001191211455.png diff --git a/docs/rds/umn/en-us_image_0000001419863714.jpg b/docs/rds/umn/en-us_image_0000001191211461.jpg similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863714.jpg rename to docs/rds/umn/en-us_image_0000001191211461.jpg diff --git a/docs/rds/umn/en-us_image_0000001470140373.png b/docs/rds/umn/en-us_image_0000001191211463.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140373.png rename to docs/rds/umn/en-us_image_0000001191211463.png diff --git a/docs/rds/umn/en-us_image_0000001470340169.png b/docs/rds/umn/en-us_image_0000001191211477.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340169.png rename to docs/rds/umn/en-us_image_0000001191211477.png diff --git a/docs/rds/umn/en-us_image_0000001470140533.png b/docs/rds/umn/en-us_image_0000001191211495.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140533.png rename to docs/rds/umn/en-us_image_0000001191211495.png diff --git a/docs/rds/umn/en-us_image_0000001419863846.png b/docs/rds/umn/en-us_image_0000001191211507.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001419863846.png rename to docs/rds/umn/en-us_image_0000001191211507.png diff --git a/docs/rds/umn/en-us_image_0000001420023786.png b/docs/rds/umn/en-us_image_0000001191211525.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420023786.png rename to docs/rds/umn/en-us_image_0000001191211525.png diff --git a/docs/rds/umn/en-us_image_0000001470340253.png b/docs/rds/umn/en-us_image_0000001191211533.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340253.png rename to docs/rds/umn/en-us_image_0000001191211533.png diff --git a/docs/rds/umn/en-us_image_0000001470140493.png b/docs/rds/umn/en-us_image_0000001191211539.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140493.png rename to docs/rds/umn/en-us_image_0000001191211539.png diff --git a/docs/rds/umn/en-us_image_0000001470140453.png b/docs/rds/umn/en-us_image_0000001191211549.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470140453.png rename to docs/rds/umn/en-us_image_0000001191211549.png diff --git a/docs/rds/umn/en-us_image_0000001470340233.png b/docs/rds/umn/en-us_image_0000001191211551.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340233.png rename to docs/rds/umn/en-us_image_0000001191211551.png diff --git a/docs/rds/umn/en-us_image_0000001470260221.png b/docs/rds/umn/en-us_image_0000001191211573.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260221.png rename to docs/rds/umn/en-us_image_0000001191211573.png diff --git a/docs/rds/umn/en-us_image_0000001470260209.png b/docs/rds/umn/en-us_image_0000001191211577.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260209.png rename to docs/rds/umn/en-us_image_0000001191211577.png diff --git a/docs/rds/umn/en-us_image_0000001469940781.png b/docs/rds/umn/en-us_image_0000001191211583.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940781.png rename to docs/rds/umn/en-us_image_0000001191211583.png diff --git a/docs/rds/umn/en-us_image_0000001420181398.png b/docs/rds/umn/en-us_image_0000001191211585.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001420181398.png rename to docs/rds/umn/en-us_image_0000001191211585.png diff --git a/docs/rds/umn/en-us_image_0000001191211587.png b/docs/rds/umn/en-us_image_0000001191211587.png new file mode 100644 index 00000000..bfec4154 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001191211587.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340241.png b/docs/rds/umn/en-us_image_0000001191211593.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340241.png rename to docs/rds/umn/en-us_image_0000001191211593.png diff --git a/docs/rds/umn/en-us_image_0000001470340305.png b/docs/rds/umn/en-us_image_0000001191211667.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340305.png rename to docs/rds/umn/en-us_image_0000001191211667.png diff --git a/docs/rds/umn/en-us_image_0000001470260033.png b/docs/rds/umn/en-us_image_0000001191211679.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260033.png rename to docs/rds/umn/en-us_image_0000001191211679.png diff --git a/docs/rds/umn/en-us_image_0000001470260233.png b/docs/rds/umn/en-us_image_0000001206123004.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470260233.png rename to docs/rds/umn/en-us_image_0000001206123004.png diff --git a/docs/rds/umn/en-us_image_0000001419863866.png b/docs/rds/umn/en-us_image_0000001419863866.png deleted file mode 100644 index 21acd3c8..00000000 Binary files a/docs/rds/umn/en-us_image_0000001419863866.png and /dev/null differ diff --git a/docs/rds/umn/en-us_image_0000001420023818.png b/docs/rds/umn/en-us_image_0000001420023818.png deleted file mode 100644 index 2adf7d4d..00000000 Binary files a/docs/rds/umn/en-us_image_0000001420023818.png and /dev/null differ diff --git a/docs/rds/umn/en-us_image_0000001470340221.png b/docs/rds/umn/en-us_image_0000001420988282.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001470340221.png rename to docs/rds/umn/en-us_image_0000001420988282.png diff --git a/docs/rds/umn/en-us_image_0000001469940549.png b/docs/rds/umn/en-us_image_0000001426447917.png similarity index 100% rename from docs/rds/umn/en-us_image_0000001469940549.png rename to docs/rds/umn/en-us_image_0000001426447917.png diff --git a/docs/rds/umn/en-us_image_0000001444753346.png b/docs/rds/umn/en-us_image_0000001444753346.png new file mode 100644 index 00000000..08fc2d5e Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001444753346.png differ diff --git a/docs/rds/umn/en-us_image_0000001444913286.png b/docs/rds/umn/en-us_image_0000001444913286.png new file mode 100644 index 00000000..fc31bdd5 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001444913286.png differ diff --git a/docs/rds/umn/en-us_image_0000001445233198.png b/docs/rds/umn/en-us_image_0000001445233198.png new file mode 100644 index 00000000..43353c5d Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001445233198.png differ diff --git a/docs/rds/umn/en-us_image_0000001470340229.png b/docs/rds/umn/en-us_image_0000001470340229.png deleted file mode 100644 index 2057d4ed..00000000 Binary files a/docs/rds/umn/en-us_image_0000001470340229.png and /dev/null differ diff --git a/docs/rds/umn/en-us_image_0000001481965146.png b/docs/rds/umn/en-us_image_0000001481965146.png new file mode 100644 index 00000000..f41f9130 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001481965146.png differ diff --git a/docs/rds/umn/en-us_image_0000001482124730.png b/docs/rds/umn/en-us_image_0000001482124730.png new file mode 100644 index 00000000..4b159e16 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001482124730.png differ diff --git a/docs/rds/umn/en-us_image_0000001482124762.png b/docs/rds/umn/en-us_image_0000001482124762.png new file mode 100644 index 00000000..5c8bef8c Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001482124762.png differ diff --git a/docs/rds/umn/en-us_image_0000001488529446.png b/docs/rds/umn/en-us_image_0000001488529446.png new file mode 100644 index 00000000..bfec4154 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001488529446.png differ diff --git a/docs/rds/umn/en-us_image_0000001495233177.png b/docs/rds/umn/en-us_image_0000001495233177.png new file mode 100644 index 00000000..7ddb4a62 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001495233177.png differ diff --git a/docs/rds/umn/en-us_image_0000001520982189.png b/docs/rds/umn/en-us_image_0000001520982189.png new file mode 100644 index 00000000..7cabd619 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001520982189.png differ diff --git a/docs/rds/umn/en-us_image_0000001533364453.png b/docs/rds/umn/en-us_image_0000001533364453.png new file mode 100644 index 00000000..48146175 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001533364453.png differ diff --git a/docs/rds/umn/en-us_image_0000001533364489.png b/docs/rds/umn/en-us_image_0000001533364489.png new file mode 100644 index 00000000..bdb6fcc7 Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001533364489.png differ diff --git a/docs/rds/umn/en-us_image_0000001539289437.png b/docs/rds/umn/en-us_image_0000001539289437.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/rds/umn/en-us_image_0000001539289437.png differ diff --git a/docs/rds/umn/en-us_image_0192954081.png b/docs/rds/umn/en-us_image_0192954081.png new file mode 100644 index 00000000..7ae20464 Binary files /dev/null and b/docs/rds/umn/en-us_image_0192954081.png differ diff --git a/docs/rds/umn/en-us_topic_0000001419863378.html b/docs/rds/umn/en-us_topic_0000001191146839.html similarity index 50% rename from docs/rds/umn/en-us_topic_0000001419863378.html rename to docs/rds/umn/en-us_topic_0000001191146839.html index 3b63528a..d5736b5e 100644 --- a/docs/rds/umn/en-us_topic_0000001419863378.html +++ b/docs/rds/umn/en-us_topic_0000001191146839.html @@ -1,366 +1,390 @@ - +

Change History

-

Released On

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + diff --git a/docs/rds/umn/en-us_topic_0043898356.html b/docs/rds/umn/en-us_topic_0043898356.html index a01f10c5..5c10a672 100644 --- a/docs/rds/umn/en-us_topic_0043898356.html +++ b/docs/rds/umn/en-us_topic_0043898356.html @@ -25,20 +25,20 @@ - - - - - diff --git a/docs/rds/umn/en-us_topic_0046585334.html b/docs/rds/umn/en-us_topic_0046585334.html index b04a0b21..3c74407f 100644 --- a/docs/rds/umn/en-us_topic_0046585334.html +++ b/docs/rds/umn/en-us_topic_0046585334.html @@ -2,7 +2,7 @@

Operation Guide

You can create and connect to DB instances on the RDS console.

-

Flowchart

Figure 1 Flowchart
+

Flowchart

Figure 1 Flowchart

Procedure

Released On

Description

+

Description

2022-10-30

+

2023-09-14

Modified the following content:

-
  • Modified the description of the tag value in Editing a Tag.
  • Modified the description of the Administrator Password.
+

Modified the following content:

+

2022-07-22

+

2023-04-20

Modified the following content:

-

Supported Table Name settings during MySQL 8.0 instance creation in Step 1: Create a DB Instance.

+

Modified the following content:

+

Added Upgrading a Minor Version.

2022-03-22

+

2023-03-08

Modified the following content:

-

Supported PostgreSQL 13.

+

Modified the following content:

+

2022-02-21

+

2022-12-07

Modified the following content:

- +

Modified the following content:

+
  • Supported SQL Server 2019 EE and 2019 SE.
  • Supported PostgreSQL 14.

2022-01-28

+

2022-10-30

Modified the following content:

- +

Modified the following content:

+
  • Modified the description of the tag value in Editing a Tag.
  • Modified the description of the Administrator Password.

2021-08-13

+

2022-07-22

Modified the following content:

- +

Modified the following content:

+

Supported Table Name settings during MySQL 8.0 instance creation in Step 1: Create a DB Instance.

2021-05-25

+

2022-03-22

Modified the following content:

- +

Modified the following content:

+

Supported PostgreSQL 13.

2021-03-29

+

2022-02-21

Modified the following content:

- +

Modified the following content:

+

2021-02-01

+

2022-01-28

Modified the following content:

-

Supported PostgreSQL 12.

+

Modified the following content:

+

2020-10-15

+

2021-08-13

Modified the following content:

-
  • Supported PostgreSQL Enhanced Edition.
  • Supported Microsoft SQL Server 2017 EE.
  • Supported Microsoft SQL Server 2017 SE.
  • Supported creating read replicas for Microsoft SQL Server 2017 EE DB instances.
  • Added support for MySQL minor version upgrades in section Upgrading a Minor Version.
  • Supported primary/standby switchover or failover logs for RDS MySQL DB instances.
  • Changed "Parameter Group" to "Parameter Template".
+

Modified the following content:

+

2020-04-17

+

2021-05-25

Modified the following content:

-

Supported MySQL 8.0.

+

Modified the following content:

+

2019-11-30

+

2021-03-29

Added an FAQ Does RDS for PostgreSQL Support the test_decoding Plugin?

+

Modified the following content:

+

2019-10-30

+

2021-02-01

Modified the following content:

- +

Modified the following content:

+

Supported PostgreSQL 12.

2019-09-27

+

2020-10-15

Accepted for RM-466, RM-525, RM-581, RM-583, RM-604, RM-650, RM-680, and RM-681.

+

Modified the following content:

+
  • Supported Microsoft SQL Server 2017 EE.
  • Supported Microsoft SQL Server 2017 SE.
  • Supported creating read replicas for Microsoft SQL Server 2017 EE DB instances.
  • Added support for MySQL minor version upgrades in section Upgrading a Minor Version.
  • Supported primary/standby switchover or failover logs for RDS MySQL DB instances.
  • Changed "Parameter Group" to "Parameter Template".

2019-09-17

+

2020-04-17

Modified the following content:

- +

Modified the following content:

+

Supported MySQL 8.0.

2019-09-12

+

2019-11-30

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, Creating or Deleting a Plugin, 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?

+

Added an FAQ Does RDS for PostgreSQL Support the test_decoding Plugin?

2019-08-15

+

2019-10-30

Modified the following content:

-
  • Added the NOTE error log level for MySQL DB instances in section Viewing Error Logs.
  • Changed "Character Set" to "Server Collation" and modified its description for Microsoft SQL Server DB instances.
+

Modified the following content:

+

2019-06-30

+

2019-09-27

Modified the following content:

-
  • Supported batch creation of DB instances.
  • Supported exporting DB instance lists.
  • Supported the task center.
  • Supported creating DB instances with the same specifications as the selected DB instance.
  • Supported selecting floating IP addresses during DB instance creation.
  • Supported restoration to existing DB instances.
  • Added the error log level WARNING for MySQL DB instances in section Viewing Error Logs.
  • Supported 16 vCPUs | 64 GB, 16 vCPUs | 128 GB, and 32 vCPUs | 256 GB for MySQL DB instances in section DB Instance Classes.
  • Supported modifying floating IP addresses of existing DB instances for MySQL and PostgreSQL.
  • Supported 16 vCPUs | 32 GB and 16 vCPUs | 64 GB for PostgreSQL DB instances in section DB Instance Classes.
  • Supported transparent data encryption for Microsoft SQL Server DB instances in Configuring the TDE Function.
  • Supported slow query logs for Microsoft SQL Server DB instances in Viewing and Downloading Slow Query Logs.
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, deleting DB instances, and task center.
+

Accepted for RM-466, RM-525, RM-581, RM-583, RM-604, RM-650, RM-680, and RM-681.

2019-04-03

+

2019-09-17

Modified the following content:

-
  • Supported restoration to original DB instances for Microsoft SQL Server DB instances.
  • Supported database-level restoration for Microsoft SQL Server DB instances.
+

Modified the following content:

+

2019-03-28

+

2019-09-12

Accepted in OTC-4.0.

+

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, Creating or Deleting a Plugin, 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-02-28

+

2019-08-15

Modified the following content:

-
  • Modified the description in section Exporting a Parameter Template to the following: An exported parameter group has initially a blank change history.
  • Modified the description in the scenario in section Viewing Parameter Change History to the following: An exported or custom parameter group has initially a blank change history.
+

Modified the following content:

+
  • Added the NOTE error log level for MySQL DB instances in section Viewing Error Logs.
  • Changed "Character Set" to "Server Collation" and modified its description for Microsoft SQL Server DB instances.

2019-02-25

+

2019-06-30

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.
+

Modified the following content:

+
  • Supported batch creation of DB instances.
  • Supported exporting DB instance lists.
  • Supported the task center.
  • Supported creating DB instances with the same specifications as the selected DB instance.
  • Supported selecting floating IP addresses during DB instance creation.
  • Supported restoration to existing DB instances.
  • Added the error log level WARNING for MySQL DB instances in section Viewing Error Logs.
  • Supported 16 vCPUs | 64 GB, 16 vCPUs | 128 GB, and 32 vCPUs | 256 GB for MySQL DB instances in section DB Instance Classes.
  • Supported modifying floating IP addresses of existing DB instances for MySQL and PostgreSQL.
  • Supported 16 vCPUs | 32 GB and 16 vCPUs | 64 GB for PostgreSQL DB instances in section DB Instance Classes.
  • Supported transparent data encryption for Microsoft SQL Server DB instances in Configuring the TDE Function.
  • Supported slow query logs for Microsoft SQL Server DB instances in Viewing and Downloading Slow Query Logs.
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, deleting DB instances, and task center.

2019-02-15

+

2019-04-03

Modified the following content:

- +

Modified the following content:

+
  • Supported restoration to original DB instances for Microsoft SQL Server DB instances.
  • Supported database-level restoration for Microsoft SQL Server DB instances.

2019-01-31

+

2019-03-28

Modified the following content:

-
  • Added PostgreSQL 10 to the PostgreSQL engine in Table 1 in section Function Comparison.
  • Changed the maximum storage space to 4 TB in Function Comparison in section Function Comparison.
  • Supported adding tags during the DB instance creation.
  • Supported selecting parameter groups during the DB instance creation.
  • Optimized parameter group management: when you change certain parameter values in parameter groups in batches and save the changes, the changes will take effect only after you apply the parameter groups to DB instances.
+

Accepted in OTC-4.0.

2018-12-29

+

2019-02-28

Modified the following content:

-
  • Supported PostgreSQL 10.
  • Supported Microsoft SQL Server 2016 EE.
  • Supported Microsoft SQL Server 2016 SE.
  • Supported selecting time zones during the DB instance creation.
  • Supported changing the DB instance type from single to primary/standby.
  • Supported DB instance storage space up to 4,000 GB.
+

Modified the following content:

+
  • Modified the description in section Exporting a Parameter Template to the following: An exported parameter group has initially a blank change history.
  • Modified the description in the scenario in section Viewing Parameter Change History to the following: An exported or custom parameter group has initially a blank change history.

2018-10-08

+

2019-02-25

Accepted in OTC-3.2.

+

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.

2018-09-26

+

2019-02-15

Modified the following content:

- +

Modified the following content:

+

2018-09-12

+

2019-01-31

Modified the following content:

-
  • Deleted the release numbers and retained the release dates only in accordance with the unified style.
  • Added the hyperlink in 2 for ease of use.
  • Added the following description in section Creating a Parameter Template: RDS does not share parameter group quotas with DDS. All RDS DB engines share the parameter group quota.
  • Deleted [username@host] from the command in section Tablespace Management.
+

Modified the following content:

+
  • Added PostgreSQL 10 to the PostgreSQL engine in Table 1 in section Function Comparison.
  • Changed the maximum storage space to 4 TB in Function Comparison in section Function Comparison.
  • Supported adding tags during the DB instance creation.
  • Supported selecting parameter groups during the DB instance creation.
  • Optimized parameter group management: when you change certain parameter values in parameter groups in batches and save the changes, the changes will take effect only after you apply the parameter groups to DB instances.

2018-08-31

+

2018-12-29

Modified the following content:

- +

Modified the following content:

+
  • Supported PostgreSQL 10.
  • Supported Microsoft SQL Server 2016 EE.
  • Supported Microsoft SQL Server 2016 SE.
  • Supported selecting time zones during the DB instance creation.
  • Supported changing the DB instance type from single to primary/standby.
  • Supported DB instance storage space up to 4,000 GB.

2018-08-17

+

2018-10-08

Modified the following content:

-
  • Changed PostGIS to postgis.
  • Added the following PostgreSQL plugins: auto_explain, pg_pathman, pg_stat_statements, and pg_hint_plan.
  • Changed "backups" to "automated backups".
  • Changed the quota of custom parameter groups to 1000. The quota is not shared by DDS.
  • Deleted [username@host] from the command.
  • Set the plugin name "postgis" in bold.
  • Adjusted the positions of constraints for earthdistance, timescaledb, and cube plugins.
+

Accepted in OTC-3.2.

2018-08-03

+

2018-09-26

Modified the following content:

-
  • Enhanced password verification when a DB instance is created or the password of a database account is reset.
  • Added PostgreSQL plugins.
  • Optimized the disabling mechanism of the automated backup policy.
+

Modified the following content:

+

2018-07-03

+

2018-09-12

Accepted in OTC-3.1.

+

Modified the following content:

+
  • Deleted the release numbers and retained the release dates only in accordance with the unified style.
  • Added the hyperlink in 2 for ease of use.
  • Added the following description in section Creating a Parameter Template: RDS does not share parameter group quotas with DDS. All RDS DB engines share the parameter group quota.
  • Deleted [username@host] from the command in section Tablespace Management.

2018-06-22

+

2018-08-31

Modified the following content:

-

Added the impact of deleting keys after disk encryption is enabled.

+

Modified the following content:

+

2018-06-14

+

2018-08-17

Modified the following content:

-
  • Added the change history of selecting a time zone when creating a Microsoft SQL Server DB instance.
  • Added the reference path for creating a key.
  • Added the maximum throughput of each storage type.
  • Optimized descriptions of subnets and security groups.
  • Optimized the public accessibility scenario.
  • Changed descriptions after successful DB instance creation from an ordered list to a nonsequential list.
  • Optimized the procedures of downloading backup files.
  • Added the description of the replication delay parameter.
  • Added an FAQ How Can I Obtain Microsoft SQL Server Error Logs Using Commands?
+

Modified the following content:

+
  • Changed PostGIS to postgis.
  • Added the following PostgreSQL plugins: auto_explain, pg_pathman, pg_stat_statements, and pg_hint_plan.
  • Changed "backups" to "automated backups".
  • Changed the quota of custom parameter groups to 1000. The quota is not shared by DDS.
  • Deleted [username@host] from the command.
  • Set the plugin name "postgis" in bold.
  • Adjusted the positions of constraints for earthdistance, timescaledb, and cube plugins.

2018-06-08

+

2018-08-03

Modified the following content:

-
  • Provided an option for enabling or disabling automated backups.
  • Optimized the procedures of downloading backup files from OBS.
  • Added the description of administrator password security.
+

Modified the following content:

+
  • Enhanced password verification when a DB instance is created or the password of a database account is reset.
  • Added PostgreSQL plugins.
  • Optimized the disabling mechanism of the automated backup policy.

2018-05-22

+

2018-07-03

Modified the following content:

-

Optimized the description of disk encryption.

+

Accepted in OTC-3.1.

2018-05-17

+

2018-06-22

Modified the following content:

-
  • Combined the content of "Access RDS" in restrictions.
  • Added the description of "Reboot an RDS DB instance" in restrictions.
  • Optimized the description of disk encryption.
  • Modified the DB instance specifications supported by Microsoft SQL Server.
+

Modified the following content:

+

Added the impact of deleting keys after disk encryption is enabled.

2018-05-03

+

2018-06-14

Modified the following content:

-
  • Supported disk encryption.
  • Supported Microsoft SQL Server instance with high specifications.
  • Supported multi-AZ deployment of Microsoft SQL Server HA DB instances.
  • Added information about product introduction.
  • Added the "Getting Started" sections for each DB engine.
  • Changed the minimum storage space of a disk to 40 GB when a DB instance is created.
  • Supported instance name modification when a DB instance is created.
  • Supported time zone selections when creating a Microsoft SQL Server DB instance.
+

Modified the following content:

+
  • Added the change history of selecting a time zone when creating a Microsoft SQL Server DB instance.
  • Added the reference path for creating a key.
  • Added the maximum throughput of each storage type.
  • Optimized descriptions of subnets and security groups.
  • Optimized the public accessibility scenario.
  • Changed descriptions after successful DB instance creation from an ordered list to a nonsequential list.
  • Optimized the procedures of downloading backup files.
  • Added the description of the replication delay parameter.
  • Added an FAQ How Can I Obtain Microsoft SQL Server Error Logs Using Commands?

2018-03-31

+

2018-06-08

Accepted in OTC-3.0.

+

Modified the following content:

+
  • Provided an option for enabling or disabling automated backups.
  • Optimized the procedures of downloading backup files from OBS.
  • Added the description of administrator password security.

2018-03-20

+

2018-05-22

  • Adjust HA Type sequence to show primary/standby first.
  • Add description of primary/standby at Scenarios and Step 1 of section 3.10.
+

Modified the following content:

+

Optimized the description of disk encryption.

2018-03-14

+

2018-05-17

Optimized the automated backup policy description.

+

Modified the following content:

+
  • Combined the content of "Access RDS" in restrictions.
  • Added the description of "Reboot an RDS DB instance" in restrictions.
  • Optimized the description of disk encryption.
  • Modified the DB instance specifications supported by Microsoft SQL Server.

2018-03-05

+

2018-05-03

Optimized the commands for exporting and importing data.

+

Modified the following content:

+
  • Supported disk encryption.
  • Supported Microsoft SQL Server instance with high specifications.
  • Supported multi-AZ deployment of Microsoft SQL Server HA DB instances.
  • Added information about product introduction.
  • Added the "Getting Started" sections for each DB engine.
  • Changed the minimum storage space of a disk to 40 GB when a DB instance is created.
  • Supported instance name modification when a DB instance is created.
  • Supported time zone selections when creating a Microsoft SQL Server DB instance.

2018-02-23

+

2018-03-31

  • Changed the MySQL version to 5.7.20.
  • Deleted the frozen status and description.
  • Updated the commands.
  • Added the description: If the retention period is 0 days (indicating that the automated backup is disabled) and you set it to one or more days, the backup policy is enabled and a full automated backup is triggered instantly.
  • Added a description.
  • Supported tag management.
+

Accepted in OTC-3.0.

2018-02-09

+

2018-03-20

Modified the following content:

-
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, and deleting DB instances.
  • Supported DB instance name modifications.
+
  • Adjust HA Type sequence to show primary/standby first.
  • Add description of primary/standby at Scenarios and Step 1 of section 3.10.

2018-01-31

+

2018-03-14

Modified the following content:

-
  • Supported tag management.
  • Supported PostgreSQL plugins.
+

Optimized the automated backup policy description.

2017-10-31

+

2018-03-05

Modified the following content:

-
  • Supported MySQL 5.7.20.
  • Supported PostgreSQL 9.6.5.
+

Optimized the commands for exporting and importing data.

2017-10-13

+

2018-02-23

Modified the following content:

-
  • Added the suffix description for the DB instance name.
  • Added the description of the EIPs displayed in the dialog box when enabling public accessibility.
+
  • Changed the MySQL version to 5.7.20.
  • Deleted the frozen status and description.
  • Updated the commands.
  • Added the description: If the retention period is 0 days (indicating that the automated backup is disabled) and you set it to one or more days, the backup policy is enabled and a full automated backup is triggered instantly.
  • Added a description.
  • Supported tag management.

2017-09-27

+

2018-02-09

Modified the following content:

-
  • Modified the Microsoft SQL Server log loading method.
  • Added a description to the EIP binding and unbinding: A reboot is required after enabling public accessibility for Microsoft SQL Server DB instances.
+

Modified the following content:

+
  • Based on the console modifications, updated the following procedure descriptions: creating DB instances, connecting DB instances, creating read replicas, scaling up storage space, changing instance classes, creating backups, restoring backups, changing database ports, changing administrator passwords, rebooting DB instances, and deleting DB instances.
  • Supported DB instance name modifications.

2017-08-30

+

2018-01-31

Modified the following content:

- +

Modified the following content:

+
  • Supported tag management.
  • Supported PostgreSQL plugins.

2017-07-30

+

2017-10-31

Modified the following content:

- +

Modified the following content:

+
  • Supported MySQL 5.7.20.
  • Supported PostgreSQL 9.6.5.

2017-06-30

+

2017-10-13

Modified the following content:

-

Supported changing the descriptions of custom parameter groups.

+

Modified the following content:

+
  • Added the suffix description for the DB instance name.
  • Added the description of the EIPs displayed in the dialog box when enabling public accessibility.

2017-06-14

+

2017-09-27

Modified the following content:

- +

Modified the following content:

+
  • Modified the Microsoft SQL Server log loading method.
  • Added a description to the EIP binding and unbinding: A reboot is required after enabling public accessibility for Microsoft SQL Server DB instances.

2017-05-06

+

2017-08-30

Modified the following content:

-

Supported MySQL 5.7.17.

+

Modified the following content:

+

2017-04-28

+

2017-07-30

Modified the following content:

-
  • Supported Microsoft SQL Server 2014 SP2 SE.
  • Supported parameter groups.
+

Modified the following content:

+

2017-03-31

+

2017-06-30

Modified the following content:

-
  • Supported resetting the administrator password.
  • Updated the SSL certificate.
+

Modified the following content:

+

Supported changing the descriptions of custom parameter groups.

2017-02-28

+

2017-06-14

Modified the following content:

-
  • Supported MySQL 5.6.35.
  • Supported changing the database port.
+

Modified the following content:

+

2017-02-08

+

2017-05-06

Modified the following content:

-
  • Adjusted the document structure.
  • Supported PostgreSQL 9.5.
  • Added section Glossary.
+

Modified the following content:

+

Supported MySQL 5.7.17.

2016-11-24

+

2017-04-28

Modified the following content:

- +

Modified the following content:

+
  • Supported Microsoft SQL Server 2014 SP2 SE.
  • Supported parameter groups.

2016-10-29

+

2017-03-31

Modified the following content:

-
  • Modified description of snapshot management.
  • Supported MySQL 5.6.34.
+

Modified the following content:

+
  • Supported resetting the administrator password.
  • Updated the SSL certificate.

2016-10-19

+

2017-02-28

Modified the following content:

-
  • Supported MySQL 5.6.33.
  • Supported scaling up DB clusters.
  • Supported creating and managing snapshots.
  • Supported changing the DB instance CPU and memory.
  • Supported restoring a DB instance to a specified point in time.
+

Modified the following content:

+
  • Supported MySQL 5.6.35.
  • Supported changing the database port.

2016-07-15

+

2017-02-08

This issue is the first official release.

+

Modified the following content:

+
  • Adjusted the document structure.
  • Supported PostgreSQL 9.5.
  • Added section Glossary.
+

2016-11-24

+

Modified the following content:

+ +

2016-10-29

+

Modified the following content:

+
  • Modified description of snapshot management.
  • Supported MySQL 5.6.34.
+

2016-10-19

+

Modified the following content:

+
  • Supported MySQL 5.6.33.
  • Supported scaling up DB clusters.
  • Supported creating and managing snapshots.
  • Supported changing the DB instance CPU and memory.
  • Supported restoring a DB instance to a specified point in time.
+

2016-07-15

+

This issue is the first official release.

PostgreSQL

 +
  • 14
  • 13
  • 12
  • 11
  • 10
  • 9.6
  • 9.5
 +
  • 14
  • 13
  • 12
  • 11
  • 10
  • 9.6
  • 9.5

Not supported

Microsoft SQL Server

  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
+
  • 2019 SE
  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
+
  • 2019 SE
  • 2017 SE
  • 2016 EE
  • 2016 SE
  • 2014 SE
  • 2017 EE
+
  • 2019 EE
  • 2017 EE
Table 1 Related operations and references

Operation

diff --git a/docs/rds/umn/en-us_topic_add_read_replica.html b/docs/rds/umn/en-us_topic_add_read_replica.html index a97b3e85..46c45b66 100644 --- a/docs/rds/umn/en-us_topic_add_read_replica.html +++ b/docs/rds/umn/en-us_topic_add_read_replica.html @@ -4,7 +4,7 @@

Scenarios

Read replicas are used to enhance the read capabilities and reduce the load on primary DB instances.

After DB instances are created, you can create read replicas for them.

-

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 Create Read Replica in the Operation column.

    Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

    +

    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 Create Read Replica in the Operation column.

      Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

    5. On the displayed page, configure information about the DB instance and click Next.

      diff --git a/docs/rds/umn/en-us_topic_apply_for_rds.html b/docs/rds/umn/en-us_topic_apply_for_rds.html index 4d1676cb..2fd6ab9b 100644 --- a/docs/rds/umn/en-us_topic_apply_for_rds.html +++ b/docs/rds/umn/en-us_topic_apply_for_rds.html @@ -2,7 +2,7 @@

      Overview

      Process

      Figure 1 illustrates the process of connecting to a MySQL DB instance through a private network.

      -
      Figure 1 Connecting to a DB instance through a private network
      +
      Figure 1 Connecting to a DB instance through a private network
      diff --git a/docs/rds/umn/en-us_topic_connect_instance.html b/docs/rds/umn/en-us_topic_connect_instance.html index a9b77c90..72a8c616 100644 --- a/docs/rds/umn/en-us_topic_connect_instance.html +++ b/docs/rds/umn/en-us_topic_connect_instance.html @@ -13,8 +13,8 @@
      -

      Using MySQL-Front to Connect to a DB Instance

      1. Start MySQL-Front.
      2. In the displayed dialog box, click New.

        Figure 1 Connection management
        -

      3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

        Figure 2 Adding an account
        +

        Using MySQL-Front to Connect to a DB Instance

        1. Start MySQL-Front.
        2. In the displayed dialog box, click New.

          Figure 1 Connection management
          +

        3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

          Figure 2 Adding an account
      Table 1 Basic information

      Parameter
      @@ -50,13 +50,13 @@
      Table 1 Parameter description

      Parameter
      -

    6. In the displayed window, select the connection that you have created in Figure 3 and click Open.

      If the connection information is correct, the DB instance is successfully connected.
      Figure 3 Opening a session
      +

    7. In the displayed window, select the connection that you have created in Figure 3 and click Open.

      If the connection information is correct, the DB instance is successfully connected.
      Figure 3 Opening a session

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

    -

    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 DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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?

          • 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_parameter_group.html b/docs/rds/umn/en-us_topic_parameter_group.html index f7328dd8..ad1e2a5f 100644 --- a/docs/rds/umn/en-us_topic_parameter_group.html +++ b/docs/rds/umn/en-us_topic_parameter_group.html @@ -8,11 +8,11 @@

          If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

          When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

          The following are the key points you should know when using parameters in a parameter template:

          -
          • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
          • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
          +
          • The changes to parameter values in a custom parameter template take effect only after you apply the template to DB instances. For details, see Applying a Parameter Template.
          • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.

          RDS does not share parameter template quotas with DDS.

          You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

          -

          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 Parameter Template Management page, click Create Parameter Template.
          5. In the displayed dialog box, configure required information and click OK.

            • Select a DB engine for the parameter template.
            • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
            • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
            +

            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 Parameter Template Management page, click Create Parameter Template.
            5. In the displayed dialog box, configure required information and click OK.

              • Select a DB engine for the parameter template.
              • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
              • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

          diff --git a/docs/rds/umn/en-us_topic_scale_cluster.html b/docs/rds/umn/en-us_topic_scale_cluster.html index aa01bb4a..c08ec94d 100644 --- a/docs/rds/umn/en-us_topic_scale_cluster.html +++ b/docs/rds/umn/en-us_topic_scale_cluster.html @@ -9,7 +9,7 @@

          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:

            +

            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 Basic Information page. In the Storage Space area, click Scale.

            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.
              @@ -18,7 +18,7 @@

            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:

              +
              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 Basic Information page. In the Storage Space area, click Scale.

              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.
                diff --git a/docs/rds/umn/en-us_topic_scale_rds.html b/docs/rds/umn/en-us_topic_scale_rds.html index 4815c3c3..d38ade3d 100644 --- a/docs/rds/umn/en-us_topic_scale_rds.html +++ b/docs/rds/umn/en-us_topic_scale_rds.html @@ -5,7 +5,7 @@

            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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

              +

              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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

              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 Basic Information 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 58b50398..28d5b12b 100644 --- a/docs/rds/umn/en-us_topic_sqlserver_reset_password.html +++ b/docs/rds/umn/en-us_topic_sqlserver_reset_password.html @@ -6,14 +6,14 @@
                • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
                • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
                • To protect against brute force hacking attempts and ensure system security, change your password periodically, such as every three or six months.
                -

                Method 1

                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 > Reset Password in the Operation column.
                5. Enter and confirm a new password.

                  Keep this password secure. The system cannot retrieve it.

                  +

                  Method 1

                  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 > Reset Password in the Operation column.
                  5. 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.

                  -

                  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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field. 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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field. 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/public_sys-resources/ExpandCollapse.js b/docs/rds/umn/public_sys-resources/ExpandCollapse.js index 116ddaab..959be0c4 100644 --- a/docs/rds/umn/public_sys-resources/ExpandCollapse.js +++ b/docs/rds/umn/public_sys-resources/ExpandCollapse.js @@ -1 +1 @@ -var expandClassName="dropdownexpand";var collapseClassName="dropdowncollapse";var collapseTableClassName="dropdowncollapsetable";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file +var collapseTableClassName="dropdowncollapsetable";var collapseClassName="dropdowncollapse";var expandClassName="dropdownexpand";function ExpandorCollapseNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseClassName}else{a.className=expandClassName}}function ExpandorCollapseTableNode(a){a=a.parentNode;if(a.className==expandClassName){a.className=collapseTableClassName}else{a.className=expandClassName}}function ExpandorCollapseAllNodes(g,h,c){var a=g.getAttribute("title");var b=g.parentNode;if(a=="collapse"){g.setAttribute("title","expand");g.className="dropdownAllButtonexpand";g.innerHTML=h}else{g.setAttribute("title","collapse");g.className="dropdownAllButtoncollapse";g.innerHTML=c}var f=b.getElementsByTagName("*");for(var d=0;d-1){ExpandForHref(a.substring(a.lastIndexOf("#")+1))}}catch(c){}}; \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/commonltr.css b/docs/rds/umn/public_sys-resources/commonltr.css index c5480b0a..17f8423f 100644 --- a/docs/rds/umn/public_sys-resources/commonltr.css +++ b/docs/rds/umn/public_sys-resources/commonltr.css @@ -1 +1 @@ -body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file +body{font-size:10pt;font-family:Arial;margin:1.5em;border-top:2pt;padding-top:1em;padding-bottom:2em}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:.6em;margin-bottom:.6em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.figcap{font-size:10pt}img{margin-top:.3em}.figdesc{font-style:normal}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.fignone{font-size:10pt;margin-top:8pt;margin-bottom:8pt}.familylinks{margin-top:1.5em;margin-bottom:1em}.ullinks{list-style-type:none}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-top:.6em;margin-bottom:.6em}.reltasks{margin-top:.6em;margin-bottom:.6em}.relref{margin-top:.6em;margin-bottom:.6em}.relinfo{margin-top:.6em;margin-bottom:.6em}.breadcrumb{font-size:smaller;margin-bottom:.6em}.prereq{margin-left:20px}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.topictitle1{margin-top:0;margin-bottom:1em;font-size:14pt;color:#007af4}.topictitle2{margin-top:1pc;margin-bottom:.45em;font-size:1.17em;color:#007af4}.topictitle3{margin-top:1pc;margin-bottom:.17em;font-size:1.17em;font-weight:bold;color:#007af4}.topictitle4{margin-top:.83em;font-size:1.17em;font-weight:bold}.topictitle5{font-size:1.17em;font-weight:bold}.topictitle6{font-size:1.17em;font-style:italic}.sectiontitle{margin-top:1em;margin-bottom:1em;color:black;font-size:10.5pt;font-weight:bold;color:#007af4;overflow:auto}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}.sectiontitle2contents:link{color:#007af4}.sectiontitle2contents:visited{color:#800080}.note{margin-top:1em;margin-bottom:1em;background-color:#ffc}.notetitle{font-weight:bold}.notelisttitle{font-weight:bold}.tip{margin-top:1em;margin-bottom:1em;background-color:#ffc}.tiptitle{font-weight:bold}.fastpath{margin-top:1em;margin-bottom:1em;background-color:#ffc}.fastpathtitle{font-weight:bold}.important{margin-top:1em;margin-bottom:1em;background-color:#ffc}.importanttitle{font-weight:bold}.remember{margin-top:1em;margin-bottom:1em;background-color:#ffc}.remembertitle{font-weight:bold}.restriction{margin-top:1em;margin-bottom:1em;background-color:#ffc}.restrictiontitle{font-weight:bold}.attention{margin-top:1em;margin-bottom:1em;background-color:#ffc}.attentiontitle{font-weight:bold}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;background-color:#ffc}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;background-color:#ffc}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;background-color:#ffc}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;background-color:#ffc}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em;word-break:break-all}ol{margin-top:1em;margin-bottom:1em;margin-left:2.4em;padding-left:0}ul{margin-top:1em;margin-bottom:1em;margin-left:2.0em;padding-left:0}ol ul{list-style:disc}ul ul{list-style:square}ol ul ul{list-style:square}ol ul{list-style-type:disc}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}.firstcol{font-weight:bold}th{background-color:#cfcfcf}table{margin-top:8pt;margin-bottom:12pt;width:100%}table caption{margin-top:8pt;text-align:left}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:.3em;margin-bottom:.3em}.substepexpand{margin-top:.3em;margin-bottom:.3em}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;background-color:#ddd;white-space:pre}.hrcopyright{color:#3f4e5d;margin-top:18pt}.hwcopyright{text-align:center}.comment{margin:2px 2px 2px 2px;font-family:Arial;font-size:10pt;background-color:#bfb;color:#000}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowncontext{display:none}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdowncollapsetable{border:0}.dropdowncollapsetable .dropdowncontext{display:none}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}pre{font-size:10pt;font-weight:normal;margin-left:9;margin-top:2;margin-bottom:2}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0} \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/commonltr_print.css b/docs/rds/umn/public_sys-resources/commonltr_print.css index a5982314..e1eb38aa 100644 --- a/docs/rds/umn/public_sys-resources/commonltr_print.css +++ b/docs/rds/umn/public_sys-resources/commonltr_print.css @@ -1 +1 @@ -body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file +body{font-size:12.0pt;margin:1.5em;margin-left:1.6cm}.msgph{font-family:Courier New}.rowlinecopyright{color:red;margin-top:10pt}.unresolved{background-color:skyblue}.noTemplate{background-color:yellow}.base{background-color:#fff}.nested0{margin-top:1em}.p{margin-top:1em}p{margin-top:.5em;margin-bottom:.5em}.note p{margin-top:.5em;margin-bottom:.5em}.tip p{margin-top:.5em;margin-bottom:.5em}.danger p{margin-top:.5em;margin-bottom:.5em}.warning p{margin-top:.5em;margin-bottom:.5em}.notice p{margin-top:.5em;margin-bottom:.5em}.caution p{margin-top:.5em;margin-bottom:.5em}.attention p{margin-top:.5em;margin-bottom:.5em}table p{margin-top:.2em;margin-bottom:.2em}table .p{margin-top:.4em;margin-bottom:.2em}.covertable{border:0;width:100% cellpadding:8pt;cellspacing:8pt}.cover_productname{font-size:15.0pt;font-family:"Arial"}.cover_manualtitle{font-size:24.0pt;font-weight:bold;font-family:"Arial"}.cover_manualsubtitle{font-size:18.0pt;font-weight:bold;font-family:"Arial"}.cover_heading{font-size:12.0pt;font-weight:bold;font-family:"Arial"}.cover_text{font-size:9.0pt;font-family:"Arial"}.tocheading,.heading1,.topictitle1{margin-top:40.0pt;margin-right:0;margin-bottom:20.0pt;margin-left:-1cm;text-align:left;border:0;border-bottom:solid windowtext .5pt;font-size:22.0pt;font-family:"Arial";font-weight:bold}.topictitlenumber1{font-size:72.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle2{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Arial";font-weight:bold}.topictitle3{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:16.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle4{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:14.0pt;font-family:"Book Antiqua";font-weight:bold}.topictitle5{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.blocklabel,.topictitle6{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.sectiontitle{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:-1cm;text-indent:0;font-size:13.0pt;font-family:"Arial";font-weight:bold}.tocentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Book Antiqua";font-weight:bold}.tocentry2{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry3{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry4{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tocentry5{margin-top:4.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman"}.tofentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.totentry1{margin-top:8.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;line-height:12.0pt;font-size:11.0pt;font-family:"Times New Roman";font-weight:normal}.indexheading{margin-top:15.0pt;margin-right:0;margin-bottom:4.0pt;margin-left:0;text-indent:0;font-size:13.0pt;font-family:"Book Antiqua";font-weight:bold}.indexentry1{margin-top:4pt;margin-right:0;margin-bottom:0;margin-left:0;line-height:12.0pt;font-size:12.0pt;font-family:"Times New Roman"}.indexentry2{margin-top:0;margin-right:0;margin-bottom:0;margin-left:24.0pt;line-height:12.0pt;font-size:12.0pt}.indexentry3{margin-top:0;margin-right:0;margin-bottom:0;margin-left:48pt;line-height:12.0pt;font-size:12.0pt}.figurenumber{font-weight:bold}.tablenumber{font-weight:bold}.familylinks{margin-top:1.5em;margin-bottom:1em}.figcap{font-size:11.0pt}.tablecap{font-size:11.0pt}.figdesc{font-style:normal}.fignone{margin-top:8.0pt}.figborder{border-style:solid;padding-left:3px;border-width:2px;padding-right:3px;margin-top:1em;border-color:Silver}.figsides{border-left:2px solid;padding-left:3px;border-right:2px solid;padding-right:3px;margin-top:1em;border-color:Silver}.figtop{border-top:2px solid;margin-top:1em;border-color:Silver}.figbottom{border-bottom:2px solid;border-color:Silver}.figtopbot{border-top:2px solid;border-bottom:2px solid;margin-top:1em;border-color:Silver}.ullinks{margin-left:0;list-style-type:none}.ulchildlink{margin-top:1em;margin-bottom:1em}.olchildlink{margin-top:1em;margin-bottom:1em;margin-left:1em}.linklist{margin-bottom:1em}.linklistwithchild{margin-left:1.5em;margin-bottom:1em}.sublinklist{margin-left:1.5em;margin-bottom:1em}.relconcepts{margin-left:1cm;margin-top:1em;margin-bottom:1em}.reltasks{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relref{margin-left:1cm;margin-top:1em;margin-bottom:1em}.relinfo{margin-top:1em;margin-bottom:1em}.breadcrumb{font-size:smaller;margin-bottom:1em}.prereq{margin-left:0}.parentlink{margin-top:.6em;margin-bottom:.6em}.nextlink{margin-top:.6em;margin-bottom:.6em}.previouslink{margin-top:.6em;margin-bottom:.6em}.section{margin-top:1em;margin-bottom:1em}.example{margin-top:1em;margin-bottom:1em}table .note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.note{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.notetitle{font-weight:bold;font-size:11.0pt}.notelisttitle{font-weight:bold}table .tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.tip{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.tiptitle{font-weight:bold;font-size:11.0pt}table .fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.fastpath{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.fastpathtitle{font-weight:bold;font-size:11.0pt}table .important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.important{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.importanttitle{font-weight:bold;font-size:11.0pt}table .remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.remember{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.remembertitle{font-weight:bold;font-size:11.0pt}table .restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman";font-style:italic}.restriction{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;border-top:solid .5pt;border-bottom:solid .5pt}.restrictiontitle{font-weight:bold;font-size:11.0pt}table .attention{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.attention{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}.attentiontitle{font-weight:bold}table .danger{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.dangertitle{font-weight:bold}.danger{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .notice{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.noticetitle{font-weight:bold}.notice{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .warning{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}.warningtitle{font-weight:bold}.warning{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}table .caution{margin-top:1em;margin-bottom:1em;border:0;font-size:10.0pt;font-family:"Times New Roman"}table caption{margin-top:8pt;text-align:left;font-weight:bold}.tablenoborder{margin-top:8pt}.cautiontitle{font-weight:bold}.caution{margin-top:1em;margin-bottom:1em;border:0;border-top:solid .5pt;border-bottom:solid .5pt}ul.simple{list-style-type:none}li ul{margin-top:.6em}li{margin-top:.6em;margin-bottom:.6em}.note li{margin-top:.2em;margin-bottom:.2em}.tip li{margin-top:.2em;margin-bottom:.2em}.danger li{margin-top:.2em;margin-bottom:.2em}.warning li{margin-top:.2em;margin-bottom:.2em}.notice li{margin-top:.2em;margin-bottom:.2em}.caution li{margin-top:.2em;margin-bottom:.2em}.attention li{margin-top:.2em;margin-bottom:.2em}table li{margin-top:.2em;margin-bottom:.2em;word-break:break-all}.firstcol{font-weight:bold}th{background-color:#cfcfcf}.bold{font-weight:bold}.boldItalic{font-weight:bold;font-style:italic}.italic{font-style:italic}.underlined{text-decoration:underline}.var{font-style:italic}.shortcut{text-decoration:underline}.dlterm{font-weight:bold}dd{margin-top:.5em;margin-bottom:.5em}.dltermexpand{font-weight:bold;margin-top:1em}*[compact="yes"]>li{margin-top:0}*[compact="no"]>li{margin-top:.53em}.liexpand{margin-top:1em;margin-bottom:1em}.sliexpand{margin-top:1em;margin-bottom:1em}.dlexpand{margin-top:1em;margin-bottom:1em}.ddexpand{margin-top:1em;margin-bottom:1em}.stepexpand{margin-top:1em;margin-bottom:1em}.substepexpand{margin-top:1em;margin-bottom:1em}table{margin-top:8pt;margin-bottom:10.0pt;width:100%}thead{font-size:10.0pt;font-family:"Book Antiqua";font-weight:bold}tbody{font-size:11.0pt}ol{margin-top:1em;margin-bottom:1em;margin-left:1.7em;-webkit-padding-start:0}ul{margin-top:1em;margin-bottom:1em;margin-left:1.2em;-webkit-padding-start:0}ol ul{list-style:disc}ul ul{list-style:square}ol ol{list-style-type:lower-alpha}table ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}table ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ul{margin-top:.4em;margin-bottom:.4em;list-style:square}table ol ol{margin-top:.4em;margin-bottom:.4em;list-style:lower-alpha}table ol ul{margin-top:.4em;margin-bottom:.4em;list-style:disc}table ul ol{margin-top:.4em;margin-bottom:.4em;list-style:decimal}.substepthirdol{list-style-type:lower-roman}div.imageleft{text-align:left}div.imagecenter{text-align:center}div.imageright{text-align:right}div.imagejustify{text-align:justify}div.noblankline{text-align:center}div.noblankline img{margin-top:0}pre{font-size:10.0pt;border-width:2px;padding:2px;margin-top:5px;margin-bottom:5px;white-space:pre-wrap;white-space:-moz-pre-wrap;white-space:-pre-wrap;white-space:-o-pre-wrap;word-wrap:break-word}pre.screen{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}pre.codeblock{margin-top:2px;margin-bottom:2px;padding:1.5px 1.5px 0 1.5px;border:0;white-space:pre}.dropdownAllButtonexpand{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4}.dropdownAllButtoncollapse{cursor:pointer;background-repeat:no-repeat;background-position:0 4px;padding-left:15px;background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;text-decoration:underline;color:#007af4}.dropdowntitle{background-repeat:no-repeat;background-position:0 4px;padding-left:15px;cursor:pointer;text-decoration:underline;color:#007af4}.dropdownexpand .dropdowntitle{background-image:url(icon-arrowdn.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapse .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.dropdowncollapsetable .dropdowntitle{background-image:url(icon-arrowrt.gif);text-decoration:underline;color:#007af4;margin:0 0 8px 0}.prefacesectiontitle1{margin-top:10.0pt;margin-right:0;margin-bottom:8.0pt;margin-left:-1cm;text-indent:0;font-size:18.0pt;font-family:"Book Antiqua";font-weight:bold;overflow:auto}.termcolor{color:blue;cursor:pointer}#dhtmlgoodies_tooltip{background-color:#f0f0d2;border:1px solid #000;position:absolute;display:none;z-index:20000;padding:2px;font-size:.9em;-moz-border-radius:6px;font-family:"Trebuchet MS","Lucida Sans Unicode",Arial,sans-serif}#dhtmlgoodies_tooltipShadow{position:absolute;background-color:#555;display:none;z-index:10000;opacity:.7;filter:alpha(opacity=70);-khtml-opacity:.7;-moz-opacity:.7;-moz-border-radius:6px}.freeze{position:fixed;_position:absolute;_top:expression(eval(document.documentElement.scrollTop));left:10;top:0}.hrcopyright{color:#3f4e5d;margin-top:18pt;margin-left:-1cm}.hwcopyright{text-align:center;font-family:Arial;margin-left:-1cm} \ No newline at end of file diff --git a/docs/rds/umn/public_sys-resources/popup.js b/docs/rds/umn/public_sys-resources/popup.js index a550862e..bae3e929 100644 --- a/docs/rds/umn/public_sys-resources/popup.js +++ b/docs/rds/umn/public_sys-resources/popup.js @@ -1 +1 @@ -var i=0;var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipMaxWidth=500;var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_iframe=false;var timeId;var clickFlag=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var xPos;var yPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){xPos=a.pageX;yPos=a.pageY}else{if(document.body!==null&&typeof document.body!=="undefined"){xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft;yPos=a.clientY+document.body.scrollTop-document.body.clientTop}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"){return}if(i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.zIndex=100;dhtmlgoodies_iframe.style.position="absolute";document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltip.style.display="block";dhtmlgoodies_tooltipShadow.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}var c=xPos+10;dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px";dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file +var i=0;var dhtmlgoodies_tooltip="";var dhtmlgoodies_tooltipFlag=false;var dhtmlgoodies_shadowSize=3;var dhtmlgoodies_tooltipShadow="";var dhtmlgoodies_tooltipMinWidth=100;var dhtmlgoodies_tooltipMaxWidth=500;var timeId;var dhtmlgoodies_iframe=false;var tooltip_is_msie=(navigator.userAgent.indexOf("MSIE")>=0&&navigator.userAgent.indexOf("opera")==-1&&document.all)?true:false;var clickFlag=false;var yPos;var xPos;window.document.onmousemove=function(a){a=a||window.event;if(a.pageX){yPos=a.pageY;xPos=a.pageX}else{if(document.body!==null&&typeof document.body!=="undefined"){yPos=a.clientY+document.body.scrollTop-document.body.clientTop;xPos=a.clientX+document.body.scrollLeft-document.body.clientLeft}}};function showTooltip(e){if(document.body===null||typeof document.body==="undefined"||i==0){return}clickFlag=true;var f=Json.parse("jsonData."+e);var a=Math.max(document.body.clientWidth,document.documentElement.clientWidth)-20;if(!dhtmlgoodies_tooltipFlag){dhtmlgoodies_tooltipShadow=document.createElement("DIV");dhtmlgoodies_tooltipShadow.id="dhtmlgoodies_tooltipShadow";dhtmlgoodies_tooltip=document.createElement("DIV");dhtmlgoodies_tooltip.id="dhtmlgoodies_tooltip";document.body.appendChild(dhtmlgoodies_tooltip);document.body.appendChild(dhtmlgoodies_tooltipShadow);if(tooltip_is_msie){dhtmlgoodies_iframe=document.createElement("IFRAME");dhtmlgoodies_iframe.style.backgroundColor="#FFFFFF";dhtmlgoodies_iframe.frameborder="5";dhtmlgoodies_iframe.src="#";dhtmlgoodies_iframe.style.position="absolute";dhtmlgoodies_iframe.style.zIndex=100;document.body.appendChild(dhtmlgoodies_iframe)}}dhtmlgoodies_tooltipShadow.style.display="block";dhtmlgoodies_tooltip.style.display="block";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="block"}var b=Math.max(document.body.scrollTop,document.documentElement.scrollTop);if(navigator.userAgent.toLowerCase().indexOf("safari")>=0){b=0}dhtmlgoodies_tooltip.style.width=null;dhtmlgoodies_tooltip.innerHTML=f;var c=xPos+10;dhtmlgoodies_tooltip.style.left=c+"px";if(tooltip_is_msie){dhtmlgoodies_tooltip.style.top=yPos+20+b+"px"}else{dhtmlgoodies_tooltip.style.top=yPos+20+"px"}dhtmlgoodies_tooltipShadow.style.left=c+dhtmlgoodies_shadowSize+"px";if(tooltip_is_msie){dhtmlgoodies_tooltipShadow.style.top=yPos+20+b+dhtmlgoodies_shadowSize+"px"}else{dhtmlgoodies_tooltipShadow.style.top=yPos+20+dhtmlgoodies_shadowSize+"px"}if(dhtmlgoodies_tooltip.offsetWidth>dhtmlgoodies_tooltipMaxWidth){dhtmlgoodies_tooltip.style.width=dhtmlgoodies_tooltipMaxWidth+"px"}var d=dhtmlgoodies_tooltip.offsetWidth;if(da){dhtmlgoodies_tooltip.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a))+"px";dhtmlgoodies_tooltipShadow.style.left=(dhtmlgoodies_tooltipShadow.style.left.replace("px","")-((c+d)-a)+dhtmlgoodies_shadowSize)+"px"}if(tooltip_is_msie){dhtmlgoodies_iframe.style.top=dhtmlgoodies_tooltip.style.top;dhtmlgoodies_iframe.style.left=dhtmlgoodies_tooltip.style.left;dhtmlgoodies_iframe.style.height=dhtmlgoodies_tooltip.offsetHeight+"px";dhtmlgoodies_iframe.style.width=dhtmlgoodies_tooltip.offsetWidth+"px"}}function hideTooltip(){i=0;clickFlag=false;if((dhtmlgoodies_tooltip!==null&&typeof dhtmlgoodies_tooltip!=="undefined")&&+(dhtmlgoodies_tooltip.style!==null&&typeof dhtmlgoodies_tooltip.style!=="undefined")){dhtmlgoodies_tooltip.style.display="none";dhtmlgoodies_tooltipShadow.style.display="none";if(tooltip_is_msie){dhtmlgoodies_iframe.style.display="none"}}if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}function showText(a){i=1;timeId=setTimeout(function(){showTooltip(a)},500)}function showText2(a){if(!clickFlag){i=1;showTooltip(a);i=0;if(timeId!==null&&typeof timeId!=="undefined"&&timeId!=""){clearTimeout(timeId)}}}function anchorScroll(b){var d=document.getElementsByName(b);if(d!=null&&d.length>0){var c=d[0];var a=c.getBoundingClientRect().left+(document.body.scrollLeft||(document.documentElement&&document.documentElement.scrollLeft));var e=c.getBoundingClientRect().top+(document.body.scrollTop||(document.documentElement&&document.documentElement.scrollTop));window.scrollTo(a,e-30)}}; \ No newline at end of file diff --git a/docs/rds/umn/rds_01_0000.html b/docs/rds/umn/rds_01_0000.html index c9057a34..8267cc4d 100644 --- a/docs/rds/umn/rds_01_0000.html +++ b/docs/rds/umn/rds_01_0000.html @@ -16,7 +16,7 @@
                    6. Typical Applications
                      7. -
                    7. User Permissions
                      +
                    8. Permissions Management
                    9. Constraints
                      10. diff --git a/docs/rds/umn/rds_01_0012.html b/docs/rds/umn/rds_01_0012.html index cc1361ec..90c4a0de 100644 --- a/docs/rds/umn/rds_01_0012.html +++ b/docs/rds/umn/rds_01_0012.html @@ -1,7 +1,7 @@

                      Read/Write Splitting

                      -

                      RDS for MySQL, RDS for PostgreSQL, and RDS for SQL Server 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.

                      +

                      RDS for MySQL, RDS for PostgreSQL, RDS for SQL Server 2019 Enterprise Edition, and 2017 Enterprise Edition DB instances support read replicas to offload read traffic from primary DB instances.

                      For RDS for MySQL and RDS for PostgreSQL, the primary DB instances and read replicas have independent connection addresses. A maximum of five read replicas can be created for each RDS for MySQL or RDS for PostgreSQL DB instance. For details about how to create a read replica, see Creating a Read Replica (RDS for MySQL) and Creating a Read Replica (RDS for PostgreSQL).

                      To offload read pressure on the primary DB instance, you can create one or more read replicas in the same region as the primary instance. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses for the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

                      diff --git a/docs/rds/umn/rds_01_0013.html b/docs/rds/umn/rds_01_0013.html index f3775404..1d3644fa 100644 --- a/docs/rds/umn/rds_01_0013.html +++ b/docs/rds/umn/rds_01_0013.html @@ -2,7 +2,7 @@

                      Diversified Data Storage

                      RDS supports diverse storage extension through Distributed Cache Service (DCS) for Memcached, DCS for Redis, and OBS.

                      -
                      Figure 1 Diversified data storage
                      +
                      Figure 1 Diversified data storage
                      diff --git a/docs/rds/umn/rds_01_0015.html b/docs/rds/umn/rds_01_0015.html index 7d31b951..5b9b9c51 100644 --- a/docs/rds/umn/rds_01_0015.html +++ b/docs/rds/umn/rds_01_0015.html @@ -20,7 +20,7 @@
                      • Regions are defined in terms of their geographical location and network latency. Each region is completely independent, improving fault tolerance and stability. After a resource is created, its region cannot be changed.
                      • An AZ is a physical location using independent power supplies and networks. Faults in an AZ do not affect other AZs. A region can contain multiple AZs, which are physically isolated but interconnected through internal networks. This ensures the independence of AZs and provides low-cost and low-latency network connections.

                      Figure 1 shows the relationship between regions and AZs.

                      -
                      Figure 1 Regions and AZs
                      +
                      Figure 1 Regions and AZs

                      Projects

                      Projects are used to group and isolate OpenStack resources (compute, storage, and network resources). A project can be a department or a project team. Multiple projects can be created for a single account.

                      diff --git a/docs/rds/umn/rds_01_0016.html b/docs/rds/umn/rds_01_0016.html index ad5e3607..21a172e7 100644 --- a/docs/rds/umn/rds_01_0016.html +++ b/docs/rds/umn/rds_01_0016.html @@ -28,7 +28,7 @@
-

For RDS for SQL Server, only 2017 EE supports read replicas.

+

RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.

You can use RDS to create and manage DB instances running various DB engines.

For details about differences and function comparison between different instance types, see DB Instance Introduction and Function Comparison.

diff --git a/docs/rds/umn/rds_01_0017.html b/docs/rds/umn/rds_01_0017.html new file mode 100644 index 00000000..0b3ccc13 --- /dev/null +++ b/docs/rds/umn/rds_01_0017.html @@ -0,0 +1,715 @@ + + +

Permissions Management

+

If you need to assign different permissions to employees in your enterprise to access your RDS resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, securing access to your cloud resources.

+

With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use RDS resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using RDS resources.

+

If your account does not need individual IAM users for permissions management, you may skip over this chapter.

+

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.

+

RDS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

+

RDS is a project-level service deployed and accessed in specific physical regions. To assign RDS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing RDS, users need to switch to a region where they have been authorized to use RDS.

+
You can grant users permissions by using roles and policies.
  • Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
+
  • Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control.
+
+

Table 1 lists all the system-defined roles and policies supported by RDS.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 1 System policy summary

Policy Name/System Role

+

Description

+

Category

+

Dependencies

+

RDS FullAccess

+

Full permissions for Relational Database Service

+

System-defined policy

+

N/A

+

RDS ReadOnlyAccess

+

Read-only permissions for Relational Database Service

+

System-defined policy

+

N/A

+

RDS ManageAccess

+

Database administrator permissions for all operations except deleting RDS resources

+

System-defined policy

+

N/A

+

RDS Administrator

+

Administrator permissions for RDS

+

System-defined role

+

The Tenant Guest and Server Administrator roles need to be assigned in the same project.

+
+
+

Table 2 lists the common operations supported by each system policy of RDS. Please choose proper system policies according to this table.

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + +
Table 2 Common operations supported by the RDS system policies

Operation

+

RDS FullAccess

+

RDS ReadOnlyAccess

+

RDS ManageAccess

+

RDS Administrator

+

Creating an RDS DB instance

+

√

+

x

+

√

+

√

+

Deleting an RDS DB instance

+

√

+

x

+

x

+

√

+

Querying an RDS DB instance list

+

√

+

√

+

√

+

√

+
+
+ +
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Table 3 Common operations and supported actions

Operation

+

Actions

+

Remarks

+

Creating a DB instance

+

rds:instance:create

+

rds:param:list

+

To select a VPC, subnet, and security group, configure the following actions:

+

vpc:vpcs:list

+

vpc:vpcs:get

+

vpc:subnets:get

+

vpc:securityGroups:get

+

To create an encrypted instance, configure the KMS Administrator permission for the project.

+

Changing DB instance specifications

+

rds:instance:modifySpec

+

N/A

+

Scaling up storage space

+

rds:instance:extendSpace

+

N/A

+

Changing a DB instance type from single to primary/standby

+

rds:instance:singleToHa

+

If the original single DB instance is encrypted, you need to configure the KMS Administrator permission in the project.

+

Rebooting a DB instance

+

rds:instance:restart

+

N/A

+

Deleting a DB instance

+

rds:instance:delete

+

N/A

+

Querying a DB instance list

+

rds:instance:list

+

N/A

+

Querying DB instance details

+

rds:instance:list

+

If the VPC, subnet, and security group are displayed in the DB instance list, you need to configure vpc:*:get and vpc:*:list.

+

Changing a DB instance password

+

rds:password:update

+

N/A

+

Changing a database port

+

rds:instance:modifyPort

+

N/A

+

Changing a floating IP address

+

rds:instance:modifyIp

+

To query the list of unused IP addresses, configure the following actions:

+

vpc:subnets:get

+

vpc:ports:get

+

Changing a DB instance name

+

rds:instance:modify

+

N/A

+

Changing a maintenance window

+

rds:instance:modify

+

N/A

+

Performing a manual switchover

+

rds:instance:switchover

+

N/A

+

Changing the replication mode

+

rds:instance:modifySynchronizeModel

+

N/A

+

Changing the failover priority

+

rds:instance:modifyStrategy

+

N/A

+

Changing a security group

+

rds:instance:modifySecurityGroup

+

N/A

+

Binding or unbinding an EIP

+

rds:instance:modifyPublicAccess

+

To query public IP addresses, configure the following actions:

+

vpc:publicIps:get

+

vpc:publicIps:list

+

Modifying the recycling policy

+

rds:instance:setRecycleBin

+

N/A

+

Querying the recycling policy

+

rds:instance:list

+

N/A

+

Enabling or disabling SSL

+

rds:instance:modifySSL

+

N/A

+

Enabling or disabling event scheduler

+

rds:instance:modifyEvent

+

N/A

+

Configuring read/write splitting

+

rds:instance:modifyProxy

+

N/A

+

Applying for a private domain name

+

rds:instance:createDns

+

N/A

+

Migrating a standby DB instance to another AZ

+

rds:instance:create

+

Standby DB instance migration involves operations on the IP address in the subnet. For encrypted DB instances, you need to configure the KMS Administrator permission in the project.

+

Restoring tables to a specified point in time

+

rds:instance:tableRestore

+

N/A

+

Configuring TDE permission

+

rds:instance:tde

+

Only used for RDS for SQL Server DB instances.

+

Changing host permission

+

rds:instance:modifyHost

+

N/A

+

Querying hosts of the corresponding database account

+

rds:instance:list

+

N/A

+

Obtaining a parameter template list

+

rds:param:list

+

N/A

+

Creating a parameter template

+

rds:param:create

+

N/A

+

Modifying parameters in a parameter template

+

rds:param:modify

+

N/A

+

Applying a parameter template

+

rds:param:apply

+

N/A

+

Modifying parameters of a specified DB instance

+

rds:param:modify

+

N/A

+

Obtaining the parameter template of a specified DB instance

+

rds:param:list

+

N/A

+

Obtaining parameters of a specified parameter template

+

rds:param:list

+

N/A

+

Deleting a parameter template

+

rds:param:delete

+

N/A

+

Resetting a parameter template

+

rds:param:reset

+

N/A

+

Comparing parameter templates

+

rds:param:list

+

N/A

+

Saving parameters in a parameter template

+

rds:param:save

+

N/A

+

Querying a parameter template type

+

rds:param:list

+

N/A

+

Setting an automated backup policy

+

rds:instance:modifyBackupPolicy

+

N/A

+

Querying an automated backup policy

+

rds:instance:list

+

N/A

+

Creating a manual backup

+

rds:backup:create

+

N/A

+

Obtaining a backup list

+

rds:backup:list

+

N/A

+

Obtaining the link for downloading a backup file

+

rds:backup:download

+

N/A

+

Deleting a manual backup

+

rds:backup:delete

+

N/A

+

Replicating a backup

+

rds:backup:create

+

N/A

+

Querying the restoration time range

+

rds:instance:list

+

N/A

+

Restoring data to a new DB instance

+

rds:instance:create

+

To select a VPC, subnet, and security group, configure the following actions:

+

vpc:vpcs:list

+

vpc:vpcs:get

+

vpc:subnets:get

+

vpc:securityGroups:get

+

Restoring data to an existing or original DB instance

+

rds:instance:restoreInPlace

+

N/A

+

Obtaining the binlog clearing policy

+

rds:binlog:get

+

N/A

+

Merging binlog files

+

rds:binlog:merge

+

N/A

+

Downloading a binlog file

+

rds:binlog:download

+

N/A

+

Deleting a binlog file

+

rds:binlog:delete

+

N/A

+

Configuring a binlog clearing policy

+

rds:binlog:setPolicy

+

N/A

+

Obtaining a database backup file list

+

rds:backup:list

+

N/A

+

Obtaining a backup database list at a specified time point

+

rds:backup:list

+

N/A

+

Querying a database error log

+

rds:log:list

+

N/A

+

Querying a database slow log

+

rds:log:list

+

N/A

+

Downloading a database error log

+

rds:log:download

+

N/A

+

Downloading a database slow log

+

rds:log:download

+

N/A

+

Enabling or disabling the audit log function

+

rds:auditlog:operate

+

N/A

+

Obtaining an audit log list

+

rds:auditlog:list

+

N/A

+

Querying the audit log policy

+

rds:auditlog:list

+

N/A

+

Obtaining the link for downloading an audit log

+

rds:auditlog:download

+

N/A

+

Obtaining a switchover log

+

rds:log:list

+

N/A

+

Creating a database

+

rds:database:create

+

N/A

+

Querying details about databases

+

rds:database:list

+

N/A

+

Querying authorized databases of a specified user

+

rds:database:list

+

N/A

+

Dropping a database

+

rds:database:drop

+

N/A

+

Creating a database account

+

rds:databaseUser:create

+

N/A

+

Querying details about database accounts

+

rds:databaseUser:list

+

N/A

+

Querying authorized accounts of a specified database

+

rds:databaseUser:list

+

N/A

+

Deleting a database account

+

rds:databaseUser:drop

+

N/A

+

Authorizing a database account

+

rds:databasePrivilege:grant

+

N/A

+

Revoking permissions of a database account

+

rds:databasePrivilege:revoke

+

N/A

+

Viewing a task center list

+

rds:task:list

+

N/A

+

Deleting a task from the task center

+

rds:task:delete

+

N/A

+

Adding nodes

+

rds:instance:expandCluster

+

N/A

+

Configuring autoscaling

+

rds:instance:extendSpace

+

To enable autoscaling, configure the following actions for the IAM users instead of your account:

+
  • iam:agencies:listAgencies
  • iam:agencies:createAgency
  • iam:permissions:listRolesForAgencyOnProject
  • iam:permissions:grantRoleToGroupOnProject
  • iam:roles:listRoles
  • Security Administrator (system role)
+
+
+
+
+
+
+
Parent topic: Introduction
+
+
+ diff --git a/docs/rds/umn/rds_01_0018.html b/docs/rds/umn/rds_01_0018.html index 0e6815fb..86b336f0 100644 --- a/docs/rds/umn/rds_01_0018.html +++ b/docs/rds/umn/rds_01_0018.html @@ -411,91 +411,92 @@

Table 4 lists the major differences of the official Microsoft SQL Server editions.

For more information about function differences among Microsoft SQL Server 2016 official editions, see official documents.

For more information about function differences among Microsoft SQL Server 2017 official editions, see official documents.

+

For more information about function differences among Microsoft SQL Server 2019 official editions, see official documents.

-
Table 4 Differences of Microsoft SQL Server editions

Function Item

+
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/rds/umn/rds_01_0025.html b/docs/rds/umn/rds_01_0025.html deleted file mode 100644 index fc44842a..00000000 --- a/docs/rds/umn/rds_01_0025.html +++ /dev/null @@ -1,14 +0,0 @@ - - -

User Permissions

-

RDS provides two types of user permissions by default: user management and resource management.

-
  • User management permissions cover the management of users, user groups, and user group permissions.
  • Resource management permissions cover the management of controlling operations on cloud service resources.
-

User management allows you to create, delete, and modify users, and allows you to grant permissions to users. Resource management refers to the management of operation permissions such as creating, deleting, modifying, and setting cloud resources. After resources and users are added to a user group, the users can inherit permissions assigned to their user group. User permissions management based on user groups is more organized and helps avoid confusions.

-

For details, see Permissions.

-
-
-
-
Parent topic: Introduction
-
-
- diff --git a/docs/rds/umn/rds_01_0029.html b/docs/rds/umn/rds_01_0029.html index 49166165..4f090bd7 100644 --- a/docs/rds/umn/rds_01_0029.html +++ b/docs/rds/umn/rds_01_0029.html @@ -14,7 +14,7 @@ - @@ -93,6 +93,20 @@ + + + + + + + +
Table 4 Differences of Microsoft SQL Server editions

Function Item

Standard Edition

+

Standard Edition

Enterprise Edition

+

Enterprise Edition

High availability

+

High availability

Mirror HA

+

Mirror HA

Mirror HA

+

Mirror HA

Data compression

+

Data compression

Supported

+

Supported

Supported

+

Supported

SQL Profiler

+

SQL Profiler

Supported

+

Supported

Supported

+

Supported

Column index

+

Column index

Supported

+

Supported

Supported

+

Supported

Table/index partitioning

+

Table/index partitioning

Supported only by Microsoft SQL Server 2014.

+

Supported only by Microsoft SQL Server 2014.

Supported

+

Supported

Change Data Capture (CDC)

+

Change Data Capture (CDC)

Not supported

+

Not supported

Supported

+

Supported

Online DDL

+

Online DDL

Not supported

+

Not supported

Supported

+

Supported

Parallel searches

+

Parallel searches

Not supported

+

Not supported

Supported

+

Supported

Adjustment of partitioned table parallelism

+

Adjustment of partitioned table parallelism

Not supported

+

Not supported

Supported

+

Supported

TDE

+

TDE

Not supported

+

Not supported

Supported

+

Supported

Advanced R integration

+

Advanced R integration

Not supported

+

Not supported

Supported

+

Supported

General-enhanced

+

General-enhanced

1

  • MySQL
  • PostgreSQL
  • Microsoft SQL Server

8

+

128

+

Microsoft SQL Server

+

8

+

256

+

Microsoft SQL Server

+

16

32

diff --git a/docs/rds/umn/rds_02_0001.html b/docs/rds/umn/rds_02_0001.html index 66a2d65b..4187b16c 100644 --- a/docs/rds/umn/rds_02_0001.html +++ b/docs/rds/umn/rds_02_0001.html @@ -2,7 +2,7 @@

Operation Guide

You can create and connect to DB instances on the RDS console.

-

Flowchart

Figure 1 Flowchart
+

Flowchart

Figure 1 Flowchart

Procedure

Table 1 Related operations and references

Operation

diff --git a/docs/rds/umn/rds_02_0008.html b/docs/rds/umn/rds_02_0008.html index 05c491d4..30b11bfb 100644 --- a/docs/rds/umn/rds_02_0008.html +++ b/docs/rds/umn/rds_02_0008.html @@ -4,7 +4,7 @@

Scenarios

This section describes how to create a DB instance on the management console.

The DB instance class and storage space you need depend on your processing power and memory requirements.

-

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 Create DB Instance.
  5. On the displayed page, configure information about your DB instance. Then, click Create Now.

    +

    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 Create DB Instance.
    5. On the displayed page, configure information about your DB instance. Then, click Create Now.

      Table 1 Basic information

      Parameter

      Description

      @@ -77,6 +77,8 @@

      Storage Space (GB)

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

      +
      If the storage type is cloud SSD or extreme SSD, you can enable storage autoscaling. If the available storage drops to a specified threshold, autoscaling is triggered. For details, see Storage Autoscaling.
      • 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.
      +

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

      diff --git a/docs/rds/umn/rds_02_0010.html b/docs/rds/umn/rds_02_0010.html index 70aa00ec..003726e7 100644 --- a/docs/rds/umn/rds_02_0010.html +++ b/docs/rds/umn/rds_02_0010.html @@ -2,7 +2,7 @@

      Overview

      Process

      Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a private network.

      -
      Figure 1 Connecting to a DB instance through a private network
      +
      Figure 1 Connecting to a DB instance through a private network
      diff --git a/docs/rds/umn/rds_02_0016.html b/docs/rds/umn/rds_02_0016.html index b8c15534..9447329e 100644 --- a/docs/rds/umn/rds_02_0016.html +++ b/docs/rds/umn/rds_02_0016.html @@ -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 DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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?

        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

          diff --git a/docs/rds/umn/rds_02_0019.html b/docs/rds/umn/rds_02_0019.html index 43db07c6..c45bd315 100644 --- a/docs/rds/umn/rds_02_0019.html +++ b/docs/rds/umn/rds_02_0019.html @@ -2,7 +2,7 @@

          Overview

          Process

          Figure 1 illustrates the process of connecting to a PostgreSQL DB instance through a public network.

          -
          Figure 1 Connecting to a DB instance through a public network
          +
          Figure 1 Connecting to a DB instance through a public network
          diff --git a/docs/rds/umn/rds_02_0047.html b/docs/rds/umn/rds_02_0047.html index 20436ab7..aa4bb788 100644 --- a/docs/rds/umn/rds_02_0047.html +++ b/docs/rds/umn/rds_02_0047.html @@ -14,8 +14,8 @@
          -

          Using MySQL-Front to Connect to a DB Instance

          1. Start MySQL-Front.
          2. In the displayed dialog box, click New.

            Figure 1 Connection management
            -

          3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

            Figure 2 Adding an account
            +

            Using MySQL-Front to Connect to a DB Instance

            1. Start MySQL-Front.
            2. In the displayed dialog box, click New.

              Figure 1 Connection management
              +

            3. Enter the information of the DB instance to be connected and click Ok, as shown in Figure 2.

              Figure 2 Adding an account
              @@ -52,12 +52,12 @@
              Table 1 Parameter description

              Parameter
              -

            4. In the displayed window, select the connection that you have created in 3 and click Open. If the connection information is correct, the DB instance is successfully connected.

              Figure 3 Opening a session
              +

            5. In the displayed window, select the connection that you have created in 3 and click Open. If the connection information is correct, the DB instance is successfully connected.

              Figure 3 Opening a session

              If the connection fails, see What Should I Do If an ECS Cannot Connect to an RDS DB Instance Through a Private Network?

            -

            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 DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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?

                  • You can also download the certificate bundle, which contains both the new certificate provided since April 2017 and the old certificate.
                  diff --git a/docs/rds/umn/rds_02_0051.html b/docs/rds/umn/rds_02_0051.html index 76a5fa96..6a01243f 100644 --- a/docs/rds/umn/rds_02_0051.html +++ b/docs/rds/umn/rds_02_0051.html @@ -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 DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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?

                  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

                    diff --git a/docs/rds/umn/rds_02_0060.html b/docs/rds/umn/rds_02_0060.html index 7896e5d5..a6d8f8bf 100644 --- a/docs/rds/umn/rds_02_0060.html +++ b/docs/rds/umn/rds_02_0060.html @@ -38,7 +38,7 @@
                    • VPC: indicates the Virtual Private Cloud.
                    • ECS: indicates the Elastic Cloud Server.
                    • If the ECS is in the same VPC as your RDS DB instance, you do not need to apply for an EIP.

                    Figure 1 illustrates the connection over a private network or a public network.

                    -
                    Figure 1 DB instance connection
                    +
                    Figure 1 DB instance connection
                    diff --git a/docs/rds/umn/rds_02_0099.html b/docs/rds/umn/rds_02_0099.html index 73b58c19..c6c3c739 100644 --- a/docs/rds/umn/rds_02_0099.html +++ b/docs/rds/umn/rds_02_0099.html @@ -2,7 +2,7 @@

                    Overview

                    Process

                    Figure 1 illustrates the process of connecting to a MySQL DB instance through a public network.

                    -
                    Figure 1 Connecting to a DB instance through a public network
                    +
                    Figure 1 Connecting to a DB instance through a public network
                    diff --git a/docs/rds/umn/rds_03_0001.html b/docs/rds/umn/rds_03_0001.html index 9b2a932d..7bfa2fba 100644 --- a/docs/rds/umn/rds_03_0001.html +++ b/docs/rds/umn/rds_03_0001.html @@ -2,7 +2,7 @@

                    Overview

                    Process

                    Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a private network.

                    -
                    Figure 1 Connecting to a DB instance through a private network
                    +
                    Figure 1 Connecting to a DB instance through a private network
                    diff --git a/docs/rds/umn/rds_03_0007.html b/docs/rds/umn/rds_03_0007.html index 72d1764a..74fa76b4 100644 --- a/docs/rds/umn/rds_03_0007.html +++ b/docs/rds/umn/rds_03_0007.html @@ -9,20 +9,20 @@
                  7. Run the ping command to connect the EIP that has been bound to the target DB instance in 2.a to check that the local device can connect to the EIP.
                    8. -

                    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
                      +

                      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 Connection Information area on the Basic Information 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.

                      3. 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 DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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.
                            -

                          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
                            +

                          4. Start SQL Server Management Studio.
                          5. 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 Connection Information area on the Basic Information 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.
                            -

                          6. 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
                            +

                          7. 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

                          8. 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_0010.html b/docs/rds/umn/rds_03_0010.html index 9774536f..b9439332 100644 --- a/docs/rds/umn/rds_03_0010.html +++ b/docs/rds/umn/rds_03_0010.html @@ -2,7 +2,7 @@

                          Operation Guide

                          You can create and connect to DB instances on the RDS console.

                          -

                          Flowchart

                          Figure 1 Flowchart
                          +

                          Flowchart

                          Figure 1 Flowchart

                          Procedure

                          Table 1 Related operations and references

                          Operation

                          diff --git a/docs/rds/umn/rds_03_0011.html b/docs/rds/umn/rds_03_0011.html index bb104924..741f28c9 100644 --- a/docs/rds/umn/rds_03_0011.html +++ b/docs/rds/umn/rds_03_0011.html @@ -5,13 +5,13 @@

                          After a DB instance has been created, you can create read replicas for it.

                          A maximum of five read replicas can be created for a primary DB instance.

                          -

                          Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.

                          +

                          Only RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.

                          -

                          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 > Create Read Replica in the Operation column.

                            Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

                            +

                            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 > Create Read Replica in the Operation column.

                              Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

                            5. On the displayed page, configure information about the DB instance and click Next.

                              -

                              Table 1 Basic information

                              Parameter

                              +
                              - @@ -44,9 +44,9 @@
                              Table 1 Basic information

                              Parameter

                              Description

                              +

                              Description
                              -
                              Table 2 Instance specifications

                              Parameter

                              +
                              - @@ -85,9 +85,9 @@
                              Table 2 Instance specifications

                              Parameter

                              Description

                              +

                              Description
                              -
                              Table 3 Network

                              Parameter

                              +
                              - @@ -110,7 +110,7 @@
                              Table 3 Network

                              Parameter

                              Description

                              +

                              Description

                            6. Confirm specifications.

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

                            7. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

                              Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

                              +

                            8. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

                              Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

                              9. diff --git a/docs/rds/umn/rds_03_0013.html b/docs/rds/umn/rds_03_0013.html index 4d8c8d0e..4639433a 100644 --- a/docs/rds/umn/rds_03_0013.html +++ b/docs/rds/umn/rds_03_0013.html @@ -4,7 +4,7 @@

                              You can connect to a DB instance through a non-SSL connection or an SSL connection. The SSL connection encrypts data and is more secure.

                              Preparations

                              1. Prepare an ECS.

                                To connect to a DB instance through a private network, you must first create an ECS.

                                For details about how to create an ECS, see section How Can I Create and Connect to an ECS?

                                -
                                • The ECS and RDS DB instance must be in the same VPC.
                                • The ECS must be allowed by the security group to access RDS DB instances.
                                  • If the security group with which the target DB instance is associated is the default security group, you do not need to configure security group rules.
                                  • If the security group with which the target DB instance is associated is not the default security group, check whether the security group rules allow the ECS to connect to 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.
                                    5. In the Connection Information area, click the security group to view its rules.

                                      If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

                                      +
                                      • The ECS and RDS DB instance must be in the same VPC.
                                      • The ECS must be allowed by the security group to access RDS DB instances.
                                        • If the security group with which the target DB instance is associated is the default security group, you do not need to configure security group rules.
                                        • If the security group with which the target DB instance is associated is not the default security group, check whether the security group rules allow the ECS to connect to 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.
                                          5. In the Connection Information area, click the security group to view its rules.

                                            If the security group rules allow the access from the ECS, the ECS can connect to the DB instance.

                                            If the security group rules do not allow the access from the ECS, you need to add a security group rule. For details, see section Configuring Security Group Rules.

                                        @@ -13,20 +13,20 @@

                                        For details, see section How Can I Install SQL Server Management Studio?

                              -

                              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
                                +

                                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 Connection Information area on the Basic Information page of the DB instance.
                                    • The port is the database port in the Connection Information area on the Basic Information 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.

                                4. 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 DB Information area on the Basic Information page, click in the SSL field 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. In the DB Information area on the Basic Information page, click in the SSL field 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.
                                      -

                                    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
                                      +

                                    4. Start SQL Server Management Studio.
                                    5. 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 Connection Information area on the Basic Information page of the DB instance.
                                        • The port is the database port in the Connection Information area on the Basic Information 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.
                                      -

                                    6. 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
                                      +

                                    7. 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

                                    8. 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_0018.html b/docs/rds/umn/rds_03_0018.html deleted file mode 100644 index 0cb8dfaf..00000000 --- a/docs/rds/umn/rds_03_0018.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                                    Introduction to PostgreSQL Enhanced Edition

                                    -

                                    PostgreSQL Enhanced Edition is developed from PostgreSQL 11. It retains all functions of the PostgreSQL databases. PostgreSQL Enhanced Edition supports system views, PL/SQL, data types, advanced functions, SQL syntax, and null value processing. It helps you reduce costs for migration to the cloud and provides a comprehensive solution with high security, high availability, and high performance.

                                    -
                                    -
                                    -
                                    -
                                    Parent topic: PostgreSQL Enhanced Edition
                                    -
                                    -
                                    - diff --git a/docs/rds/umn/rds_03_0060.html b/docs/rds/umn/rds_03_0060.html index acb2204e..aaedc6b6 100644 --- a/docs/rds/umn/rds_03_0060.html +++ b/docs/rds/umn/rds_03_0060.html @@ -38,7 +38,7 @@
                                    • VPC: indicates the Virtual Private Cloud.
                                    • ECS: indicates the Elastic Cloud Server.
                                    • If the ECS is in the same VPC as your RDS DB instance, you do not need to apply for an EIP.

                                    Figure 1 illustrates the connection over a private network or a public network.

                                    -
                                    Figure 1 DB instance connection
                                    +
                                    Figure 1 DB instance connection
                                    diff --git a/docs/rds/umn/rds_03_0065.html b/docs/rds/umn/rds_03_0065.html index c0f3b9e5..befe3e9d 100644 --- a/docs/rds/umn/rds_03_0065.html +++ b/docs/rds/umn/rds_03_0065.html @@ -4,7 +4,7 @@

                                    Scenarios

                                    You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see "Creating a DB Instance" in the Relational Database Service API Reference. This section describes how to create a DB instance on the RDS console.

                                    RDS allows you to tailor your computing resources and storage space to your business needs.

                                    -

                                    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 Create DB Instance.
                                    5. On the displayed page, configure information about your DB instance. Then, click Create Now.

                                      +

                                      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 Create DB Instance.
                                      5. On the displayed page, configure information about your DB instance. Then, click Create Now.

                                        Table 1 Basic information

                                        Parameter

                                        Description

                                        diff --git a/docs/rds/umn/rds_03_0066.html b/docs/rds/umn/rds_03_0066.html index d4df5ca4..4a8e9496 100644 --- a/docs/rds/umn/rds_03_0066.html +++ b/docs/rds/umn/rds_03_0066.html @@ -2,7 +2,7 @@

                                        Overview

                                        Process

                                        Figure 1 illustrates the process of connecting to a Microsoft SQL Server DB instance through a public network.

                                        -
                                        Figure 1 Connecting to a DB instance through a public network
                                        +
                                        Figure 1 Connecting to a DB instance through a public network
                                        diff --git a/docs/rds/umn/rds_03_0100.html b/docs/rds/umn/rds_03_0100.html index 8403a63d..229a5996 100644 --- a/docs/rds/umn/rds_03_0100.html +++ b/docs/rds/umn/rds_03_0100.html @@ -3,7 +3,7 @@

                                        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.

                                        -

                                        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 Basic Information 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 Basic Information 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.
                                        diff --git a/docs/rds/umn/rds_04_0001.html b/docs/rds/umn/rds_04_0001.html deleted file mode 100644 index 78b285e0..00000000 --- a/docs/rds/umn/rds_04_0001.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

                                        PostgreSQL Enhanced Edition

                                        -
                                        - - diff --git a/docs/rds/umn/rds_04_0002.html b/docs/rds/umn/rds_04_0002.html deleted file mode 100644 index 0dc2305b..00000000 --- a/docs/rds/umn/rds_04_0002.html +++ /dev/null @@ -1,386 +0,0 @@ - - -

                                        Functions

                                        -

                                        This section describes the built-in functions and advanced function packages added to PostgreSQL Enhanced Edition on the basis of PostgreSQL 11 open-source edition.

                                        - -
                                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                        Table 1 Built-in functions

                                        Built-in Function

                                        -

                                        Description

                                        -

                                        add_months(date,integer)

                                        -

                                        Returns the date plus integer months. The return type is DATE.

                                        -

                                        appendchildxml(XMLType_instance, XPath_string, value_expr[, namespace_string])

                                        -

                                        Appends the value_expr node onto XPath_string specified by XMLType_instance. The namespace_string provides namespace information for the XPath_string.

                                        -

                                        asciistr(string)

                                        -

                                        Returns an ASCII version of the string in the database character set. Non-ASCII characters are not supported.

                                        -

                                        bin_to_num(expr_list)

                                        -

                                        Converts a binary string in expr_list to its equivalent decimal number. The return type is NUMBER.

                                        -

                                        bitand(number1,number2)

                                        -

                                        Returns the bitwise 'AND' for two supplied integers number1 and number2. The return type is BIT.

                                        -

                                        convert(char, dest_char_set[, source_char_set])

                                        -

                                        Converts char in the source_char_set to the dest_char_set encoding format. This function takes effect only on the server.

                                        -

                                        cosh(n)

                                        -

                                        Returns the hyperbolic cosine of argument n.

                                        -

                                        decode(expr,search1, result1[[,search2, result2],......][, default])

                                        -

                                        Compares expr to each search value (search1, search2, etc). If expr is equal to a search, then Oracle Database returns the corresponding result. If no match is found, then Oracle returns default. If default is omitted, then Oracle returns null.

                                        -

                                        empty_blob()

                                        -

                                        Returns an empty BLOB.

                                        -

                                        hextoraw(char)

                                        -

                                        Converts a hexadecimal string to a raw value.

                                        -

                                        instrb(string, substring[, position[, occurrence]])

                                        -

                                        Searches a string for a substring using characters and return the position in the string that is the first character of a specified occurrence of the substring. The functions vary in how they determine the position of the substring to return.

                                        -

                                        last_day(date)

                                        -

                                        Returns the date of the last day of the month that contains date.

                                        -

                                        lengthb(char)

                                        -

                                        Returns the length of char. Char can be any of the data types (CHAR, VARCHAR2, NCHAR, or NVARCHAR2), or types (such as integer) that can be implicitly converted into character strings.

                                        -

                                        listagg(measure_expr[, 'delimiter']) within group(order_by_clause) [over query_partition_clause]

                                        -

                                        Sorts the values of the column expression measure_expr in the query_partition_clause group based on the order_by_clause rule and aggregates them into one row. Values are separated by delimiter.

                                        -

                                        lnnvl(condition)

                                        -

                                        Returns a value of condition expression. The return type is BOOLEAN.

                                        -

                                        mod(n2, n1)

                                        -

                                        Returns the remainder of n2 divided by n1. Returns n2 if n1 is 0.

                                        -

                                        months_between(date1, date2)

                                        -

                                        Returns the number of months between dates date1 and date2. If date1 is earlier than date2, then the result is negative.

                                        -

                                        nanvl(n2, n1)

                                        -

                                        Returns n1 if the single- or double-precision floating point number input value n2 is NAN. If the input value n2 is not NAN, n2 is returned.

                                        -

                                        nchr(number)

                                        -

                                        Returns the character having the binary equivalent to number in the national character set.

                                        -

                                        new_time(date, timezone1, timezone2)

                                        -

                                        Returns the date and time in time zone timezone2 when date and time in time zone timezone1 are date. The return type is DATE.

                                        -

                                        next_day(date, char)

                                        -

                                        Returns the date of the first weekday named by char that is later than the date (including workdays, weekends, and holidays). The return type is DATE.

                                        -

                                        numtodsinterval(n, interval_unit)

                                        -

                                        Converts n to an INTERVAL DAY TO SECOND literal. The value for interval_unit specifies the unit of n and must resolve to 'DAY', 'HOUR', 'MINUTE', and 'SECOND'.

                                        -

                                        numtoyminterval(n, 'interval_unit')

                                        -

                                        Converts n to an INTERVAL YEAR TO MONTH literal. The value for interval_unit can be YEAR or MONTH.

                                        -

                                        nlssort(char[, nlsparam])

                                        -

                                        Sorts the char string according to the sorting character set specified by nlsparam. By default, char is used for sorting.

                                        -

                                        nls_upper(char[, nlsparam])

                                        -

                                        Converts all alphabetic characters in the character string char to uppercase letters based on the sort sequence specified by nlsparam. The character string type is CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB, and nlsparam is in the form of NLS_SORT = sort.

                                        -

                                        nls_lower(char[, nlsparam])

                                        -

                                        Converts all alphabetic characters in the character string char to lowercase letters based on the sort sequence specified by nlsparam. The character string type is CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB, and nlsparam is in the form of NLS_SORT = sort.

                                        -

                                        nvl(expr1, expr2)

                                        -

                                        Returns the first non-null value in expr1 and expr2.

                                        -

                                        rawtohex(raw)

                                        -

                                        Converts raw to a character value containing its hexadecimal representation.

                                        -

                                        regexp_count(source_char, pattern, position, match_param)

                                        -

                                        Returns the number of times a pattern occurs in a source string starting from the position that indicates the source_char character where the database begins the search. The match_param parameter is a text literal that lets you change the default matching behavior of the function. For example, match_param='i' specifies case-insensitive matching.

                                        -

                                        regexp_instr(source_char, pattern[, position[, occurrence[, return_opt[, match_param[, subexpr]]]]])

                                        -

                                        Extends the INSTR function and allows regular expression matching. The return type is INTEGER.

                                        -
                                        • position: indicates the start position of the search.
                                        • occurrence: indicates the sequence number of the pattern in source_char.
                                        • return_opt:
                                          • The value 0 indicates the start position of the return mode.
                                          • The value 1 indicates the end position of the return mode.
                                          -
                                        • match_param: indicates the control parameter of the regular expression, such as case sensitive.
                                        • subexpr: indicates the group number of the regular expression group.
                                        -

                                        regexp_like(source_char, pattern[,match_param])

                                        -

                                        source_char is a character expression. Pattern is the regular expression. The match_param parameter is a text literal that lets you change the default matching behavior of the function.

                                        -

                                        regexp_substr(source_char, pattern[,position[,occurrence[,match_param[,subexpr]]]])

                                        -

                                        Matches the character string in the source_char string based on the regular expression.

                                        -
                                        • source_char is the text expression that is searched. Supports all character strings, including CHAR, VARCHAR2, NCHAR, or NVARCHAR2, or types (such as integer) that can be implicitly converted into character strings.
                                        • pattern is the text expression to search for.
                                        • position is a nonzero integer indicating the character of source_char where the function begins the search.
                                        • occurrence is an integer indicating which occurrence of pattern the function should search for.
                                        • match_parameter is a text expression that lets you change the default matching behavior of the function.
                                        • subexpr is a nonnegative integer from 0 to 9 indicating which subexpression in pattern is to be returned by the function.
                                        -

                                        raise_application_error(errnum, errmsg)

                                        -

                                        Sends the error code errnum and error message errmsg to the client.

                                        -

                                        remainder(n2, n1)

                                        -

                                        Returns the remainder of n2 divided by n1. The remainder function is similar to mod except that mod uses floor in its formula, whereas reminder uses ROUND. The return type is NUMERIC or double-precision floating-point number (determined by the input parameter type).

                                        -

                                        round(n,precision)

                                        -

                                        Returns n rounded to integer places to the right of the decimal point. The precision is the number of digits in a number.

                                        -

                                        scn_to_timestamp(number)

                                        -

                                        Returns the approximate timestamp associated with a system change number (SCN).

                                        -

                                        sinh(n)

                                        -

                                        Returns the hyperbolic sine of n. If n is BINARY_FLOAT, the return type is BINARY_DOUBLE. Otherwise, the return type is NUMERIC.

                                        -

                                        substr(char,position[,substring_length])

                                        -

                                        Returns a portion of string, beginning at a specified position in the string. The functions vary in how they calculate the length of the substring to return. If substring_length is not specified, the function returns all characters to the end of string.

                                        -

                                        substrb(char, position[, substring_length])

                                        -

                                        Returns a portion of char, beginning at a specified position in the string. The functions vary in how they calculate the length of the substring to return. If substring_length is not specified, the function returns all characters to the end of string.

                                        -

                                        sys_context(namespace, parameter)

                                        -

                                        Returns the value of parameter associated with the context namespace. The return type is VARCHAR2.

                                        -

                                        sys_guid()

                                        -

                                        Returns a globally unique identifier (RAW value).

                                        -

                                        sys_connect_by_path(column, char)

                                        -

                                        Is valid only in CONNECT BY queries and returns the path of a column value from root to node.

                                        -

                                        tanh(n)

                                        -

                                        Returns the hyperbolic tangent of argument n.

                                        -

                                        to_blob(char)

                                        -

                                        Converts char strings to BLOB values. Char can be any of the data types (CHAR, VARCHAR2, NCHAR, or NVARCHAR2), or types (such as integer) that can be implicitly converted into character strings.

                                        -

                                        to_binary_float(expr)

                                        -

                                        Converts expr to the single-precision float type.

                                        -

                                        to_binary_double(expr)

                                        -

                                        Converts expr to the double-precision float type.

                                        -

                                        to_clob(char)

                                        -

                                        Converts char to the CLOB data type.

                                        -

                                        to_char(char)

                                        -

                                        Supports char types: char, character, and varchar.

                                        -

                                        to_date(char[,fmt])

                                        -

                                        Converts char of the CHAR, VARCHAR2, NCHAR, NVARCHAR2, or TIMESTAMP data type to a value of the DATE data type according to the fmt format. If fmt is omitted, char must use the default format of the DATE data type.

                                        -

                                        to_dsinterval('sql_format' | 'ds_iso_format')

                                        -

                                        Converts the time character string of the SQL standard (such as '100 00:00:00') or ISO standard (such as 'P100DT05H') to the INTERVAL DAY TO SECOND data type.

                                        -

                                        to_multi_byte(char)

                                        -

                                        Converts a single-byte character char into a multi-byte character.

                                        -

                                        to_number(expr)

                                        -

                                        Converts expr to a value of NUMBER data type.

                                        -

                                        to_number(expr, fmt, 'nlsparam')

                                        -

                                        -

                                        Converts expr to a value of NUMBER data type in the format specified by fmt. The nlsparam is an international language parameter and supports the following parameters: NLS_NUMERIC_CHARACTERS, NLS_CURRENCY, and NLS_ISO_CURRENCY.

                                        -

                                        to_timestamp(char[,fmt])

                                        -

                                        Converts char of the CHAR, VARCHAR2, NCHAR, NVARCHAR2, or TIMESTAMP data type to a value of the timestamp data type according to the fmt format. If fmt is omitted, char must use the default format of the TIMESTAMP data type.

                                        -

                                        to_single_byte(char)

                                        -

                                        Converts multibyte characters to their corresponding single-byte characters.

                                        -

                                        to_yminterval('sql_format' | 'ym_iso_format')

                                        -

                                        Converts the time character string of the SQL standard (such as '01-02') or ISO standard (such as 'P1Y2M') to the INTERVAL MONTH TO YEAR data type.

                                        -

                                        timestamp_to_scn(timestamp)

                                        -

                                        Returns the approximate system change number (SCN) associated with a timestamp.

                                        -

                                        trunc(date[, fmt])

                                        -

                                        Truncates date according to the date format specified by fmt. The return type is DATE. If fmt is omitted, the default date format is 'DDD'.

                                        -

                                        tz_offset({time_zone_name | '{+|-}hh:mi'})

                                        -

                                        Returns the specified time zone offset. The return type is VARCHAR2. The parameter is a character string in the time_zone_name or '{+|-}hh:mi' format.

                                        -

                                        value(correlation_variable)

                                        -

                                        Returns the recorded row associated with correlation_variable in object table mode. The return type is the object table associated with correlation_variable.

                                        -
                                        -
                                        - -
                                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                        Table 2 Advanced function packages

                                        Advanced Function Package

                                        -

                                        Description

                                        -

                                        DBMS_OUTPUT.PUT(item)

                                        -

                                        Places the item string in the local buffer. Item indicates all types that can be converted into character strings.

                                        -

                                        DBMS_OUTPUT.PUT_LINE(item)

                                        -

                                        Places the item string in the local buffer and outputs all the content in the local buffer. Item indicates all types that can be converted into character strings.

                                        -

                                        DBMS_RANDOM.SEED(val)

                                        -

                                        Val is the seed number used to generate a random number. It can be a character string or a digit.

                                        -

                                        DBMS_RANDOM.VALUE([low,high])

                                        -

                                        Returns a 16-digit random number between low and high. If the range of low and high is not specified, the default value range is 0-1.

                                        -

                                        dbms_lob.getlength(lob_loc {clob|blob})

                                        -

                                        Returns the LOB length specified by lob_loc.

                                        -

                                        dbms_lob.read(lob_loc, amount, offset, buffer)

                                        -

                                        Returns the specified amount into the buffer parameter, starting from an absolute offset from the beginning of the LOB.

                                        -

                                        dbms_lob.write(lob_loc, amount, offset, buffer)

                                        -

                                        Writes the buffer content to the large object lob_loc buffer (the referenced large object is not affected) starting at offset. The amount represents the size.

                                        -

                                        utl_raw.cast_to_raw(char)

                                        -

                                        Converts char of the VARCHAR2 data type to RAW. The return type is RAW.

                                        -

                                        utl_raw.length(raw)

                                        -

                                        Returns the length of the raw data type. The return type is NUMBER.

                                        -

                                        utl_raw.cast_from_binary_integer(n, endianess)

                                        -

                                        Converts the integer n to the RAW type based on the memory alignment mode specified by endianess. The values of endianess are as follows:

                                        -
                                        • 1: big_endian
                                        • 2: little_endian
                                        • 3: machine_endian
                                        -
                                        -
                                        -
                                        -
                                        -
                                        -
                                        Parent topic: PostgreSQL Enhanced Edition
                                        -
                                        -
                                        - diff --git a/docs/rds/umn/rds_04_0060.html b/docs/rds/umn/rds_04_0060.html index 0d166a2a..608efacb 100644 --- a/docs/rds/umn/rds_04_0060.html +++ b/docs/rds/umn/rds_04_0060.html @@ -38,7 +38,7 @@
                                        • VPC: indicates the Virtual Private Cloud.
                                        • ECS: indicates the Elastic Cloud Server.
                                        • If the ECS is in the same VPC as the RDS DB instance, you do not need to apply for an EIP.

                                        Figure 1 illustrates the connection over a private network or a public network.

                                        -
                                        Figure 1 DB instance connection
                                        +
                                        Figure 1 DB instance connection
                                        diff --git a/docs/rds/umn/rds_04_0061.html b/docs/rds/umn/rds_04_0061.html index 5452be9d..8e641154 100644 --- a/docs/rds/umn/rds_04_0061.html +++ b/docs/rds/umn/rds_04_0061.html @@ -4,7 +4,7 @@

                                        Scenarios

                                        You can create DB instances using the RDS console or APIs. For details about how to create DB instances using APIs, see the "Creating a DB Instance" section in the Relational Database Service API Reference. This section describes how to create a DB instance on the RDS console.

                                        The DB instance class and storage space you need depend on your processing power and memory requirements.

                                        -

                                        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 Create DB Instance.
                                        5. On the displayed page, configure information about your DB instance. Then, click Create Now.

                                          +

                                          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 Create DB Instance.
                                          5. On the displayed page, configure information about your DB instance. Then, click Create Now.

                                            Table 1 Basic information

                                            Parameter

                                            Description

                                            diff --git a/docs/rds/umn/rds_05_0001.html b/docs/rds/umn/rds_05_0001.html index 4ac03769..5cfb34b8 100644 --- a/docs/rds/umn/rds_05_0001.html +++ b/docs/rds/umn/rds_05_0001.html @@ -18,12 +18,16 @@
                                          6. Scaling up Storage Space
                                            7. +
                                          7. Storage Autoscaling
                                            +
                                          8. Changing the Maintenance Window
                                          9. Changing a DB Instance Type from Single to Primary/Standby
                                          10. Manually Switching Between Primary and Standby DB Instances
                                            11. +
                                          11. Migrating a Standby DB Instance
                                            +
                                            12. diff --git a/docs/rds/umn/rds_05_0003.html b/docs/rds/umn/rds_05_0003.html index 26cbcb19..7adab086 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 target primary/standby DB instances.
                                            5. In the DB Information area on the Basic Information page, click Upgrade in the DB Engine Version field.
                                            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 target primary/standby DB instances.
                                            5. In the DB Information area on the Basic Information page, click Upgrade in the DB Engine Version field.
                                            6. In the displayed dialog box, select a scheduled time and click OK.
                                            diff --git a/docs/rds/umn/rds_05_0017.html b/docs/rds/umn/rds_05_0017.html index a8817b86..6d2e0ee0 100644 --- a/docs/rds/umn/rds_05_0017.html +++ b/docs/rds/umn/rds_05_0017.html @@ -3,9 +3,9 @@

                                            Exporting DB Instance Information

                                            Scenarios

                                            You can export information about all or selected DB instances to view and analyze DB instance information.

                                            -

                                            Exporting Information About All DB Instances

                                            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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                            5. Find a .csv file locally after the export task is completed.
                                            +

                                            Exporting Information About All DB Instances

                                            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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                            5. Find a .csv file locally after the export task is completed.
                                            -

                                            Exporting Information About Selected DB Instances

                                            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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                            5. Find a .csv file locally after the export task is completed.
                                            +

                                            Exporting Information About Selected DB Instances

                                            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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                            5. Find a .csv file locally after the export task is completed.
                                            diff --git a/docs/rds/umn/rds_05_0018.html b/docs/rds/umn/rds_05_0018.html index eeb37dd8..24a4ea1a 100644 --- a/docs/rds/umn/rds_05_0018.html +++ b/docs/rds/umn/rds_05_0018.html @@ -4,7 +4,7 @@

                                            Scenarios

                                            You can apply parameter templates to DB instances as needed.

                                            • The parameter innodb_buffer_pool_size is determined by the memory. DB instances of different specifications have different value ranges. If this parameter value is out of range of the DB instance that the parameter template applies to, the maximum value within the range is used.
                                            • A parameter template can be applied only to DB instances of the same DB engine version.
                                            -

                                            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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                              • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                              • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
                                              +

                                              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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                                • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                                • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.

                                                A parameter template can be applied to one or more DB instances.

                                              5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

                                                After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

                                              diff --git a/docs/rds/umn/rds_05_0023.html b/docs/rds/umn/rds_05_0023.html index 699fce2b..da88f19e 100644 --- a/docs/rds/umn/rds_05_0023.html +++ b/docs/rds/umn/rds_05_0023.html @@ -3,8 +3,8 @@

                                              Changing a DB Instance Type from Single to Primary/Standby

                                              Scenarios

                                              • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability. This operation does not affect the services running on the primary DB instance.
                                              • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
                                              -

                                              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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                -

                                              5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                              6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
                                                +

                                                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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                  Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                  +

                                                5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                                6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                  • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.

                                              diff --git a/docs/rds/umn/rds_05_0024.html b/docs/rds/umn/rds_05_0024.html index 898e3a05..8122de79 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.
                                              5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                              6. In the displayed dialog box, enter a new floating 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.
                                                5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                                6. In the displayed dialog box, enter a new floating 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 4165eaeb..5f0971ac 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. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
                                              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. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
                                                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_05_0039.html b/docs/rds/umn/rds_05_0039.html new file mode 100644 index 00000000..13ed3a6b --- /dev/null +++ b/docs/rds/umn/rds_05_0039.html @@ -0,0 +1,44 @@ + + +

                                                Storage Autoscaling

                                                +

                                                Scenarios

                                                With storage autoscaling enabled, when RDS detects that you are running out of database space, it automatically scales up your storage.

                                                +

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

                                                +

                                                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 common I/O and ultra-high I/O 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.
                                                +
                                                +

                                                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 (click in front of a DB instance to locate the read replica).
                                                5. In the Storage Space area, click Configure Autoscaling.
                                                6. In the displayed dialog box, set the following parameters:

                                                  +

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

                                                  Parameter

                                                  +

                                                  Description

                                                  +

                                                  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.

                                                  +
                                                  +
                                                  +

                                                7. Click OK.
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: Instance Modifications
                                                +
                                                +
                                                + diff --git a/docs/rds/umn/rds_05_0044.html b/docs/rds/umn/rds_05_0044.html index 703fcb5d..46f70edd 100644 --- a/docs/rds/umn/rds_05_0044.html +++ b/docs/rds/umn/rds_05_0044.html @@ -5,13 +5,13 @@
                                                • Before restoring data, ensure that the ECS has been installed with the SQL Server database service running a same or later version than the SQL Server databases.

                                                Procedure

                                                1. Download SSMS and upload it to the ECS for installation.

                                                  Download SSMS 18.0 (GA) from the website and upload it to the ECS.

                                                  -

                                                2. On the ECS, decompress the RDS full backup file that has been downloaded.
                                                3. Start the SSMS client.
                                                4. Log in to the local database service through the SSMS client.
                                                5. In the SSMS client, right-click Databases and choose Restore Database.

                                                  -

                                                6. In the displayed Restore Database dialog box, select Device in the Source pane. In the displayed Select backup devices dialog box, specify the backup media and its location and click OK.

                                                  1. Set Backup media type to File.

                                                    -
                                                  2. Click Add to add the decompressed backup file (in the .bak format) and configure required information on the Options page.
                                                    Figure 1 Adding a backup file
                                                    -
                                                    Figure 2 Configuring required options
                                                    +

                                                  3. On the ECS, decompress the RDS full backup file that has been downloaded.
                                                  4. Start the SSMS client.
                                                  5. Log in to the local database service through the SSMS client.
                                                  6. In the SSMS client, right-click Databases and choose Restore Database.

                                                    +

                                                  7. In the displayed Restore Database dialog box, select Device in the Source pane. In the displayed Select backup devices dialog box, specify the backup media and its location and click OK.

                                                    1. Set Backup media type to File.

                                                      +
                                                    2. Click Add to add the decompressed backup file (in the .bak format) and configure required information on the Options page.
                                                      Figure 1 Adding a backup file
                                                      +
                                                      Figure 2 Configuring required options

                                                    3. Click OK to add the backup file to the backup media list and click OK again to restore the backup file to a self-built database.

                                                    -

                                                    +

                                                diff --git a/docs/rds/umn/rds_05_0055.html b/docs/rds/umn/rds_05_0055.html index c23030fb..9bf7a025 100644 --- a/docs/rds/umn/rds_05_0055.html +++ b/docs/rds/umn/rds_05_0055.html @@ -5,7 +5,7 @@
                                                • You can create DB instances with the same configurations numerous times.
                                                • This function is unavailable for read replicas.
                                                -

                                                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 > Create Same DB Instance in the Operation column.
                                                5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Create Now.

                                                  For details about MySQL DB instance configurations, see section Step 1: Create a 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 > Create Same DB Instance in the Operation column.
                                                  5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Create Now.

                                                    For details about MySQL DB instance configurations, see section Step 1: Create a DB Instance.

                                                  6. Confirm the instance specifications.

                                                  7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

                                                    You can manage the DB instance on the Instances page.

                                                  diff --git a/docs/rds/umn/rds_05_0057.html b/docs/rds/umn/rds_05_0057.html index 15534379..be62a825 100644 --- a/docs/rds/umn/rds_05_0057.html +++ b/docs/rds/umn/rds_05_0057.html @@ -5,7 +5,7 @@

                                                  Constraints

                                                  • If you stop a primary DB instance, read replicas (if there are any) will also be stopped. They are stopped for up to seven days. You cannot stop a read replica without stopping the primary DB instance.
                                                  • A stopped DB instance will not be moved to the recycle bin after being deleted.
                                                  • If you do not manually start your stopped DB instance after seven days, your DB instance is automatically started during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start a DB instance, see Starting a DB Instance.
                                                  • After a DB instance is stopped, billing for instance usage duration will stop.
                                                  -

                                                  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 primary DB instance that you want to stop and choose More > Stop in the Operation column.
                                                  5. In the displayed dialog box, click Yes.
                                                  6. Refresh the DB instance list and view the status of the DB instance. If the status is Stopped, the DB instance is stopped successfully.
                                                  +

                                                  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 primary DB instance that you want to stop and choose More > Stop in the Operation column.
                                                  5. In the displayed dialog box, click Yes.
                                                  6. Refresh the DB instance list and view the status of the DB instance. If the status is Stopped, the DB instance is stopped successfully.

                                                  diff --git a/docs/rds/umn/rds_05_0058.html b/docs/rds/umn/rds_05_0058.html index 52b80cb2..16507699 100644 --- a/docs/rds/umn/rds_05_0058.html +++ b/docs/rds/umn/rds_05_0058.html @@ -5,7 +5,7 @@

                                                Constraints

                                                • If you start a primary DB instance, read replicas (if there are any) will also be started.
                                                • Only DB instances in Stopped state can be started. After this function is enabled, billing for instance usage duration will start.
                                                -

                                                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 primary DB instance that you want to start and choose More > Start in the Operation column.
                                                5. In the displayed dialog box, click Yes.
                                                6. Refresh the DB instance list and view the status of the DB instance. If the status is Available, the DB instance is started successfully.
                                                +

                                                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 primary DB instance that you want to start and choose More > Start in the Operation column.
                                                5. In the displayed dialog box, click Yes.
                                                6. Refresh the DB instance list and view the status of the DB instance. If the status is Available, the DB instance is started successfully.

                                                diff --git a/docs/rds/umn/rds_05_0060.html b/docs/rds/umn/rds_05_0060.html new file mode 100644 index 00000000..46ac6212 --- /dev/null +++ b/docs/rds/umn/rds_05_0060.html @@ -0,0 +1,18 @@ + + +

                                                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.6, 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 DB Instance 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.
                                                  • In the DB Information on the Basic Information page, you can view the AZ hosting the standby DB instance.
                                                  +

                                                +
                                                +

                                                +
                                                +
                                                +
                                                +
                                                Parent topic: Instance Modifications
                                                +
                                                +
                                                + diff --git a/docs/rds/umn/rds_05_0098.html b/docs/rds/umn/rds_05_0098.html index 224f0da6..36e6d86c 100644 --- a/docs/rds/umn/rds_05_0098.html +++ b/docs/rds/umn/rds_05_0098.html @@ -3,7 +3,7 @@

                                                Viewing Application Records of a Parameter Template

                                                Scenarios

                                                You can view the application records of a parameter template.

                                                -

                                                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. Choose Parameter Template Management in the navigation pane on the left.
                                                5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                  You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                  +

                                                  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. Choose Parameter Template Management in the navigation pane on the left.
                                                  5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                diff --git a/docs/rds/umn/rds_05_0099.html b/docs/rds/umn/rds_05_0099.html index abae859d..c1a65af7 100644 --- a/docs/rds/umn/rds_05_0099.html +++ b/docs/rds/umn/rds_05_0099.html @@ -5,11 +5,11 @@

                                                An exported or custom parameter template has initially a blank change history.

                                                -

                                                Viewing Change History of 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.
                                                5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                  You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                  +

                                                  Viewing Change History of 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.
                                                  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                    You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                    You can apply the parameter template to DB instances as required by referring to Applying a Parameter Template.

                                                  -

                                                  Viewing Change History of a Parameter Template

                                                  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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                  5. On the displayed page, choose Change History in the navigation pane on the left.

                                                    You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                    +

                                                    Viewing Change History of a Parameter Template

                                                    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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                    5. On the displayed page, choose Change History in the navigation pane on the left.

                                                      You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                  diff --git a/docs/rds/umn/rds_06_0003.html b/docs/rds/umn/rds_06_0003.html index a273ab7f..a281f33c 100644 --- a/docs/rds/umn/rds_06_0003.html +++ b/docs/rds/umn/rds_06_0003.html @@ -11,7 +11,7 @@
                                                  • RDS has been running properly for about 10 minutes.

                                                    For a newly created RDS DB instance, you need to wait a bit before you can view the 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                  Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                    Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

                                                  5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

                                                    Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

                                                  diff --git a/docs/rds/umn/rds_06_0005.html b/docs/rds/umn/rds_06_0005.html index 97f31e1c..af096003 100644 --- a/docs/rds/umn/rds_06_0005.html +++ b/docs/rds/umn/rds_06_0005.html @@ -6,7 +6,7 @@

                                                Procedure

                                                1. Log in to the management console.
                                                2. Choose Management & Governance > Cloud Trace Service.
                                                3. Choose Trace List in the navigation pane on the left.
                                                4. Filter conditions to query traces. The details are described as follows:

                                                  • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

                                                    When you select Resource ID for Search By, you also need to select or enter a resource ID.

                                                  • Operator: Select a specific operator from the drop-down list.
                                                  • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
                                                  • In the upper right corner of the page, you can specify a time range for querying traces.
                                                  -

                                                5. Select the search criteria, and click Query.
                                                6. Click on the left of the required trace to expand its details.
                                                7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                  For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                                  +

                                                9. Select the search criteria, and click Query.
                                                10. Click on the left of the required trace to expand its details.
                                                11. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                12. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                  For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                              diff --git a/docs/rds/umn/rds_07_0000.html b/docs/rds/umn/rds_07_0000.html new file mode 100644 index 00000000..90745286 --- /dev/null +++ b/docs/rds/umn/rds_07_0000.html @@ -0,0 +1,17 @@ + + +

                                              Permissions Management

                                              +
                                              + + diff --git a/docs/rds/umn/rds_07_0002.html b/docs/rds/umn/rds_07_0002.html new file mode 100644 index 00000000..052f81f4 --- /dev/null +++ b/docs/rds/umn/rds_07_0002.html @@ -0,0 +1,26 @@ + + +

                                              Creating a User and Granting Permissions

                                              +

                                              This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:

                                              +
                                              • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing RDS resources.
                                              • Grant only the permissions required for users to perform a specific task.
                                              • Entrust a account or cloud service to perform efficient O&M on your RDS resources.
                                              +

                                              If your account does not require individual IAM users, skip this chapter.

                                              +

                                              This section describes the procedure for granting permissions (see Figure 1).

                                              +

                                              Prerequisites

                                              Learn about the permissions (see Permissions Management) supported by RDS and choose policies or roles according to your requirements.For the system policies of other services, see Permissions.

                                              +
                                              +

                                              Process Flow

                                              Figure 1 Process for granting RDS permissions
                                              +
                                              1. Create a user group and assign permissions to it.

                                                Create a user group on the IAM console, and attach the RDS ReadOnlyAccess policy to the group.

                                                +

                                                To use some interconnected services, you also need to configure permissions of such services.

                                                +

                                                For example, to connect to your DB instance through the console, configure the DAS FullAccess permission of Data Admin Service (DAS) besides RDS ReadOnlyAccess.

                                                +
                                                +
                                              2. Create an IAM user and add it to the user group.

                                                Create a user on the IAM console and add the user to the group created in 1.

                                                +
                                              3. Log in and verify permissions.

                                                Log in to the RDS console by using the created user, and verify that the user only has read permissions for RDS.

                                                +
                                                • Choose Service List > Relational Database Service and click Buy DB Instance. If a message appears indicating that you have insufficient permissions to perform the operation, the RDS ReadOnlyAccess policy has already been applied.
                                                • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the RDS ReadOnlyAccess policy has already taken effect.
                                                +
                                              +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Permissions Management
                                              +
                                              +
                                              + diff --git a/docs/rds/umn/rds_07_0003.html b/docs/rds/umn/rds_07_0003.html new file mode 100644 index 00000000..a7dbcae4 --- /dev/null +++ b/docs/rds/umn/rds_07_0003.html @@ -0,0 +1,32 @@ + + +

                                              RDS Custom Policies

                                              +

                                              Custom policies can be created to supplement the system policies of RDS.

                                              +

                                              You can create custom policies in either of the following two ways:

                                              +
                                              • Visual editor: Select cloud services, actions, resources, and request conditions without the need to know policy syntax.
                                              • JSON: Edit JSON policies from scratch or based on an existing policy.
                                              +

                                              For details, see Creating a Custom Policy. The following section contains examples of common RDS custom policies.

                                              +

                                              Example Custom Policies

                                              • Example 1: Allowing users to create RDS DB instances
                                                {
+	"Version": "1.1",
+	"Statement": [{
+		"Effect": "Allow",
+		"Action": ["rds:instance:create"]
+	}]
+}
                                                +
                                              • Example 2: Denying RDS DB instance deletion

                                                A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user include both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

                                                +

                                                The following method can be used if you need to assign permissions of the RDS FullAccess policy to a user but you want to prevent the user from deleting RDS DB instances. Create a custom policy for denying RDS DB instance deletion, and attach both policies to the group the user belongs to. Then, the user can perform all operations on RDS DB instances except deleting RDS DB instances. The following is an example deny policy:

                                                +
                                                {
+	"Version": "1.1",
+	"Statement": [{
+		"Action": ["rds:instance:delete"],
+		"Effect": "Deny"
+	}]
+}
                                                +
                                              +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Permissions Management
                                              +
                                              +
                                              + diff --git a/docs/rds/umn/rds_08_0000.html b/docs/rds/umn/rds_08_0000.html index 1e609828..01d2b7a0 100644 --- a/docs/rds/umn/rds_08_0000.html +++ b/docs/rds/umn/rds_08_0000.html @@ -8,6 +8,8 @@
                                            5. Parameter Tuning
                                              6. +
                                            6. Permissions Management
                                              +
                                            7. Instance Lifecycle
                                            8. Instance Modifications
                                              @@ -20,6 +22,8 @@
                                            9. Connection Management
                                              10. +
                                            10. Database Proxy (Read/Write Splitting)
                                              +
                                            11. Data Security
                                            12. Metrics and Alarms
                                              diff --git a/docs/rds/umn/rds_08_0002.html b/docs/rds/umn/rds_08_0002.html index eee6f585..59f684f0 100644 --- a/docs/rds/umn/rds_08_0002.html +++ b/docs/rds/umn/rds_08_0002.html @@ -7,9 +7,9 @@
                                              • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
                                              • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
                                              • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
                                              • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
                                            -

                                            Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                            5. In the displayed dialog box, click Yes.
                                            6. Refresh the DB instance list later to confirm that the deletion was successful.
                                            +

                                            Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                            5. In the displayed dialog box, click Yes.
                                            6. Refresh the DB instance list later to confirm that the deletion was successful.
                                            -

                                            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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                            5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                            6. In the displayed dialog box, click Yes.
                                            7. Refresh the DB instance list later to check that the deletion is successful.
                                            +

                                            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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                            5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                            6. In the displayed dialog box, click Yes.
                                            7. Refresh the DB instance list later to check that the deletion is successful.
                                            diff --git a/docs/rds/umn/rds_08_0003.html b/docs/rds/umn/rds_08_0003.html index fa0ca2b9..a51d81dc 100644 --- a/docs/rds/umn/rds_08_0003.html +++ b/docs/rds/umn/rds_08_0003.html @@ -3,8 +3,8 @@

                                            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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                            6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information 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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                            6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
                                            diff --git a/docs/rds/umn/rds_08_0004.html b/docs/rds/umn/rds_08_0004.html index d03fcd01..3a45e013 100644 --- a/docs/rds/umn/rds_08_0004.html +++ b/docs/rds/umn/rds_08_0004.html @@ -9,7 +9,7 @@

                                            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, click Modify Backup Policy.

                                              • 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, click Modify Backup Policy.

                                                • 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.

                                              6. Click OK.
                                            diff --git a/docs/rds/umn/rds_08_0005.html b/docs/rds/umn/rds_08_0005.html index 8170652f..da6e9a80 100644 --- a/docs/rds/umn/rds_08_0005.html +++ b/docs/rds/umn/rds_08_0005.html @@ -8,11 +8,11 @@

                                            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.
                                            -

                                            Method 1

                                            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 > Create Backup in the Operation column.
                                            5. In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                              • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                              • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                              • The time required for creating a manual backup depends on the amount of data.
                                              +

                                              Method 1

                                              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 > Create Backup in the Operation column.
                                              5. In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                                • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                • The time required for creating a manual backup depends on the amount of data.

                                              6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                              -

                                              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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and description and click OK. If you want to cancel the backup creation task, click Cancel.

                                                • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                • The time required for creating a manual backup depends on the amount of data.
                                                +

                                                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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and description and click OK. If you want to cancel the backup creation task, click Cancel.

                                                  • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                  • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                  • The time required for creating a manual backup depends on the amount of data.

                                                6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                  Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                                diff --git a/docs/rds/umn/rds_08_0006.html b/docs/rds/umn/rds_08_0006.html index 824c2cba..c9920194 100644 --- a/docs/rds/umn/rds_08_0006.html +++ b/docs/rds/umn/rds_08_0006.html @@ -6,7 +6,7 @@

                                              Constraints

                                              • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
                                              -

                                              Method 1: Using OBS Browser+

                                              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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                +

                                                Method 1: Using OBS Browser+

                                                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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                  Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

                                                  1. Download OBS Browser+
                                                  2. Decompress and install OBS Browser+.
                                                  3. Log in to OBS Browser+.

                                                    For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

                                                  4. Disable certificate verification on OBS Browser+.

                                                    For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

                                                    The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, and then it must be enabled again after the backup is downloaded.

                                                    @@ -17,11 +17,11 @@
                                                  5. After the backup is downloaded, enable OBS Browser+ certificate verification.

                                                6. Follow the instructions provided in Restoring from Backup Files to a Self-Built MySQL Database to restore data locally as required.
                                                -

                                                Method 2: Using Current Browser

                                                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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                  Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                  +

                                                  Method 2: Using Current Browser

                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                  5. In the displayed dialog box, select Use Current Browser for Download Method and click OK.
                                                  6. Follow the instructions provided in Restoring from Backup Files to a Self-Built MySQL Database to restore data locally as required.
                                                  -

                                                  Method 3: Using Download URL

                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                    -

                                                  5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                    A valid URL for downloading the backup data is displayed.

                                                    +

                                                    Method 3: Using Download URL

                                                    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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                      Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                      +

                                                    5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                      A valid URL for downloading the backup data is displayed.

                                                      • You can use various download tools to download backup files.
                                                      • You can also run the following command to download backup files:

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

                                                        The parameters in the command are as follows:

                                                        FILE_NAME: indicates the new backup file name after the download is successful. 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.

                                                        diff --git a/docs/rds/umn/rds_08_0007.html b/docs/rds/umn/rds_08_0007.html index 3611ec31..3090263b 100644 --- a/docs/rds/umn/rds_08_0007.html +++ b/docs/rds/umn/rds_08_0007.html @@ -4,7 +4,7 @@

                                                        Scenarios

                                                        This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance level.

                                                        When you restore a DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.

                                                        -

                                                        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 Backup Management page, select the backup to be restored and click Restore in the Operation column.

                                                          Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                          +

                                                          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 Backup Management page, select the backup to be restored and click Restore in the Operation column.

                                                            Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                          5. Select a restoration method and click OK.

                                                            • Create New Instance

                                                              The Create New Instance page is displayed.

                                                              • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
                                                              • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                              • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
                                                            • Restore to Original
                                                              1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
                                                              2. Confirm the information and click OK.
                                                              diff --git a/docs/rds/umn/rds_08_0008.html b/docs/rds/umn/rds_08_0008.html index c7d16044..23260cdf 100644 --- a/docs/rds/umn/rds_08_0008.html +++ b/docs/rds/umn/rds_08_0008.html @@ -5,7 +5,7 @@

                                                              RDS for MySQL supports restoration to a new, the original, or an existing DB instance.

                                                              When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

                                                          -

                                                          Restoring 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.
                                                          5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                          6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

                                                            • Create New Instance

                                                              The Create New Instance page is displayed.

                                                              +

                                                              Restoring 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.
                                                              5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                              6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

                                                                • Create New Instance

                                                                  The Create New Instance page is displayed.

                                                                  • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
                                                                  • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
                                                                • Restore to Original
                                                                  1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
                                                                  2. Confirm the information and click OK.

                                                                  Restoring to the original DB instance will overwrite all existing data and the DB instance will be unavailable during the restoration process.

                                                                  diff --git a/docs/rds/umn/rds_08_0009.html b/docs/rds/umn/rds_08_0009.html index 60d2f6b8..ed5f47fb 100644 --- a/docs/rds/umn/rds_08_0009.html +++ b/docs/rds/umn/rds_08_0009.html @@ -7,7 +7,7 @@

                                                                  Backup Retention Policy

                                                                  • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
                                                                  • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
                                                                  • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
                                                                  -

                                                                  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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                    Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                    +

                                                                    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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                      Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                    5. In the displayed dialog box, enter a new backup name and description and click OK.

                                                                      • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                      • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=

                                                                    6. After the new backup has been created, you can view and manage it on the Backup Management page.
                                                                    diff --git a/docs/rds/umn/rds_08_0010.html b/docs/rds/umn/rds_08_0010.html index 633ae6de..a63db867 100644 --- a/docs/rds/umn/rds_08_0010.html +++ b/docs/rds/umn/rds_08_0010.html @@ -5,7 +5,7 @@

                                                                  Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

                                                                  -

                                                                  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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                    The following backups cannot be deleted:

                                                                    +

                                                                    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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                      The following backups cannot be deleted:

                                                                      • Automated backups
                                                                      • Backups that are being restored
                                                                      • Backups that are being replicated

                                                                    5. In the displayed dialog box, click Yes.
                                                                    diff --git a/docs/rds/umn/rds_08_0012.html b/docs/rds/umn/rds_08_0012.html index 10c4cd25..9b2bd6ed 100644 --- a/docs/rds/umn/rds_08_0012.html +++ b/docs/rds/umn/rds_08_0012.html @@ -4,10 +4,10 @@

                                                                    Scenarios

                                                                    You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

                                                                    You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

                                                                    -

                                                                    Comparing Instance Parameters with a Parameter Template

                                                                    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 displayed page, click Compare above the parameter list.
                                                                    6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                      • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                      • If their settings are the same, no data is displayed.
                                                                      +

                                                                      Comparing Instance Parameters with a Parameter Template

                                                                      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 displayed page, click Compare above the parameter list.
                                                                      6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                        • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                        • If their settings are the same, no data is displayed.

                                                                      -

                                                                      Comparing Parameter Templates

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                      5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                        • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                        • If their settings are the same, no data is displayed.
                                                                        +

                                                                        Comparing Parameter Templates

                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                        5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                          • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                          • If their settings are the same, no data is displayed.

                                                                      diff --git a/docs/rds/umn/rds_08_0013.html b/docs/rds/umn/rds_08_0013.html index 8b2540dd..dd3ce07f 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 Basic Information page. In the upper right corner, click Reboot.

                                                                      +

                                                                      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 Basic Information page. In the upper right corner, click Reboot.

                                                                        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_0014.html b/docs/rds/umn/rds_08_0014.html index ec78bfd3..0fe8e4b2 100644 --- a/docs/rds/umn/rds_08_0014.html +++ b/docs/rds/umn/rds_08_0014.html @@ -5,7 +5,7 @@

                                                                      After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

                                                                      Default parameter templates cannot be replicated, but you can create parameter templates based on the default 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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                      Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                      +

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                        Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                      5. In the displayed dialog box, configure required information and click OK.

                                                                        • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                        After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

                                                                      diff --git a/docs/rds/umn/rds_08_0015.html b/docs/rds/umn/rds_08_0015.html index 7b612083..7c73ebc1 100644 --- a/docs/rds/umn/rds_08_0015.html +++ b/docs/rds/umn/rds_08_0015.html @@ -3,7 +3,7 @@

                                                                      Resetting a Parameter Template

                                                                      Scenarios

                                                                      You can reset all parameters in a custom parameter template to their default settings.

                                                                      -

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                      5. Click Yes.
                                                                      6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                      7. View the status of the DB instance to which the parameter template is applied.

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

                                                                        +

                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                        5. Click Yes.
                                                                        6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                        7. View the status of the DB instance to which the parameter template is applied.

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

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

                                                                        diff --git a/docs/rds/umn/rds_08_0016.html b/docs/rds/umn/rds_08_0016.html index 4818d5f1..157ff599 100644 --- a/docs/rds/umn/rds_08_0016.html +++ b/docs/rds/umn/rds_08_0016.html @@ -5,7 +5,7 @@

                                                                        You cannot modify the description of a default parameter template.

                                                                      -

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                      5. Enter a new description. You can click to submit or to cancel the modification.

                                                                        • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                        • After the modification is successful, you can view the new description in the Description column of the parameter template list.
                                                                        +

                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                        5. Enter a new description. You can click to submit or to cancel the modification.

                                                                          • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                          • After the modification is successful, you can view the new description in the Description column of the parameter template list.

                                                                      diff --git a/docs/rds/umn/rds_08_0017.html b/docs/rds/umn/rds_08_0017.html index 1c2b51be..c1b5411d 100644 --- a/docs/rds/umn/rds_08_0017.html +++ b/docs/rds/umn/rds_08_0017.html @@ -5,7 +5,7 @@
                                                                      • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
                                                                      • Default parameter templates cannot be deleted.
                                                                      -

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                      5. In the displayed dialog box, click Yes.
                                                                      +

                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                      5. In the displayed dialog box, click Yes.
                                                                      diff --git a/docs/rds/umn/rds_08_0022.html b/docs/rds/umn/rds_08_0022.html index 2cc8766e..36be0561 100644 --- a/docs/rds/umn/rds_08_0022.html +++ b/docs/rds/umn/rds_08_0022.html @@ -3,7 +3,7 @@

                                                                      Selecting Displayed Items

                                                                      Scenarios

                                                                      You can customize which instance items are displayed on the Instances 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 to edit columns displayed in the DB instance list.

                                                                        • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                          These default items cannot be deselected.

                                                                          +

                                                                          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 to edit columns displayed in the DB instance list.

                                                                            • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                              These default items cannot be deselected.

                                                                            • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.

                                                                          diff --git a/docs/rds/umn/rds_08_0042.html b/docs/rds/umn/rds_08_0042.html index 399608fc..19141f95 100644 --- a/docs/rds/umn/rds_08_0042.html +++ b/docs/rds/umn/rds_08_0042.html @@ -3,7 +3,7 @@

                                                                          Exporting a Parameter Template

                                                                          Scenarios

                                                                          • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
                                                                          • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
                                                                          -

                                                                          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.
                                                                          5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                            • Exporting to a custom template
                                                                              In the displayed dialog box, configure required information and click OK.
                                                                              • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                              • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                              +

                                                                              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.
                                                                              5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                                • Exporting to a custom template
                                                                                  In the displayed dialog box, configure required information and click OK.
                                                                                  • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                  • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                  After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

                                                                                  diff --git a/docs/rds/umn/rds_08_0044.html b/docs/rds/umn/rds_08_0044.html index 6ee6febf..29f1ccc9 100644 --- a/docs/rds/umn/rds_08_0044.html +++ b/docs/rds/umn/rds_08_0044.html @@ -39,7 +39,7 @@

                                                                            • Log in to the database and view the restoration result.

                                                                              mysql -u -root

                                                                              show databases

                                                                              -
                                                                              Figure 1 Viewing the restoration result
                                                                              +
                                                                              Figure 1 Viewing the restoration result

                                                                          diff --git a/docs/rds/umn/rds_09_0000.html b/docs/rds/umn/rds_09_0000.html index 4d7a68b9..b6f861ce 100644 --- a/docs/rds/umn/rds_09_0000.html +++ b/docs/rds/umn/rds_09_0000.html @@ -8,7 +8,7 @@
                                                                        • Parameter Tuning
                                                                          • -
                                                                        • PostgreSQL Enhanced Edition
                                                                          +
                                                                        • Permissions Management
                                                                        • Instance Lifecycle
                                                                          • diff --git a/docs/rds/umn/rds_09_0024.html b/docs/rds/umn/rds_09_0024.html index f5621601..2e959e95 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 Basic Information page. In the upper right corner, click Reboot.

                                                                        +

                                                                        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 Basic Information page. In the upper right corner, click Reboot.

                                                                          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_0025.html b/docs/rds/umn/rds_09_0025.html index 3495928b..6edc59e9 100644 --- a/docs/rds/umn/rds_09_0025.html +++ b/docs/rds/umn/rds_09_0025.html @@ -7,9 +7,9 @@
                                                                        • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
                                                                        • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
                                                                        • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
                                                                        • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
                                                                      -

                                                                      Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                                                      5. In the displayed dialog box, click Yes.
                                                                      6. Refresh the DB instance list later to confirm that the deletion was successful.
                                                                      +

                                                                      Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                                                      5. In the displayed dialog box, click Yes.
                                                                      6. Refresh the DB instance list later to confirm that the deletion was successful.
                                                                      -

                                                                      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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                                                      5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                                                      6. In the displayed dialog box, click Yes.
                                                                      7. Refresh the DB instance list later to check that the deletion is successful.
                                                                      +

                                                                      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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                                                      5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                                                      6. In the displayed dialog box, click Yes.
                                                                      7. Refresh the DB instance list later to check that the deletion is successful.
                                                                      diff --git a/docs/rds/umn/rds_09_0026.html b/docs/rds/umn/rds_09_0026.html index e63f1d6b..77edcc68 100644 --- a/docs/rds/umn/rds_09_0026.html +++ b/docs/rds/umn/rds_09_0026.html @@ -3,8 +3,8 @@

                                                                      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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                                                      6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information 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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                                                      6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
                                                                      diff --git a/docs/rds/umn/rds_09_0027.html b/docs/rds/umn/rds_09_0027.html index 879bbf21..477d5db1 100644 --- a/docs/rds/umn/rds_09_0027.html +++ b/docs/rds/umn/rds_09_0027.html @@ -6,7 +6,7 @@
                                                                      The automated backup policy is enabled by default as follows:
                                                                      • Retention period: 7 days. Backup files that exceed the retention period will be deleted and cannot be restored.
                                                                      • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
                                                                      • Backup cycle: Each day of the week
                                                                      -

                                                                      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, click Modify Backup Policy.

                                                                        • 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. The backup files that have expired will be deleted.
                                                                        • The backup retention period is the number of days you want automated full and incremental 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, click Modify Backup Policy.

                                                                          • 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. The backup files that have expired will be deleted.
                                                                          • The backup retention period is the number of days you want automated full and incremental 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.

                                                                        6. Click OK.
                                                                      diff --git a/docs/rds/umn/rds_09_0028.html b/docs/rds/umn/rds_09_0028.html index afce421b..2baaaba6 100644 --- a/docs/rds/umn/rds_09_0028.html +++ b/docs/rds/umn/rds_09_0028.html @@ -5,11 +5,11 @@

                                                                      When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

                                                                      -

                                                                      Method 1

                                                                      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 > Create Backup in the Operation column.
                                                                      5. In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                                                        • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                        • The time required for creating a manual backup depends on the amount of data.
                                                                        +

                                                                        Method 1

                                                                        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 > Create Backup in the Operation column.
                                                                        5. In the displayed dialog box, enter a backup name and description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                                                          • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                          • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                          • The time required for creating a manual backup depends on the amount of data.

                                                                        6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                                          Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                                                        -

                                                                        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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and description and click OK. If you want to cancel the backup creation task, click Cancel.

                                                                          • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                          • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                          • The time required for creating a manual backup depends on the amount of data.
                                                                          +

                                                                          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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name and description and click OK. If you want to cancel the backup creation task, click Cancel.

                                                                            • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                            • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                            • The time required for creating a manual backup depends on the amount of data.

                                                                          6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                                            Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                                                          diff --git a/docs/rds/umn/rds_09_0029.html b/docs/rds/umn/rds_09_0029.html index 7a43ef05..1a298b28 100644 --- a/docs/rds/umn/rds_09_0029.html +++ b/docs/rds/umn/rds_09_0029.html @@ -5,7 +5,7 @@

                                                                          RDS for PostgreSQL supports restoration to a new, the original, or an existing DB instance.

                                                                          When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

                                                                        -

                                                                        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.
                                                                        5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                                        6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

                                                                          • Create New Instance
                                                                            The Create New Instance page is displayed.
                                                                            • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
                                                                            • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                                            • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Step 1: Create a 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.
                                                                            5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                                            6. Select the restoration date and time range, enter a time point within the selected time range, and select a restoration method. Then, click OK.

                                                                              • Create New Instance
                                                                                The Create New Instance page is displayed.
                                                                                • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
                                                                                • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                                                • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Step 1: Create a DB Instance.
                                                                              • Restore to Original
                                                                                1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
                                                                                2. Confirm the information and click OK.
                                                                                diff --git a/docs/rds/umn/rds_09_0030.html b/docs/rds/umn/rds_09_0030.html index 2856d6b7..a8bce12b 100644 --- a/docs/rds/umn/rds_09_0030.html +++ b/docs/rds/umn/rds_09_0030.html @@ -3,7 +3,7 @@

                                                                                Restoring from Backup Files to RDS for PostgreSQL

                                                                                Scenarios

                                                                                This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created. The restoration is at the DB instance level.

                                                                                -

                                                                                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 Backup Management page, select the backup to be restored and click Restore in the Operation column.

                                                                                  Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                                                  +

                                                                                  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 Backup Management page, select the backup to be restored and click Restore in the Operation column.

                                                                                    Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                                                  5. Select a restoration method and click OK.

                                                                                    • Create New Instance
                                                                                      The Create New Instance page is displayed.
                                                                                      • The DB engine and version of the new DB instance are the same as those of the original DB instance and cannot be changed.
                                                                                      • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                                                      • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
                                                                                    • Restore to Original
                                                                                      1. Select "I acknowledge that after I select Restore to Original, data on the original databases will be overwritten and the original DB instance will be unavailable during the restoration." and click Next.
                                                                                      2. Confirm the information and click OK.
                                                                                      diff --git a/docs/rds/umn/rds_09_0031.html b/docs/rds/umn/rds_09_0031.html index f72a77fb..64f96316 100644 --- a/docs/rds/umn/rds_09_0031.html +++ b/docs/rds/umn/rds_09_0031.html @@ -6,7 +6,7 @@

                                                                                  Constraints

                                                                                  • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
                                                                                  -

                                                                                  Method 1: Using OBS Browser+

                                                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    +

                                                                                    Method 1: Using OBS Browser+

                                                                                    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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                      Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

                                                                                      1. Download OBS Browser+
                                                                                      2. Decompress and install OBS Browser+.
                                                                                      3. Log in to OBS Browser+.

                                                                                        For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

                                                                                      4. Disable certificate verification on OBS Browser+.

                                                                                        For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

                                                                                        The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, and then it must be enabled again after the backup is downloaded.

                                                                                        @@ -15,19 +15,19 @@

                                                                                        For details about how to add external buckets, see Adding External Buckets in the OBS Browser+ Operation Guide.

                                                                                      5. Download the backup file.

                                                                                        On the OBS Browser+ page, click the bucket that you added. In the search box on the right of OBS Browser+, enter the backup file name provided in step 3 "Download the Backup File" of the RDS console. In the search result, locate the target backup and download it.

                                                                                      6. After the backup is downloaded, enable OBS Browser+ certificate verification.
                                                                                      -

                                                                                    6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
                                                                                    +

                                                                                  5. Restore data locally as required.
                                                                                  -

                                                                                  Method 2: Using Current Browser

                                                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    -

                                                                                  5. In the displayed dialog box, select Use Current Browser for Download Method and click OK.
                                                                                  6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
                                                                                  +

                                                                                  Method 2: Using Current Browser

                                                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    +

                                                                                  5. In the displayed dialog box, select Use Current Browser for Download Method and click OK.
                                                                                  6. Restore data locally as required.
                                                                                  -

                                                                                  Method 3: Using Download URL

                                                                                  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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                    -

                                                                                  5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                                                    A valid URL for downloading the backup data is displayed.

                                                                                    +

                                                                                    Method 3: Using Download URL

                                                                                    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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                      Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the Full Backups page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                      +

                                                                                    5. In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                                                      A valid URL for downloading the backup data is displayed.

                                                                                      • You can use various download tools to download backup files.
                                                                                      • You can also run the following command to download backup files:

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

                                                                                        The parameters in the command are as follows:

                                                                                        FILE_NAME: indicates the new backup file name after the download is successful. 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 backup file to be downloaded. If the location contains special characters, escape is required.

                                                                                      -

                                                                                    6. Restore data locally as required. For details, see Restoring from Full Backup Files to a Self-Built PostgreSQL Database.
                                                                                    +

                                                                                  6. Restore data locally as required.
                                                                                  diff --git a/docs/rds/umn/rds_09_0032.html b/docs/rds/umn/rds_09_0032.html index 13e93ba7..61cb029f 100644 --- a/docs/rds/umn/rds_09_0032.html +++ b/docs/rds/umn/rds_09_0032.html @@ -7,7 +7,7 @@

                                                                                  Backup Retention Policy

                                                                                  • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
                                                                                  • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
                                                                                  • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
                                                                                  -

                                                                                  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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                                    Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                                    +

                                                                                    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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                                      Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                                    5. In the displayed dialog box, enter a new backup name and description and click OK.

                                                                                      • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                      • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=

                                                                                    6. After the new backup has been created, you can view and manage it on the Backup Management page.
                                                                                    diff --git a/docs/rds/umn/rds_09_0033.html b/docs/rds/umn/rds_09_0033.html index 69985d8b..821dacf4 100644 --- a/docs/rds/umn/rds_09_0033.html +++ b/docs/rds/umn/rds_09_0033.html @@ -5,7 +5,7 @@

                                                                                  Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

                                                                                  -

                                                                                  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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                                    The following backups cannot be deleted:

                                                                                    +

                                                                                    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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                                      The following backups cannot be deleted:

                                                                                      • Automated backups
                                                                                      • Backups that are being restored
                                                                                      • Backups that are being replicated

                                                                                    5. In the displayed dialog box, click Yes.
                                                                                    diff --git a/docs/rds/umn/rds_09_0035.html b/docs/rds/umn/rds_09_0035.html index 91c411d4..e6facb52 100644 --- a/docs/rds/umn/rds_09_0035.html +++ b/docs/rds/umn/rds_09_0035.html @@ -4,10 +4,10 @@

                                                                                    Scenarios

                                                                                    You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

                                                                                    You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

                                                                                    -

                                                                                    Comparing Instance Parameters with a Parameter Template

                                                                                    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 displayed page, click Compare above the parameter list.
                                                                                    6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                                      • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                      • If their settings are the same, no data is displayed.
                                                                                      +

                                                                                      Comparing Instance Parameters with a Parameter Template

                                                                                      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 displayed page, click Compare above the parameter list.
                                                                                      6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                                        • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                        • If their settings are the same, no data is displayed.

                                                                                      -

                                                                                      Comparing Parameter Templates

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                                      5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                                        • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                        • If their settings are the same, no data is displayed.
                                                                                        +

                                                                                        Comparing Parameter Templates

                                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                                        5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                                          • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                          • If their settings are the same, no data is displayed.

                                                                                      diff --git a/docs/rds/umn/rds_09_0036.html b/docs/rds/umn/rds_09_0036.html index a4ac767e..5ebbb7fc 100644 --- a/docs/rds/umn/rds_09_0036.html +++ b/docs/rds/umn/rds_09_0036.html @@ -5,7 +5,7 @@

                                                                                      After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

                                                                                      Default parameter templates cannot be replicated, but you can create parameter templates based on the default 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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                                      Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                                      +

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                                        Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                                      5. In the displayed dialog box, configure required information and click OK.

                                                                                        • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                        After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

                                                                                      diff --git a/docs/rds/umn/rds_09_0037.html b/docs/rds/umn/rds_09_0037.html index e322ba62..6fb0b6f9 100644 --- a/docs/rds/umn/rds_09_0037.html +++ b/docs/rds/umn/rds_09_0037.html @@ -3,7 +3,7 @@

                                                                                      Resetting a Parameter Template

                                                                                      Scenarios

                                                                                      You can reset all parameters in a custom parameter template to their default settings.

                                                                                      -

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                                      5. Click Yes.
                                                                                      6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                                      7. View the status of the DB instance to which the parameter template is applied.

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

                                                                                        +

                                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                                        5. Click Yes.
                                                                                        6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                                        7. View the status of the DB instance to which the parameter template is applied.

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

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

                                                                                        diff --git a/docs/rds/umn/rds_09_0038.html b/docs/rds/umn/rds_09_0038.html index a865566d..b7925f06 100644 --- a/docs/rds/umn/rds_09_0038.html +++ b/docs/rds/umn/rds_09_0038.html @@ -5,7 +5,7 @@

                                                                                        You cannot modify the description of a default parameter template.

                                                                                      -

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                                      5. Enter a new description. You can click to submit or to cancel the modification.

                                                                                        • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                                        • After the modification is successful, you can view the new description in the Description column of the parameter template list.
                                                                                        +

                                                                                        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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                                        5. Enter a new description. You can click to submit or to cancel the modification.

                                                                                          • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                                          • After the modification is successful, you can view the new description in the Description column of the parameter template list.

                                                                                      diff --git a/docs/rds/umn/rds_09_0039.html b/docs/rds/umn/rds_09_0039.html index dccada06..1c0adb49 100644 --- a/docs/rds/umn/rds_09_0039.html +++ b/docs/rds/umn/rds_09_0039.html @@ -5,7 +5,7 @@
                                                                                      • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
                                                                                      • Default parameter templates cannot be deleted.
                                                                                      -

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                                      5. In the displayed dialog box, click Yes.
                                                                                      +

                                                                                      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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                                      5. In the displayed dialog box, click Yes.
                                                                                      diff --git a/docs/rds/umn/rds_09_0043.html b/docs/rds/umn/rds_09_0043.html index c19f908b..a98bd43b 100644 --- a/docs/rds/umn/rds_09_0043.html +++ b/docs/rds/umn/rds_09_0043.html @@ -4,7 +4,7 @@

                                                                                      RDS provides the PostgreSQL plugin management solution for user root. Except the following plugins, you need to manually create other plugins by referring to this section.

                                                                                      • auto_explain
                                                                                      • passwordcheck
                                                                                      • pg_profile_pro
                                                                                      • pg_sql_history
                                                                                      • wal2json
                                                                                      • test_decoding

                                                                                      The PostgreSQL plugin takes effect at the database level, not globally. You need to manually create it on corresponding databases.

                                                                                      -

                                                                                      The latest minor versions of PostgreSQL 11, 12, 13, and Enhanced Edition allow the root user to create plugins (create extension) or delete plugins (drop extension).

                                                                                      +

                                                                                      The latest minor versions of PostgreSQL 11, 12, 13, and 14 allow the root user to create plugins (create extension) or delete plugins (drop extension).

                                                                                      Creating a Plugin

                                                                                      1. Connect to the database database1 as user root and use template1 to create a database that can support the plugin.

                                                                                        # psql --host=<RDS_ADDRESS> --port=<DB_PORT> --dbname=database1 --username=root -c "create database <DB_NAME> template template1;"

                                                                                        • RDS_ADDRESS indicates the IP address of the RDS DB instance.
                                                                                        • DB_PORT indicates the RDS DB instance port.
                                                                                        • DB_NAME indicates the name of the database to be created.
                                                                                        diff --git a/docs/rds/umn/rds_09_0045.html b/docs/rds/umn/rds_09_0045.html index 382e0313..2da4654c 100644 --- a/docs/rds/umn/rds_09_0045.html +++ b/docs/rds/umn/rds_09_0045.html @@ -5,758 +5,758 @@

                                                                                        Before using the mysql_fdw, oracle_fdw, pgsql-ogr-fdw, postgres_fdw, and tds_fdw plugins, ensure that the server IP addresses of the two PostgreSQL DB instances are in the same VPC and subnet.

                                                                                      -
                                                                                      Table 1 Supported plugins

                                                                                      Plugin Name

                                                                                      +
                                                                                      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -768,7 +768,7 @@

                                                                                      postgis_tiger_geocoder

                                                                                      address_standardizer

                                                                                      address_standardizer_data_us

                                                                                      -
                                                                                    5. After the postgis plugin is created on the primary DB instance, you need to disconnect the connection from the standby DB instance first and re-establish a connection to update the search_path setting.
                                                                                    6. For PostgreSQL Enhanced Edition DB instances, you need to set empty_is_null to OFF on the console before creating the postgis plugin.
                                                                                      7. +
                                                                                    7. After the postgis plugin is created on the primary DB instance, you need to disconnect the connection from the standby DB instance first and re-establish a connection to update the search_path setting.
                                                                                    8. earthdistance

                                                                                      To install the earthdistance plugin, you must install the cube plugin first.

                                                                                    9. cube

                                                                                      If the earthdistance plugin has been installed, deleting the cube plugin will cause the earthdistance plugin to be unavailable.

                                                                                    10. timescaledb

                                                                                      The timescaledb plugin does not support the TSL protocol. For more information, see APIs Not Supported by the timescaledb Plugin.

                                                                                      diff --git a/docs/rds/umn/rds_10_0000.html b/docs/rds/umn/rds_10_0000.html index c8a2928b..936891f6 100644 --- a/docs/rds/umn/rds_10_0000.html +++ b/docs/rds/umn/rds_10_0000.html @@ -6,6 +6,8 @@
                                                                                      • Data Migration
                                                                                        • +
                                                                                      • Permissions Management
                                                                                        +
                                                                                      • Instance Lifecycle
                                                                                      • Instance Modifications
                                                                                        diff --git a/docs/rds/umn/rds_10_0035.html b/docs/rds/umn/rds_10_0035.html index ad5dc903..123daabe 100644 --- a/docs/rds/umn/rds_10_0035.html +++ b/docs/rds/umn/rds_10_0035.html @@ -50,7 +50,7 @@ Enter password: 
                                                                                        C:\test>bcp test.dbo.t1 in c:\test\t1.txt -n -S "10.65.60.79,8636" -U rdsuser -b 2000
 Enter password:

                                                                                      • Check the data import result.

                                                                                        select * from sys.databases;
                                                                                        -
                                                                                        Figure 1 Data import result
                                                                                        +
                                                                                        Figure 1 Data import result

                                                                                        • diff --git a/docs/rds/umn/rds_10_0055.html b/docs/rds/umn/rds_10_0055.html index a4d177b6..7e9e3e81 100644 --- a/docs/rds/umn/rds_10_0055.html +++ b/docs/rds/umn/rds_10_0055.html @@ -7,7 +7,7 @@

                                                                                        Backup Retention Policy

                                                                                        • RDS will delete automated backups when they expire or the DB instance for which the backups are created is deleted.
                                                                                        • If you want to retain the automated backups for a long time, you can replicate them to generate manual backups, which will be always retained until you delete them.
                                                                                        • If the storage occupied by manual backups exceeds the provisioned free backup storage, additional storage costs may incur.
                                                                                        -

                                                                                        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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                                          Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                                          +

                                                                                          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. On the Backups & Restorations page, locate the target backup to be replicated and click Replicate in the Operation column.

                                                                                            Alternatively, choose Backup Management. On the displayed page, locate the manual backup to be replicated and choose More > Replicate or locate an automated backup and click Replicate in the Operation column.

                                                                                          5. In the displayed dialog box, enter a new backup name and description and click OK.

                                                                                            • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                            • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=

                                                                                          6. After the new backup has been created, you can view and manage it on the Backup Management page.
                                                                                          diff --git a/docs/rds/umn/rds_10_0101.html b/docs/rds/umn/rds_10_0101.html index 797145a1..ec365f64 100644 --- a/docs/rds/umn/rds_10_0101.html +++ b/docs/rds/umn/rds_10_0101.html @@ -5,7 +5,7 @@

                                                                                        Deleted manual backups cannot be recovered. Exercise caution when performing this operation.

                                                                                        -

                                                                                        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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                                          The following backups cannot be deleted:

                                                                                          +

                                                                                          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. In the navigation pane on the left, choose Backup Management. On the displayed page, locate the target manual backup to be deleted and choose More > Delete in the Operation column.

                                                                                            The following backups cannot be deleted:

                                                                                            • Automated backups
                                                                                            • Backups that are being restored
                                                                                            • Backups that are being replicated

                                                                                          5. In the displayed dialog box, click Yes.
                                                                                          diff --git a/docs/rds/umn/rds_10_0103.html b/docs/rds/umn/rds_10_0103.html index f503664e..e386f9b7 100644 --- a/docs/rds/umn/rds_10_0103.html +++ b/docs/rds/umn/rds_10_0103.html @@ -4,10 +4,10 @@

                                                                                          Scenarios

                                                                                          You can compare DB instance parameters with a parameter template that uses the same DB engine to understand the differences of parameter settings.

                                                                                          You can also compare default parameter templates that use the same DB engine to understand the differences of parameter settings.

                                                                                          -

                                                                                          Comparing Instance Parameters with a Parameter Template

                                                                                          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 displayed page, click Compare above the parameter list.
                                                                                          6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                                            • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                            • If their settings are the same, no data is displayed.
                                                                                            +

                                                                                            Comparing Instance Parameters with a Parameter Template

                                                                                            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 displayed page, click Compare above the parameter list.
                                                                                            6. In the displayed dialog box, select a parameter template to be compared and click OK.

                                                                                              • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                              • If their settings are the same, no data is displayed.

                                                                                            -

                                                                                            Comparing Parameter Templates

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                                            5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                                              • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                              • If their settings are the same, no data is displayed.
                                                                                              +

                                                                                              Comparing Parameter Templates

                                                                                              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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Compare in the Operation column.
                                                                                              5. In the displayed dialog box, select a parameter template that uses the same DB engine as the target template and click OK.

                                                                                                • If their settings are different, the parameter names and values of both parameter templates are displayed.
                                                                                                • If their settings are the same, no data is displayed.

                                                                                            diff --git a/docs/rds/umn/rds_10_0104.html b/docs/rds/umn/rds_10_0104.html index 9e9f2ccd..fda2101a 100644 --- a/docs/rds/umn/rds_10_0104.html +++ b/docs/rds/umn/rds_10_0104.html @@ -5,7 +5,7 @@

                                                                                            After a parameter template is replicated, it takes about 5 minutes before the new template is displayed.

                                                                                            Default parameter templates cannot be replicated, but you can create parameter templates based on the default 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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                                            Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                                            +

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click Replicate in the Operation column.

                                                                                              Alternatively, click the target DB instance on the Instances page. On the Parameters page, click Export to generate a new parameter template for future use.

                                                                                            5. In the displayed dialog box, configure required information and click OK.

                                                                                              • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                              • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                              After the parameter template is replicated, a new template is generated in the list on the Parameter Template Management page.

                                                                                            diff --git a/docs/rds/umn/rds_10_0105.html b/docs/rds/umn/rds_10_0105.html index c0695986..1c3c3ba6 100644 --- a/docs/rds/umn/rds_10_0105.html +++ b/docs/rds/umn/rds_10_0105.html @@ -3,7 +3,7 @@

                                                                                            Resetting a Parameter Template

                                                                                            Scenarios

                                                                                            You can reset all parameters in a custom parameter template to their default settings.

                                                                                            -

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                                            5. Click Yes.
                                                                                            6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                                            7. View the status of the DB instance to which the parameter template is applied.

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

                                                                                              +

                                                                                              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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and choose More > Reset in the Operation column.
                                                                                              5. Click Yes.
                                                                                              6. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                                              7. View the status of the DB instance to which the parameter template is applied.

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

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

                                                                                              diff --git a/docs/rds/umn/rds_10_0106.html b/docs/rds/umn/rds_10_0106.html index 3e8fbc2a..0d75056c 100644 --- a/docs/rds/umn/rds_10_0106.html +++ b/docs/rds/umn/rds_10_0106.html @@ -5,7 +5,7 @@

                                                                                              You cannot modify the description of a default parameter template.

                                                                                            -

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                                            5. Enter a new description. You can click to submit or to cancel the modification.

                                                                                              • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                                              • After the modification is successful, you can view the new description in the Description column of the parameter template list.
                                                                                              +

                                                                                              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 Parameter Template Management page, click Custom Templates. Locate the target parameter template and click in the Description column.
                                                                                              5. Enter a new description. You can click to submit or to cancel the modification.

                                                                                                • The description consists of a maximum of 256 characters and cannot contain the following special characters: >!<"&'=
                                                                                                • After the modification is successful, you can view the new description in the Description column of the parameter template list.

                                                                                            diff --git a/docs/rds/umn/rds_10_0107.html b/docs/rds/umn/rds_10_0107.html index 270d7f33..2184a46c 100644 --- a/docs/rds/umn/rds_10_0107.html +++ b/docs/rds/umn/rds_10_0107.html @@ -5,7 +5,7 @@
                                                                                            • Deleted parameter templates cannot be recovered. Exercise caution when performing this operation.
                                                                                            • Default parameter templates cannot be deleted.
                                                                                            -

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                                            5. In the displayed dialog box, click Yes.
                                                                                            +

                                                                                            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 Parameter Template Management page, click Custom Templates. Locate the target parameter template to be deleted and choose More > Delete in the Operation column.
                                                                                            5. In the displayed dialog box, click Yes.
                                                                                            diff --git a/docs/rds/umn/rds_11_0004.html b/docs/rds/umn/rds_11_0004.html index cddfdf8e..ca5943f3 100644 --- a/docs/rds/umn/rds_11_0004.html +++ b/docs/rds/umn/rds_11_0004.html @@ -13,17 +13,17 @@
                                                                                      11. - - @@ -33,7 +33,7 @@
                                                                                    11. Enabling TDE improves data security but affects read and write performance of encrypted databases. Exercise caution when enabling TDE.
                                                                                    12. To migrate on-premises encrypted databases to RDS SQL Server DB instances, you need to disable database-level TDE first.
                                                                                    13. DB instances with the instance-level TDE function enabled cannot be restored from backups to existing DB instances.
                                                                                    14. When enabling the instance-level TDE function or using the stored procedure rds_tde to enable or disable database-level TDE, you are advised not to perform the following operations:
                                                                                      • Delete files from file groups in databases.
                                                                                      • Delete databases.
                                                                                      • Take databases offline
                                                                                      • Split databases.
                                                                                      • Convert databases or file groups to the READ ONLY state.
                                                                                      • Run the ALTER DATABASE command.
                                                                                      • Create backups.
                                                                                      • Start backup for databases or database files.
                                                                                      • Start restoration for databases or database files.
                                                                                      15. -

                                                                                      Enabling Instance-Level TDE

                                                                                      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 DB Information area, click in the TDE field to enable TDE.
                                                                                      +

                                                                                      Enabling Instance-Level TDE

                                                                                      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 DB Information area, click in the TDE field to enable TDE.

                                                                                      Configuring Database-Level TDE

                                                                                      Before enabling the database-level TDE function, ensure that the instance-level TDE function has been enabled.

                                                                                      @@ -42,14 +42,14 @@
                                                                                    15. The value 0 indicates that the TDE function is disabled.
                                                                                    16. The value 1 indicates that the TDE function is enabled.
                                                                                      1. Enable TDE for database db1.

                                                                                        exec master.dbo.rds_tde db1, 1

                                                                                        -
                                                                                        Figure 1 Enabling TDE
                                                                                        +
                                                                                        Figure 1 Enabling TDE
                                                                                      2. Disable TDE for database db1.

                                                                                        exec master.dbo.rds_tde db1, 0

                                                                                        -
                                                                                        Figure 2 Disabling TDE
                                                                                        +
                                                                                        Figure 2 Disabling TDE
                                                                                      3. Query the TDE status of database db1.

                                                                                        exec master.dbo.rds_tde db1, -1

                                                                                        -
                                                                                        Figure 3 Querying the TDE status (Enabled)
                                                                                        -
                                                                                        Figure 4 Querying the TDE status (Disabled)
                                                                                        +
                                                                                        Figure 3 Querying the TDE status (Enabled)
                                                                                        +
                                                                                        Figure 4 Querying the TDE status (Disabled)
                                                                                      4. Query the TDE status of all databases.

                                                                                        exec master.dbo.rds_tde null, -1

                                                                                        -
                                                                                        Figure 5 Querying the TDE status of all databases
                                                                                        +
                                                                                        Figure 5 Querying the TDE status of all databases

                                                                                      diff --git a/docs/rds/umn/rds_11_0006.html b/docs/rds/umn/rds_11_0006.html index 79164d0e..fc83dda5 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 Basic Information page. In the upper right corner, click Reboot.

                                                                                        +

                                                                                        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 Basic Information page. In the upper right corner, click Reboot.

                                                                                          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_0010.html b/docs/rds/umn/rds_11_0010.html index faec522b..55e4adc3 100644 --- a/docs/rds/umn/rds_11_0010.html +++ b/docs/rds/umn/rds_11_0010.html @@ -5,13 +5,13 @@

                                                                                        When you delete a DB instance, its automated backups are also deleted but its manual backups are retained.

                                                                                      -

                                                                                      Method 1

                                                                                      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 > Create Backup in the Operation column.
                                                                                      5. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                                                                        • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                        • The time required for creating a manual backup depends on the amount of data.
                                                                                        +

                                                                                        Method 1

                                                                                        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 > Create Backup in the Operation column.
                                                                                        5. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a description. Then, click OK. If you want to cancel the backup creation task, click Cancel.

                                                                                          • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                          • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                          • The time required for creating a manual backup depends on the amount of data.

                                                                                          System databases are backed up by default.

                                                                                        6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                                                          Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                                                                        -

                                                                                        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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a description. Then, click OK.

                                                                                          • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                          • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                          • The time required for creating a manual backup depends on the amount of data.
                                                                                          +

                                                                                          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 Backups & Restorations page, click Create Backup. In the displayed dialog box, enter a backup name, select a target database for which to create the backup, and enter a description. Then, click OK.

                                                                                            • The backup name must consist of 4 to 64 characters and start with a letter. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
                                                                                            • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                            • The time required for creating a manual backup depends on the amount of data.

                                                                                            System databases are backed up by default.

                                                                                          6. After a manual backup has been created, you can view and manage it on the Backup Management page.

                                                                                            Alternatively, click the target DB instance. On the Backups & Restorations page, you can view and manage the manual backups.

                                                                                            diff --git a/docs/rds/umn/rds_11_0013.html b/docs/rds/umn/rds_11_0013.html index 850c30f1..3faf30bc 100644 --- a/docs/rds/umn/rds_11_0013.html +++ b/docs/rds/umn/rds_11_0013.html @@ -5,7 +5,7 @@

                                                                                          Constraints

                                                                                          • If the size of the backup data is greater than 400 MB, you are advised to use OBS Browser+ to download the backup data.
                                                                                          -

                                                                                          Method 1: Using OBS Browser+

                                                                                          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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                            Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                            +

                                                                                            Method 1: Using OBS Browser+

                                                                                            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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                              Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                            5. In the displayed dialog box, select Use OBS Browser+ for Download Method and click OK.

                                                                                              1. Download OBS Browser+
                                                                                              2. Decompress and install OBS Browser+.
                                                                                              3. Log in to OBS Browser+.

                                                                                                For details about how to log in to OBS Browser+, see Logging In to OBS Browser+ in the OBS Browser+ Operation Guide.

                                                                                              4. Disable certificate verification on OBS Browser+.

                                                                                                For details on how to configure OBS Browser+, see Configuring the System in the OBS Browser+ Operation Guide.

                                                                                                The OBS bucket name displayed in the Download Backup File pane on the RDS console does not support certificate verification. OBS Browser+ certificate verification needs to be disabled before the external bucket can be added, then it must be enabled again after the backup is downloaded.

                                                                                                @@ -17,8 +17,8 @@
                                                                                              5. After the backup is downloaded, enable OBS Browser+ certificate verification.

                                                                                            6. Follow the instructions provided in Restoring from Backup Files to a Self-Built SQL Server Database to restore data locally as required.
                                                                                            -

                                                                                            Method 2: Using Download URL

                                                                                            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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                              Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                              -

                                                                                            5. In the displayed dialog box, select a method to download backup data.

                                                                                              In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                                                              +

                                                                                              Method 2: Using Download URL

                                                                                              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 Backup Management page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                                Alternatively, click the target DB instance. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, locate the target backup to be downloaded and click Download in the Operation column.

                                                                                                +

                                                                                              5. In the displayed dialog box, select a method to download backup data.

                                                                                                In the displayed dialog box, select Use Download URL for Download Method, click to copy the URL, and click OK.

                                                                                                For Microsoft SQL Server DB instances, the URLs of all the backup files are displayed. You can download the backup files of a specific database.

                                                                                                • You can use other download tools to download backup files.
                                                                                                • You can also run the following command to download backup files:

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

                                                                                                  Variables in the commands are as follows:

                                                                                                  diff --git a/docs/rds/umn/rds_11_0015.html b/docs/rds/umn/rds_11_0015.html index e83c40b8..f9bd3e5c 100644 --- a/docs/rds/umn/rds_11_0015.html +++ b/docs/rds/umn/rds_11_0015.html @@ -1,11 +1,11 @@

                                                                                                  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 Basic Information 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 Basic Information page.
                                                                                                  -

                                                                                                  Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                  5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                  +

                                                                                                  Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                  5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                  -

                                                                                                  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.
                                                                                                  +

                                                                                                  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 new file mode 100644 index 00000000..73d0412e --- /dev/null +++ b/docs/rds/umn/rds_11_0017.html @@ -0,0 +1,62 @@ + + +

                                                                                                  Enabling Read/Write Splitting

                                                                                                  +

                                                                                                  Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. This section describes how to enable read/write splitting.

                                                                                                  +

                                                                                                  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 Basic Information page is displayed.
                                                                                                  5. In the navigation pane on the left, choose Database Proxy.

                                                                                                    Alternatively, in the Connection Information area on the Basic Information page, click Apply in the Read/Write Splitting Address field.

                                                                                                    +

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

                                                                                                    +

                                                                                      Table 1 Supported plugins

                                                                                      Plugin Name

                                                                                      PostgreSQL 9.5

                                                                                      +

                                                                                      PostgreSQL 9.5

                                                                                      PostgreSQL 9.6

                                                                                      +

                                                                                      PostgreSQL 9.6

                                                                                      PostgreSQL 10

                                                                                      +

                                                                                      PostgreSQL 10

                                                                                      PostgreSQL 11

                                                                                      +

                                                                                      PostgreSQL 11

                                                                                      PostgreSQL Enhanced Edition (1.0)

                                                                                      +

                                                                                      PostgreSQL 12

                                                                                      PostgreSQL 12

                                                                                      +

                                                                                      PostgreSQL 13

                                                                                      PostgreSQL 13

                                                                                      +

                                                                                      PostgreSQL 14

                                                                                      address_standardizer

                                                                                      -

                                                                                      +

                                                                                      address_standardizer

                                                                                      +

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      address_standardizer_data_us

                                                                                      +

                                                                                      address_standardizer_data_us

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      btree_gin

                                                                                      +

                                                                                      btree_gin

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      btree_gist

                                                                                      +

                                                                                      btree_gist

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      citext

                                                                                      +

                                                                                      citext

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.6

                                                                                      1.6

                                                                                      +

                                                                                      1.6

                                                                                      1.6

                                                                                      +

                                                                                      1.6

                                                                                      cube

                                                                                      -

                                                                                      For details, see cube.

                                                                                      +

                                                                                      cube

                                                                                      +

                                                                                      For details, see cube.

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      dblink

                                                                                      +

                                                                                      dblink

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      dict_int

                                                                                      +

                                                                                      dict_int

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      dict_xsyn

                                                                                      +

                                                                                      dict_xsyn

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      earthdistance

                                                                                      -

                                                                                      For details, see earthdistance.

                                                                                      +

                                                                                      earthdistance

                                                                                      +

                                                                                      For details, see earthdistance.

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      fuzzystrmatch

                                                                                      +

                                                                                      fuzzystrmatch

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      hll

                                                                                      +

                                                                                      hll

                                                                                      2.12

                                                                                      +

                                                                                      2.12

                                                                                      2.12

                                                                                      +

                                                                                      2.12

                                                                                      2.12

                                                                                      +

                                                                                      2.12

                                                                                      2.12

                                                                                      +

                                                                                      2.12

                                                                                      2.12

                                                                                      +

                                                                                      2.14

                                                                                      2.14

                                                                                      +

                                                                                      2.15.1

                                                                                      2.15.1

                                                                                      +

                                                                                      2.15.1

                                                                                      hstore

                                                                                      +

                                                                                      hstore

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.6

                                                                                      1.6

                                                                                      +

                                                                                      1.7

                                                                                      1.7

                                                                                      +

                                                                                      1.7

                                                                                      intagg

                                                                                      +

                                                                                      intagg

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      intarray

                                                                                      +

                                                                                      intarray

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      isn

                                                                                      +

                                                                                      isn

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      ltree

                                                                                      +

                                                                                      ltree

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.2

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      oracle_fdw

                                                                                      +

                                                                                      oracle_fdw

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      2.1.0

                                                                                      +

                                                                                      2.1.0

                                                                                      2.1.0

                                                                                      +

                                                                                      2.1.0

                                                                                      2.1.0

                                                                                      +

                                                                                      2.2.0

                                                                                      2.2.0

                                                                                      +

                                                                                      2.3.0

                                                                                      2.3.0

                                                                                      +

                                                                                      2.3.0

                                                                                      orafce

                                                                                      +

                                                                                      orafce

                                                                                      3.8.0

                                                                                      +

                                                                                      3.8.0

                                                                                      3.8.0

                                                                                      +

                                                                                      3.8.0

                                                                                      3.8.0

                                                                                      +

                                                                                      3.8.0

                                                                                      3.8.0

                                                                                      +

                                                                                      3.8.0

                                                                                      0

                                                                                      +

                                                                                      3.8.0

                                                                                      3.8.0

                                                                                      +

                                                                                      3.14.0

                                                                                      3.14.0

                                                                                      +

                                                                                      3.14.0

                                                                                      pg_cron

                                                                                      +

                                                                                      pg_cron

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      1.2.0

                                                                                      1.2.0

                                                                                      +

                                                                                      1.3.0

                                                                                      1.3.0

                                                                                      +

                                                                                      1.3.0

                                                                                      pg_hint_plan

                                                                                      +

                                                                                      pg_hint_plan

                                                                                      1.1.5

                                                                                      +

                                                                                      1.1.5

                                                                                      1.2.0

                                                                                      +

                                                                                      1.2.0

                                                                                      1.3.0

                                                                                      +

                                                                                      1.3.0

                                                                                      1.3.5

                                                                                      +

                                                                                      1.3.5

                                                                                      1.3.5

                                                                                      +

                                                                                      1.3.7

                                                                                      1.3.7

                                                                                      +

                                                                                      1.3.7

                                                                                      1.3.7

                                                                                      +

                                                                                      1.3.7

                                                                                      pg_jieba

                                                                                      +

                                                                                      pg_jieba

                                                                                      1.1.0

                                                                                      +

                                                                                      1.1.0

                                                                                      1.1.0

                                                                                      +

                                                                                      1.1.0

                                                                                      1.1.0

                                                                                      +

                                                                                      1.1.0

                                                                                      1.1.0

                                                                                      +

                                                                                      1.1.0

                                                                                      1.1.0

                                                                                      +

                                                                                      1.1.0

                                                                                      1.1.0

                                                                                      +

                                                                                      2.0.1

                                                                                      2.0.1

                                                                                      +

                                                                                      2.0.1

                                                                                      pg_pathman

                                                                                      +

                                                                                      pg_pathman

                                                                                      1.5.8

                                                                                      +

                                                                                      1.5.8

                                                                                      1.5.8

                                                                                      +

                                                                                      1.5.8

                                                                                      1.5.8

                                                                                      +

                                                                                      1.5.8

                                                                                      1.5.8

                                                                                      +

                                                                                      1.5.8

                                                                                      1.5.8

                                                                                      +

                                                                                      1.5.12

                                                                                      1.5.12

                                                                                      +

                                                                                      1.5.12

                                                                                      1.5.12

                                                                                      +

                                                                                      1.5.12

                                                                                      pg_repack

                                                                                      +

                                                                                      pg_repack

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      1.4.6

                                                                                      +

                                                                                      1.4.6

                                                                                      pgrouting

                                                                                      +

                                                                                      pgrouting

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.3

                                                                                      3.1.3

                                                                                      +

                                                                                      3.1.3

                                                                                      pg_stat_statements

                                                                                      +

                                                                                      pg_stat_statements

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.6

                                                                                      +

                                                                                      1.6

                                                                                      1.6

                                                                                      +

                                                                                      1.6

                                                                                      1.6

                                                                                      +

                                                                                      1.7

                                                                                      1.7

                                                                                      +

                                                                                      1.8

                                                                                      1.8

                                                                                      +

                                                                                      1.8

                                                                                      pg_trgm

                                                                                      +

                                                                                      pg_trgm

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.4

                                                                                      1.4

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      pgcrypto

                                                                                      +

                                                                                      pgcrypto

                                                                                      1.2

                                                                                      +

                                                                                      1.2

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      1.3

                                                                                      +

                                                                                      1.3

                                                                                      pgstattuple

                                                                                      +

                                                                                      pgstattuple

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      1.5

                                                                                      +

                                                                                      1.5

                                                                                      plpgsql

                                                                                      +

                                                                                      plpgsql

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      postgis

                                                                                      -

                                                                                      For details, see postgis.

                                                                                      +

                                                                                      postgis

                                                                                      +

                                                                                      For details, see postgis.

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      postgres_fdw

                                                                                      +

                                                                                      postgres_fdw

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      postgis_raster

                                                                                      +

                                                                                      postgis_raster

                                                                                      Integrated to postgis

                                                                                      +

                                                                                      Integrated to postgis

                                                                                      Integrated to postgis

                                                                                      +

                                                                                      Integrated to postgis

                                                                                      Integrated to postgis

                                                                                      +

                                                                                      Integrated to postgis

                                                                                      Integrated to postgis

                                                                                      +

                                                                                      Integrated to postgis

                                                                                      Integrated to postgis

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      postgis_sfcgal

                                                                                      +

                                                                                      postgis_sfcgal

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      postgis_tiger_geocoder

                                                                                      +

                                                                                      postgis_tiger_geocoder

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      postgis_topology

                                                                                      +

                                                                                      postgis_topology

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      2.5.1

                                                                                      2.5.1

                                                                                      +

                                                                                      3.0.0

                                                                                      3.0.0

                                                                                      +

                                                                                      3.1.0

                                                                                      3.1.0

                                                                                      +

                                                                                      3.1.0

                                                                                      tablefunc

                                                                                      +

                                                                                      tablefunc

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      tds_fdw

                                                                                      +

                                                                                      tds_fdw

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      2.0.1

                                                                                      +

                                                                                      2.0.1

                                                                                      2.0.1

                                                                                      +

                                                                                      2.0.1

                                                                                      2.0.1

                                                                                      +

                                                                                      2.0.2

                                                                                      2.0.2

                                                                                      +

                                                                                      2.0.2

                                                                                      timescaledb

                                                                                      -

                                                                                      For details, see timescaledb.

                                                                                      +

                                                                                      timescaledb

                                                                                      +

                                                                                      For details, see timescaledb.

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      1.3.2

                                                                                      +

                                                                                      1.3.2

                                                                                      1.3.2

                                                                                      +

                                                                                      1.3.2

                                                                                      1.3.2

                                                                                      +

                                                                                      1.3.2

                                                                                      1.3.2

                                                                                      +

                                                                                      1.7.0

                                                                                      1.7.0

                                                                                      +

                                                                                      2.1.0

                                                                                      2.1.0

                                                                                      +

                                                                                      2.1.0

                                                                                      unaccent

                                                                                      +

                                                                                      unaccent

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      uuid-ossp

                                                                                      +

                                                                                      uuid-ossp

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      1.1

                                                                                      +

                                                                                      1.1

                                                                                      wal2json

                                                                                      +

                                                                                      wal2json

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      -

                                                                                      +

                                                                                      -

                                                                                      2.3

                                                                                      +

                                                                                      2.3

                                                                                      2.3

                                                                                      +

                                                                                      2.3

                                                                                      2.3

                                                                                      +

                                                                                      2.3

                                                                                      2.3

                                                                                      +

                                                                                      2.3

                                                                                      zhparser

                                                                                      +

                                                                                      zhparser

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      1.0

                                                                                      +

                                                                                      1.0

                                                                                      Primary/Standby (1/1)

                                                                                      		 -
                                                                                      • 2016 EE
                                                                                      • 2017 SE
                                                                                      +
                                                                                      • 2016 EE
                                                                                      • 2017 SE
                                                                                      • 2019 SE

                                                                                      Single DB instances

                                                                                      • 2016 EE
                                                                                      • 2017 SE
                                                                                      +
                                                                                      • 2016 EE
                                                                                      • 2017 SE
                                                                                      • 2019 SE

                                                                                      Cluster

                                                                                      • 2017 EE
                                                                                      +
                                                                                      • 2017 EE
                                                                                      • 2019 EE
                                                                                      + + + + + + + + + + + + + + + + + + + + + + +
                                                                                      Table 1 Parameter description

                                                                                      Parameter

                                                                                      +

                                                                                      Description

                                                                                      +

                                                                                      Proxy Name

                                                                                      +

                                                                                      Set the proxy name based on service requirements.

                                                                                      +

                                                                                      Role

                                                                                      +
                                                                                      • Read/write: Read and write requests are split.
                                                                                      • Read-only: The proxy is not connected to your primary instance and cannot receive write requests.
                                                                                      +

                                                                                      Routing Policy

                                                                                      +
                                                                                      • Weighted: You can change the weights of your DB instance and read replicas after read/write splitting is enabled.
                                                                                      • Load balancing: This policy is only available if proxy load balancing is enabled. After Load balancing is selected, read requests are automatically distributed to multiple read replicas based on the number of active connections to balance the load among these read replicas.
                                                                                      +

                                                                                      You can change the routing policy after the database proxy is created. For details, see Configuring the Delay Threshold and Routing Policy.

                                                                                      +

                                                                                      Read Requests Accepted by Primary DB Instance

                                                                                      +

                                                                                      This parameter is only available if Load balancing is selected.

                                                                                      +
                                                                                      • Yes: Read requests can be routed to both the primary instance and read replicas.
                                                                                      • No: Read requests are routed only to read replicas to offload read pressure from the primary instance.
                                                                                      +

                                                                                      New Instance Class

                                                                                      +

                                                                                      Select specifications for the proxy instance based on service demands. You can change the specifications after the proxy instance is created. For details, see Changing the Instance Class of a DB Proxy Instance.

                                                                                      +

                                                                                      Proxy Nodes

                                                                                      +

                                                                                      Enter an integer from 2 to 8. You can change the nodes after the proxy instance is created.

                                                                                      +

                                                                                      You are advised to set proxy nodes to the quantity of read replicas, with one proxy node for one read replica.

                                                                                      +
                                                                                      +
                                                                                      +
                                                                                      • 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.
                                                                                      +

                                                                                    17. Confirm the database proxy configuration.

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

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

                                                                                      You can view the read/write splitting address on the Basic Information 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.

                                                                                      +

                                                                                      19. + + + + diff --git a/docs/rds/umn/rds_11_0018.html b/docs/rds/umn/rds_11_0018.html new file mode 100644 index 00000000..27ca3a74 --- /dev/null +++ b/docs/rds/umn/rds_11_0018.html @@ -0,0 +1,43 @@ + + +

                                                                                      Configuring the Delay Threshold and Routing Policy

                                                                                      +

                                                                                      After read/write splitting is enabled, you can configure the delay threshold and routing policy as required.

                                                                                      + +
                                                                                      + + + + + + + + + + +
                                                                                      Table 1 Read/write splitting parameters

                                                                                      Parameter

                                                                                      +

                                                                                      Description

                                                                                      +

                                                                                      Delay Threshold

                                                                                      +

                                                                                      The maximum delay for data to be synchronized from primary DB instances to read replicas. To prevent data inconsistencies between primary DB instances and read replicas from lasting too long, if the delay of a read replica exceeds the configured threshold, read requests are not forwarded to the read replica regardless of the read weight distributed to it.

                                                                                      +

                                                                                      When read/write splitting is enabled, the default delay threshold is 30s and the default value range is 0–7,200s. It is recommended that the threshold be greater than or equal to 30s. Traffic is not allocated to read replicas whose delay exceeds the configured threshold.

                                                                                      +

                                                                                      Read Weight Distribution

                                                                                      +

                                                                                      When read/write splitting is enabled, the read weight of the primary DB instance is 0 by default. You can modify the read weights distributed to read replicas.

                                                                                      +

                                                                                      Read replicas with higher read weight distributions process more read requests. For example, if the read weights distributed to one primary DB instance and four read replicas are 0, 100, 200, 500, and 300, respectively, the primary DB instance does not process read requests (write requests are all automatically forwarded to the primary DB instance) while the four read replicas process read requests with a ratio of 1:2:5:3.

                                                                                      +

                                                                                      The system automatically distributes weights to read replicas, including read replicas created afterwards, according to their specifications based on the distribution rules listed in Rules for Distributing Weights.

                                                                                      +
                                                                                      +
                                                                                      +

                                                                                      Configuring Delay 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 target DB instance. The Basic Information page is displayed.
                                                                                      5. In the navigation pane on the left, click Database Proxy.
                                                                                      6. In the proxy information area, click next to the Delay Threshold field.
                                                                                      +
                                                                                      +

                                                                                      Configuring Routing Policy in Single-Proxy Mode

                                                                                      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 Basic Information page is displayed.
                                                                                      5. In the navigation pane on the left, click Database Proxy.
                                                                                      6. If proxy load balancing is not enabled, click Configure next to the Routing Policy field in the proxy information area. In the displayed dialog box, configure read weights for the primary instance and read replicas.

                                                                                        • The system automatically distributes weights to read replicas, including read replicas created afterwards, according to the default distribution rules. If a read replica breaks down or is deleted, the weight is automatically removed. After the read replica recovers, the weight is automatically restored.
                                                                                        • If the weight of a node is set to 0, read requests will not be routed to the node. If the weights of all nodes are set to 0, read requests will be randomly routed to these nodes.
                                                                                        +
                                                                                        +

                                                                                      7. Click OK and view the weights on the Database Proxy page.
                                                                                      8. If proxy load balancing is enabled, click Configure next to the Routing Policy field in the proxy information area. In the displayed dialog box, set required parameters.

                                                                                        Select Load balancing as the routing policy. Read requests will be automatically distributed to read replicas based on the number of active connections to balance the load among these read replicas.

                                                                                        +
                                                                                        Set Read Requests Accepted by Primary DB Instance:
                                                                                        • Yes: Read requests can be routed to both the primary instance and read replicas, which increases the load of the primary instance to some extent. Configure this parameter based on your workload requirements.
                                                                                        • No: To offload read pressure from the primary instance, read requests are only routed to read replicas.
                                                                                        +
                                                                                        +

                                                                                      9. Click OK. On the Database Proxy page, view the result. You can select the instances for load balancing as required.
                                                                                      +
                                                                                      +
                                                                                      + + diff --git a/docs/rds/umn/rds_11_0019.html b/docs/rds/umn/rds_11_0019.html new file mode 100644 index 00000000..c10b1b9d --- /dev/null +++ b/docs/rds/umn/rds_11_0019.html @@ -0,0 +1,15 @@ + + +

                                                                                      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 Basic Information 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_0020.html b/docs/rds/umn/rds_11_0020.html new file mode 100644 index 00000000..d8f2038c --- /dev/null +++ b/docs/rds/umn/rds_11_0020.html @@ -0,0 +1,20 @@ + + +

                                                                                      Rules for Distributing Weights

                                                                                      +

                                                                                      This section describes the rules of distributing read weights to DB instances of different specifications.

                                                                                      +

                                                                                      Weight Distribution Rules

                                                                                      When the system automatically sets the read weights for DB instances, the weight values are fixed.

                                                                                      The default weight equals to the number of vCPUs multiplied by 50. The weight ranges from 100 to 1000.

                                                                                      +
                                                                                      +
                                                                                      +
                                                                                      +

                                                                                      Adding a Hint to Specify the Direction that a SQL Statement Will Be Routed

                                                                                      Hints supported by read/write splitting are as follows:

                                                                                      +
                                                                                      • /*FORCE_MASTER*/: A SQL statement is routed to the primary DB instance.
                                                                                      • /*FORCE_SLAVE*/: A SQL statement is routed to a read replica.
                                                                                      +
                                                                                      • In addition to the weight distribution system of read/write splitting, hints are a useful type of SQL syntax that allows you to specify whether a SQL statement is executed on the primary DB instance or on a read replica.
                                                                                      • Hints are only used as routing suggestions. In non-read-only SQL and non-transaction scenarios, SQL statements cannot be routed to read replicas.
                                                                                      +
                                                                                      +
                                                                                      +
                                                                                      + + diff --git a/docs/rds/umn/rds_11_0021.html b/docs/rds/umn/rds_11_0021.html new file mode 100644 index 00000000..e239fb20 --- /dev/null +++ b/docs/rds/umn/rds_11_0021.html @@ -0,0 +1,15 @@ + + +

                                                                                      Testing Read/Write Splitting Performance

                                                                                      +

                                                                                      After read/write splitting is enabled, databases can be connected through a read/write splitting address. You can use internal SQL commands to verify the read/write splitting performance.

                                                                                      +

                                                                                      Procedure

                                                                                      1. Connect to a database through a read/write splitting address by referring to Enabling Read/Write Splitting.
                                                                                      2. Run show last route to view the routing result of the previous SQL statement.

                                                                                        Figure 1 Query result
                                                                                        +

                                                                                        Do not use show last route for service code or include it in multi-statements.

                                                                                        +

                                                                                      +
                                                                                      +
                                                                                      + + diff --git a/docs/rds/umn/rds_11_0022.html b/docs/rds/umn/rds_11_0022.html index 9d0f2bc2..17173e26 100644 --- a/docs/rds/umn/rds_11_0022.html +++ b/docs/rds/umn/rds_11_0022.html @@ -6,7 +6,7 @@

                                                                                      If you delete a database or modify some records in a database at a specified time, you only need to restore the database instead of restoring the whole DB instance. You can also restore databases to a point in time as required.

                                                                                      When you enter the time point that you want to restore the DB instance to, RDS downloads the most recent full backup file from OBS to the DB instance. Then, incremental backups are also restored to the specified point in time on the DB instance. Data is restored at an average speed of 30 MB/s.

                                                                                      -

                                                                                      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.
                                                                                      5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                                                      6. In the displayed dialog box, configure required information and click OK.

                                                                                        1. Select the time range, select or enter a time point within the acceptable range.
                                                                                        2. Select a restoration method.
                                                                                          • Create New Instance

                                                                                            The Create New Instance page is 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 DB instance.
                                                                                            5. In the navigation pane on the left, choose Backups & Restorations. On the displayed page, click Restore to Point in Time.
                                                                                            6. In the displayed dialog box, configure required information and click OK.

                                                                                              1. Select the time range, select or enter a time point within the acceptable range.
                                                                                              2. Select a restoration method.
                                                                                                • Create New Instance

                                                                                                  The Create New Instance page is displayed.

                                                                                                  • The DB engine of the new DB instance is the same as that of the original DB instance and cannot be changed.
                                                                                                  • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                                                                  • Other settings are the same as those of the original DB instance by default and can be modified. For details, see section Step 1: Create a DB Instance.
                                                                                                • Restore to Original
                                                                                                  • Restoring to the original DB instance will overwrite data on it and cause the original DB instance to be unavailable during the restoration.
                                                                                                  diff --git a/docs/rds/umn/rds_11_0023.html b/docs/rds/umn/rds_11_0023.html index 3e70cc0b..bd03becf 100644 --- a/docs/rds/umn/rds_11_0023.html +++ b/docs/rds/umn/rds_11_0023.html @@ -3,7 +3,7 @@

                                                                                                  Restoring from Backup Files to RDS for SQL Server

                                                                                                  Scenarios

                                                                                                  This section describes how to use an automated or manual backup to restore a DB instance to the status when the backup was created.

                                                                                                  -

                                                                                                  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 Backups & Restorations page, locate the target backup and click Restore in the Operation column.

                                                                                                    Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                                                                    +

                                                                                                    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 Backups & Restorations page, locate the target backup and click Restore in the Operation column.

                                                                                                      Alternatively, click the target DB instance on the Instances page. On the displayed page, choose Backups & Restorations. On the displayed page, select the target backup to be restored and click Restore in the Operation column.

                                                                                                    5. In the displayed dialog box, configure required information and click OK.

                                                                                                      1. Select a restoration method and click OK.
                                                                                                        • Create New Instance
                                                                                                          The Create New Instance page is displayed.
                                                                                                          • The DB engine of the new DB instance is the same as that of the original DB instance and cannot be changed.
                                                                                                          • Storage space of the new DB instance is the same as that of the original DB instance by default and the new instance must be at least as large as the original DB instance.
                                                                                                          • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Step 1: Create a DB Instance.
                                                                                                        • Restore to Original
                                                                                                          • If the DB instance for which the backup is created has been deleted, data cannot be restored to the original DB instance.
                                                                                                          • Restoring to the original DB instance will overwrite data on it and cause the original DB instance to be unavailable during the restoration.
                                                                                                          diff --git a/docs/rds/umn/rds_11_0024.html b/docs/rds/umn/rds_11_0024.html new file mode 100644 index 00000000..cf882aef --- /dev/null +++ b/docs/rds/umn/rds_11_0024.html @@ -0,0 +1,19 @@ + + +

                                                                                                          Upgrading the Kernel Version of Database Proxy

                                                                                                          +

                                                                                                          Scenarios

                                                                                                          You can manually upgrade the RDS for MySQL database proxy to the latest kernel version to improve performance, add new functions, and fix problems.

                                                                                                          +
                                                                                                          +

                                                                                                          Precautions

                                                                                                          Intermittent disconnections occur during the upgrade. The time required to complete the upgrade depends on how many proxy instances there are. Perform the upgrade during off-peak hours.

                                                                                                          + +
                                                                                                          +

                                                                                                          Constraints

                                                                                                          • Only proxy instances with kernel version 2.3.0.1 or later can be upgraded manually on the console.
                                                                                                          • A version upgrade cannot be rolled back after the upgrade is complete.
                                                                                                          +
                                                                                                          +

                                                                                                          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.
                                                                                                          5. On the Database Proxy page, in the Proxy Instance Information area, click Upgrade in the Version field.
                                                                                                          6. In the displayed dialog box, select a scheduled time and click OK.
                                                                                                          +
                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_11_0025.html b/docs/rds/umn/rds_11_0025.html new file mode 100644 index 00000000..4bd41dab --- /dev/null +++ b/docs/rds/umn/rds_11_0025.html @@ -0,0 +1,17 @@ + + +

                                                                                                          Enabling or Disabling Access Control

                                                                                                          +

                                                                                                          If load balancing is enabled for a database proxy instance, the security group associated with the proxy instance does not apply. You need to use access control to grant access from specific IP addresses.

                                                                                                          +

                                                                                                          Enabling Access Control

                                                                                                          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 Database Proxy page, in the proxy instance information area, click in the Access Control field.
                                                                                                          6. Click Configure. In the displayed dialog box, set the access control mode and IP addresses or CIDR blocks.

                                                                                                            • Access Control: The blocklist and allowlist cannot be configured at the same time. If you switch between lists, your previously entered settings will be lost. IP addresses or CIDR blocks in the blocklist are not allowed to access proxy instances.
                                                                                                            • IP Address or CIDR Block: Enter valid IP addresses or CIDR blocks that meet the following requirements:
                                                                                                              • Each line contains an IP address or a CIDR block and ends with a line break.
                                                                                                              • Each IP address or CIDR block can include a description separated by a vertical bar symbol (|), for example, 192.168.10.10|RDS01. The description can include up to 50 characters but cannot contain angle brackets (<>).
                                                                                                              • Up to 300 IP addresses or CIDR blocks can be added.
                                                                                                              +
                                                                                                            +

                                                                                                          +
                                                                                                          +

                                                                                                          Disabling Access Control

                                                                                                          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 Database Proxy page, in the Proxy Instance Information area, click in the Access Control field.
                                                                                                          +
                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_11_0026.html b/docs/rds/umn/rds_11_0026.html new file mode 100644 index 00000000..83cde2ca --- /dev/null +++ b/docs/rds/umn/rds_11_0026.html @@ -0,0 +1,21 @@ + + +

                                                                                                          Changing the Read/Write Splitting Address

                                                                                                          +

                                                                                                          Scenarios

                                                                                                          After read/write splitting is enabled, you can change the read/write splitting address.

                                                                                                          +
                                                                                                          +

                                                                                                          Precautions

                                                                                                          Changing the read/write splitting address will interrupt database connections and services. Therefore, change the read/write splitting address during off-peak hours or when services are stopped.

                                                                                                          +
                                                                                                          +

                                                                                                          Constraints

                                                                                                          The new IP address is not in use and must be in the same subnet as the RDS for MySQL instance.

                                                                                                          +
                                                                                                          +

                                                                                                          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 Connection Information area on the Basic Information 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_0028.html b/docs/rds/umn/rds_11_0028.html new file mode 100644 index 00000000..2f5f5e93 --- /dev/null +++ b/docs/rds/umn/rds_11_0028.html @@ -0,0 +1,23 @@ + + +

                                                                                                          Changing the Instance Class of a DB Proxy Instance

                                                                                                          +

                                                                                                          Scenarios

                                                                                                          You can change the instance class (vCPU or memory) of a DB proxy instance as required. If the DB instance status changes from Changing proxy instance class to Available, the change was successful.

                                                                                                          +
                                                                                                          +

                                                                                                          Constraints

                                                                                                          • You can change the instance class of a DB proxy instance only when the statuses of your primary DB instance, read replicas, and DB proxy instance are Available.
                                                                                                          • A DB proxy instance cannot be deleted when its instance class is being changed.
                                                                                                          • Changing the instance class of a DB proxy instance will cause the instance to reboot. Therefore, perform the operation 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 instance name.
                                                                                                          5. Choose Database Proxy from the navigation pane on the left. In the Proxy Instance Information area, click Change in the Specifications field.

                                                                                                            +

                                                                                                            You can change the DB proxy instance class if required.

                                                                                                            +

                                                                                                            Changing the DB proxy instance class will cause the instance to reboot. To prevent service interruptions, change the DB proxy instance class during off-peak hours.

                                                                                                            +

                                                                                                            If you have selected Maintenance Window for Scheduled Time, the DB proxy instance will be rebooted during the instance class change time and services will be interrupted. To prevent service interruptions, you are advised to set the maintenance window to off-peak hours. For details, see Changing the Maintenance Window.

                                                                                                            +

                                                                                                          6. Confirm the specifications and click Submit.

                                                                                                            If you need to modify your settings, click Previous.

                                                                                                            + +

                                                                                                          7. View the instance class change result.

                                                                                                            Changing the DB proxy instance class takes 13–15 minutes. During this period, the status of the primary DB instance on the Instances page is Changing proxy instance class. After a few minutes, view the proxy instance class on the Database Proxy page to check that the change is successful.

                                                                                                            +

                                                                                                          +
                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_11_0030.html b/docs/rds/umn/rds_11_0030.html index fe501a21..7c99c6ed 100644 --- a/docs/rds/umn/rds_11_0030.html +++ b/docs/rds/umn/rds_11_0030.html @@ -7,9 +7,9 @@
                                                                                                          • If you delete a primary DB instance, its standby DB instance and read replicas (if any) are also deleted automatically. Exercise caution when performing this operation.
                                                                                                          • Deleted DB instances cannot be recovered and resources are released. Exercise caution when performing this operation. If you want to retain data, create a manual backup first before deleting the DB instance.
                                                                                                          • You can restore a DB instance that was deleted up to 7 days ago from the recycle bin. For details, see Recycling a DB Instance.
                                                                                                          • You can use a manual backup to restore a DB instance. For details, see Restoring from Backup Files to DB Instances.
                                                                                                          -

                                                                                                          Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                                                                                          5. In the displayed dialog box, click Yes.
                                                                                                          6. Refresh the DB instance list later to confirm that the deletion was successful.
                                                                                                          +

                                                                                                          Deleting 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, locate the primary DB instance to be deleted and click More > Delete in the Operation column.
                                                                                                          5. In the displayed dialog box, click Yes.
                                                                                                          6. Refresh the DB instance list later to confirm that the deletion was successful.
                                                                                                          -

                                                                                                          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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                                                                                          5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                                                                                          6. In the displayed dialog box, click Yes.
                                                                                                          7. Refresh the DB instance list later to check that the deletion is successful.
                                                                                                          +

                                                                                                          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. On the Instances page, locate the target DB instance and click . All the read replicas created for the DB instance are displayed.
                                                                                                          5. Locate the read replica to be deleted and click More > Delete in the Operation column.
                                                                                                          6. In the displayed dialog box, click Yes.
                                                                                                          7. Refresh the DB instance list later to check that the deletion is successful.
                                                                                                          diff --git a/docs/rds/umn/rds_11_0031.html b/docs/rds/umn/rds_11_0031.html index 2f7cb558..5c9cab8b 100644 --- a/docs/rds/umn/rds_11_0031.html +++ b/docs/rds/umn/rds_11_0031.html @@ -6,7 +6,7 @@
                                                                                                          The default automated backup policy is as follows:
                                                                                                          • Retention period: 7 days
                                                                                                          • Time window: An hour within 24 hours, such as 01:00-02:00 or 12:00-13:00. The backup time is configured based on UTC time and is adjusted for daylight saving time, which changes at different times depending on the time zone.
                                                                                                          • Backup cycle: Each day of the week
                                                                                                          -

                                                                                                          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, click Modify Backup Policy.

                                                                                                            • Retention Period refers to the number of days that your automated backups can be retained. Increasing the retention period will improve data reliability.
                                                                                                            • If you shorten the retention period, the new backup policy takes effect for all backup files. The backup files that have expired will be deleted.
                                                                                                            • The backup retention period indicates the number of days you want automated full and incremental backups of your DB instance to be retained. 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, click Modify Backup Policy.

                                                                                                              • Retention Period refers to the number of days that your automated backups can be retained. Increasing the retention period will improve data reliability.
                                                                                                              • If you shorten the retention period, the new backup policy takes effect for all backup files. The backup files that have expired will be deleted.
                                                                                                              • The backup retention period indicates the number of days you want automated full and incremental backups of your DB instance to be retained. 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.

                                                                                                            6. Click OK.
                                                                                                          diff --git a/docs/rds/umn/rds_11_0032.html b/docs/rds/umn/rds_11_0032.html index 93e9b847..9735a951 100644 --- a/docs/rds/umn/rds_11_0032.html +++ b/docs/rds/umn/rds_11_0032.html @@ -3,8 +3,8 @@

                                                                                                          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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                                                                                          6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information 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. In the Connection Information area on the Basic Information page, click in the Security Group field.

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

                                                                                                          6. Changing the security group takes 1 to 3 minutes. Click in the upper right corner on the Basic Information page to view the results.
                                                                                                          diff --git a/docs/rds/umn/rds_11_0035.html b/docs/rds/umn/rds_11_0035.html new file mode 100644 index 00000000..0d17789a --- /dev/null +++ b/docs/rds/umn/rds_11_0035.html @@ -0,0 +1,16 @@ + + +

                                                                                                          Introducing Read/Write Splitting

                                                                                                          +

                                                                                                          Read/write splitting enables read and write requests to be automatically routed through a read/write splitting address. You can enable read/write splitting after read replicas are created. Write requests are automatically routed to the primary DB instance and read requests are routed to read replicas by user-defined weights.

                                                                                                          +

                                                                                                          Proxy load balancing balances requests among multiple read replicas using a load-based scheduling policy. To enable proxy load balancing, contact customer service to apply for the required permissions.

                                                                                                          +

                                                                                                          Constraints

                                                                                                          When read/write splitting is enabled, the system automatically deletes the existing account rdsProxy and creates a new rdsProxy account. When read/write splitting is disabled, the system automatically deletes the existing account rdsProxy. To prevent the system from deleting your created rdsProxy account, you are advised not to create it.

                                                                                                          +
                                                                                                          +
                                                                                                          • To use read/write splitting, connect to your DB instance through a private network because read/write splitting addresses are private IP addresses.
                                                                                                          • If you delete a primary DB instance after read/write splitting is enabled, the read replicas are also deleted and the read/write splitting function is disabled.
                                                                                                          • After read/write splitting is enabled, database ports, security groups, and floating IP addresses of both the primary DB instance and read replicas cannot be changed. If you do need to change any of them, change it before enabling read/write splitting.
                                                                                                          • Read/write splitting does not support SSL encryption.
                                                                                                          • Read/write splitting does not support the compression protocol.
                                                                                                          • Read/write splitting does not support the READ UNCOMMITTED transaction isolation level.
                                                                                                          • If multi-statements are executed, all subsequent requests will be routed to the primary DB instance. To restore the read/write splitting function, disconnect the connection from your applications and establish a connection again.
                                                                                                          • When read and write requests are split through the read/write splitting address, all transaction requests are routed to the primary DB instance while the non-transaction read consistency is not ensured. To ensure read consistency, encapsulate requests into transactions.
                                                                                                          • When the read/write splitting address is used, the LAST_INSERT_ID() function can be used only in transactions.
                                                                                                          • When the read/write splitting address is used, the execution results of the show processlist command are inconsistent.
                                                                                                          • When the read/write splitting address is used, the show errors and show warnings commands are not supported.
                                                                                                          • When the read/write splitting address is used, user-defined variables, such as the SET @variable statements, are not supported.
                                                                                                          • When the read/write splitting address is used, if stored procedures and functions depend on user variables (@variable), the execution result may be incorrect.
                                                                                                          +
                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_11_0045.html b/docs/rds/umn/rds_11_0045.html new file mode 100644 index 00000000..4c647905 --- /dev/null +++ b/docs/rds/umn/rds_11_0045.html @@ -0,0 +1,18 @@ + + +

                                                                                                          Changing the Number of Proxy Nodes

                                                                                                          +

                                                                                                          Scenarios

                                                                                                          After read/write splitting is enabled, you can change the number of proxy nodes as required.

                                                                                                          +
                                                                                                          +

                                                                                                          Prerequisites

                                                                                                          • Read/write splitting has been enabled.
                                                                                                          • The primary DB instance, read replicas, and proxy instance are all available.
                                                                                                          +
                                                                                                          +

                                                                                                          Constraints

                                                                                                          The number of proxy nodes ranges from 2 to 8.

                                                                                                          +
                                                                                                          +

                                                                                                          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.
                                                                                                          5. In the Proxy Instance Information area on the Database Proxy page, click Change next to the Proxy Nodes field.
                                                                                                          6. Set the number of proxy nodes and click Next.
                                                                                                          7. Confirm the settings and click Submit.
                                                                                                          +
                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_11_0047.html b/docs/rds/umn/rds_11_0047.html new file mode 100644 index 00000000..94fd1c2b --- /dev/null +++ b/docs/rds/umn/rds_11_0047.html @@ -0,0 +1,22 @@ + + +

                                                                                                          Configuring Transaction Splitting

                                                                                                          +

                                                                                                          Scenarios

                                                                                                          In most cases, an RDS for MySQL proxy instance sends all requests in transactions to the primary DB instance to ensure transaction correctness. However, in some frameworks, all requests are encapsulated into transactions that are not automatically committed using set autocommit=0. This causes heavy loads on the primary DB instance.

                                                                                                          +
                                                                                                          +

                                                                                                          Function

                                                                                                          Database proxies support transaction splitting. With this feature enabled, RDS can route the read requests prior to write operations in a transaction to read replicas, reducing the pressure of the primary DB instance.

                                                                                                          +

                                                                                                          Transaction splitting is disabled by default. If it is enabled under the default READ COMMITTED transaction isolation, RDS only starts a transaction for write operations when automatic commit is disabled. Before the transaction starts, read requests are routed to read replicas through load balancers.

                                                                                                          +
                                                                                                          +

                                                                                                          Precautions

                                                                                                          Enabling transaction splitting affects global consistency of certain workloads. Before enabling this feature, evaluate its impact on your workloads.

                                                                                                          +
                                                                                                          +

                                                                                                          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 Basic Information 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_11_0050.html b/docs/rds/umn/rds_11_0050.html new file mode 100644 index 00000000..e1057481 --- /dev/null +++ b/docs/rds/umn/rds_11_0050.html @@ -0,0 +1,37 @@ + + +

                                                                                                          Database Proxy (Read/Write Splitting)

                                                                                                          +
                                                                                                          + + diff --git a/docs/rds/umn/rds_add_read_replica_pg.html b/docs/rds/umn/rds_add_read_replica_pg.html index 1399417e..91162885 100644 --- a/docs/rds/umn/rds_add_read_replica_pg.html +++ b/docs/rds/umn/rds_add_read_replica_pg.html @@ -7,7 +7,7 @@

                                                                                                          A maximum of five read replicas can be created for a primary DB instance.

                                                                                                          The specifications of read replicas must be greater than or equal to the specifications of the current primary 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 click Create Read Replica in the Operation column.

                                                                                                            Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

                                                                                                            +

                                                                                                            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 Create Read Replica in the Operation column.

                                                                                                              Alternatively, click the target DB instance. In the DB instance topology, click under the primary DB instance to create read replicas.

                                                                                                            5. On the displayed page, configure information about the DB instance and click Next.

                                                                                                              @@ -110,7 +110,7 @@
                                                                                                              Table 1 Basic information

                                                                                                              Parameter

                                                                                                            6. Confirm specifications.

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

                                                                                                            7. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

                                                                                                              Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

                                                                                                              +

                                                                                                            8. After a read replica has been created, you can view and manage it on the Instances page by clicking on the left of the DB instance to which it belongs.

                                                                                                              Alternatively, click the target DB instance. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.

                                                                                                            diff --git a/docs/rds/umn/rds_change_database_port.html b/docs/rds/umn/rds_change_database_port.html index b908f818..8e6fe18a 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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                              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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                                A MySQL database can use ports 2100 to 9500.

                                                                                                                -
                                                                                                                • To submit the change, click .
                                                                                                                  • In the dialog box, click Yes.
                                                                                                                    1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                    2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
                                                                                                                    3. This process takes 1-5 minutes.
                                                                                                                    +
                                                                                                                    • To submit the change, click .
                                                                                                                      • In the dialog box, click Yes.
                                                                                                                        1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                        2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
                                                                                                                        3. This process takes 1-5 minutes.
                                                                                                                      • In the dialog box, click No to cancel the modification.
                                                                                                                      -
                                                                                                                    • To cancel the change, click .
                                                                                                                    +
                                                                                                                  • To cancel the change, click .

                                                                                                                • View the results on the Basic Information page.
                                                                                                              diff --git a/docs/rds/umn/rds_configuration.html b/docs/rds/umn/rds_configuration.html index 7420b0b7..eb353cfb 100644 --- a/docs/rds/umn/rds_configuration.html +++ b/docs/rds/umn/rds_configuration.html @@ -7,14 +7,14 @@

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

                                                                                                              RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

                                                                                                              -

                                                                                                              Modifying Parameter Template Parameters

                                                                                                              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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                              5. On the Parameters page, modify parameters as required.

                                                                                                                For parameter description details, see Suggestions on MySQL Parameter Tuning.

                                                                                                                +

                                                                                                                Modifying Parameter Template Parameters

                                                                                                                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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                5. On the Parameters page, modify parameters as required.

                                                                                                                  For parameter description details, see Suggestions on MySQL Parameter Tuning.

                                                                                                                  Available operations are as follows:

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

                                                                                                                6. After the parameter values are modified, you can click View Change History to view the details.
                                                                                                                7. The modifications do not take effect until you apply the parameter template to your DB instances. For details, see Applying a Parameter Template.
                                                                                                                8. View the status of the DB instance to which the parameter template was applied.

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

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

                                                                                                                -

                                                                                                                Modifying Instance Parameters

                                                                                                                1. Log in to the 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 displayed page, modify parameters as required.

                                                                                                                  Check the value in the Effective upon Reboot column.
                                                                                                                  • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
                                                                                                                    • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
                                                                                                                    • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
                                                                                                                    +

                                                                                                                    Modifying Instance Parameters

                                                                                                                    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 displayed page, modify parameters as required.

                                                                                                                      Check the value in the Effective upon Reboot column.
                                                                                                                      • If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
                                                                                                                        • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
                                                                                                                        • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
                                                                                                                      • If the value is No, the modifications take effect immediately.
                                                                                                                      diff --git a/docs/rds/umn/rds_download_sql_auditing_log.html b/docs/rds/umn/rds_download_sql_auditing_log.html index 6627cdd4..584466cb 100644 --- a/docs/rds/umn/rds_download_sql_auditing_log.html +++ b/docs/rds/umn/rds_download_sql_auditing_log.html @@ -2,8 +2,8 @@

                                                                                                                      Downloading SQL Audit Logs

                                                                                                                      If you enable the SQL audit function, all SQL operations will be logged, and you can download audit logs to view details. By default, the SQL audit function is disabled. Enabling this function may affect 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 DB instance.
                                                                                                                      5. In the navigation pane on the left, choose SQL Audits.
                                                                                                                      6. On the displayed page, select a time range in the upper right corner, select SQL audit logs to be downloaded in the list, and click Download above the list to download SQL audit logs in batches.

                                                                                                                        Alternatively, select an audit log and click Download in the Operation column to download an individual SQL audit log.

                                                                                                                        -

                                                                                                                      7. The following figure shows the SQL audit log content. For field descriptions, see Table 1.

                                                                                                                        Figure 1 MySQL audit logs
                                                                                                                        +

                                                                                                                        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.
                                                                                                                        5. In the navigation pane on the left, choose SQL Audits.
                                                                                                                        6. On the displayed page, select a time range in the upper right corner, select SQL audit logs to be downloaded in the list, and click Download above the list to download SQL audit logs in batches.

                                                                                                                          Alternatively, select an audit log and click Download in the Operation column to download an individual SQL audit log.

                                                                                                                          +

                                                                                                                        7. The following figure shows the SQL audit log content. For field descriptions, see Table 1.

                                                                                                                          Figure 1 MySQL audit logs
                                                                                                                          diff --git a/docs/rds/umn/rds_faq_0016.html b/docs/rds/umn/rds_faq_0016.html index 13e771bc..6435baf4 100644 --- a/docs/rds/umn/rds_faq_0016.html +++ b/docs/rds/umn/rds_faq_0016.html @@ -2,7 +2,7 @@

                                                                                                                          Are My RDS DB Instances Available When Scaling?

                                                                                                                          Currently, you can scale up storage space and change the CPU or memory of a DB instance.

                                                                                                                          -
                                                                                                                          • When storage space is being scaled up, RDS DB instances are still available and services are not affected. However, you cannot delete or reboot DB instances that are being scaled.
                                                                                                                          • When the CPU or memory of DB instances is being changed, the network is intermittently disconnected once or twice within a few seconds. (For Microsoft SQL Server 2017 Enterprise Edition, you need to stop services first and then change the CPU or memory of DB instances.) For primary/standby DB instances, a failover may occur and services may be briefly interrupted. Changing the CPU or memory takes 5 to 15 minutes.

                                                                                                                            After you change the CPU or memory, the DB instances will reboot and services will be interrupted. Therefore, select off-peak hours to perform this operation. Rebooting a DB instance will clear the cached memory in it. You are advised to reboot it during off-peak hours.

                                                                                                                            +
                                                                                                                            • When storage space is being scaled up, RDS DB instances are still available and services are not affected. However, you cannot delete or reboot DB instances that are being scaled.
                                                                                                                            • When the CPU or memory of DB instances is being changed, the network is intermittently disconnected once or twice within a few seconds. For primary/standby DB instances, a failover may occur and services may be briefly interrupted. Changing the CPU or memory takes 5 to 15 minutes.

                                                                                                                              After you change the CPU or memory, the DB instances will reboot and services will be interrupted. Therefore, select off-peak hours to perform this operation. Rebooting a DB instance will clear the cached memory in it. You are advised to reboot it during off-peak hours.

                                                                                                                          diff --git a/docs/rds/umn/rds_faq_0027.html b/docs/rds/umn/rds_faq_0027.html index ed882992..ee163e37 100644 --- a/docs/rds/umn/rds_faq_0027.html +++ b/docs/rds/umn/rds_faq_0027.html @@ -3,7 +3,7 @@

                                                                                                                          How Can I Install the MySQL Client?

                                                                                                                          MySQL provides client installation packages for different OSs on its official website. MySQL 5.6 is used as an example. Download the MySQL 5.6 client installation package or other versions of the packages. The following procedure illustrates how to obtain the required installation package and install the MySQL client into a Red Hat Linux system.

                                                                                                                          Procedure

                                                                                                                          1. Obtain the installation package.

                                                                                                                            Find the link to the required version on the download page. MySQL-client-5.6.31-1.el6.x86_64.rpm is used as an example in the following figure.

                                                                                                                            -
                                                                                                                            Figure 1 Procedure
                                                                                                                            +
                                                                                                                            Figure 1 Procedure

                                                                                                                            Click URL to download the installation package.

                                                                                                                            diff --git a/docs/rds/umn/rds_faq_0029.html b/docs/rds/umn/rds_faq_0029.html index 6d1a38bd..1da62f2a 100644 --- a/docs/rds/umn/rds_faq_0029.html +++ b/docs/rds/umn/rds_faq_0029.html @@ -1,20 +1,16 @@

                                                                                                                            How Can I Install the PostgreSQL Client?

                                                                                                                            -

                                                                                                                            PostgreSQL provides client installation packages and the required dynamic shared library packages for different OSs on its official website.

                                                                                                                            -

                                                                                                                            Ensure that the database client matches the DB engine version of your RDS PostgreSQL DB instances.

                                                                                                                            -
                                                                                                                            -

                                                                                                                            This following uses PostgreSQL 9.5 in Red Hat Linux 6 as an example to describe how to obtain the required installation package and complete the installation.

                                                                                                                            -

                                                                                                                            Procedure

                                                                                                                            1. Obtain the PostgreSQL client installation package.

                                                                                                                              Find the link to the required version on the download page. postgresql95 is used as an example in the following figure.

                                                                                                                              -
                                                                                                                              Figure 1 Downloading the PostgreSQL client installation package
                                                                                                                              -

                                                                                                                            2. Obtain the dynamic shared library package required for the PostgreSQL client.

                                                                                                                              Find the link to the required version on the download page. postgresql95-libs is used as an example in the following figure.

                                                                                                                              -
                                                                                                                              Figure 2 Downloading the dynamic shared library package
                                                                                                                              -

                                                                                                                            3. Upload the installation and dynamic shared library packages to the ECS.

                                                                                                                              1. When you create an ECS, select an OS, such as Red Hat 6.6, and bind an EIP to it.
                                                                                                                              2. Use a remote connection tool to connect to the ECS through the bound EIP and upload the installation package and dynamic dependency package to the ECS.
                                                                                                                              -

                                                                                                                            4. Run the following command to install the PostgreSQL client:

                                                                                                                              sudo rpm -ivh postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
                                                                                                                              -
                                                                                                                              • If there are any conflicts during the installation, add the replacefiles parameter to the command and try to install the client again. Example:
                                                                                                                                rpm -ivh --replacefiles postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
                                                                                                                                -
                                                                                                                              • If a message is displayed prompting you to install a dependency package, you can add the nodeps parameter to the command and install the client again. Example:
                                                                                                                                rpm -ivh --nodeps postgresql95-9.5.7-1PGDG.rhel6.x86_64.rpm postgresql95-libs-9.5.7-1PGDG.rhel6.x86_64.rpm
                                                                                                                                -
                                                                                                                              -
                                                                                                                              +

                                                                                                                              PostgreSQL provides client installation methods for different OSs on its official website.

                                                                                                                              +

                                                                                                                              The following describes how to install a PostgreSQL 12 client in CentOS.

                                                                                                                              +

                                                                                                                              Procedure

                                                                                                                              1. Log in to an ECS.

                                                                                                                                1. When you create an ECS, select an OS, such as CentOS 7, and bind an EIP to it.
                                                                                                                                2. Use a remote connection tool to connect to the ECS through the EIP.
                                                                                                                                +

                                                                                                                              2. Open the client installation page.
                                                                                                                              3. Select a DB engine version, OS, and OS architecture, and run the following commands on the ECS to install a PostgreSQL client.

                                                                                                                                sudo yum install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
+sudo yum install -y postgresql12-server
                                                                                                                                +
                                                                                                                                Figure 1 Installing a client
                                                                                                                                +
                                                                                                                                • Select a DB engine version that is consistent with that of your RDS for PostgreSQL instance.
                                                                                                                                • Select an OS that is consistent with that of the ECS.
                                                                                                                                • Select an OS architecture that is consistent with that of the ECS.
                                                                                                                                +
                                                                                                                                Figure 2 Installing the RPM package
                                                                                                                                +
                                                                                                                                Figure 3 Client installed
                                                                                                                                +

                                                                                                                              4. Connect to the RDS for PostgreSQL instance.

                                                                                                                                Figure 4 Connection successful

                                                                                                                              diff --git a/docs/rds/umn/rds_faq_0050.html b/docs/rds/umn/rds_faq_0050.html index 47eca861..269971dc 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.

                                                                                                                              -

                                                                                                                              In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.

                                                                                                                              +

                                                                                                                              In the DB Information area on the Basic Information page, click in the SSL field to download the root certificate or certificate bundle.

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

                                                                                                                                jdbc:postgresql://<instance_ip>:<instance_port>/<database_name>?sslmode=verify-full&sslrootcert=<ca.pem>
                                                                                                                                diff --git a/docs/rds/umn/rds_faq_0051.html b/docs/rds/umn/rds_faq_0051.html index 712fda01..711dd2d9 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. In the DB Information area on the Basic Information page, click 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. In the DB Information area on the Basic Information page, click 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.

                                                                                                                                    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_0059.html b/docs/rds/umn/rds_faq_0059.html index 29edacaa..94bfcaef 100644 --- a/docs/rds/umn/rds_faq_0059.html +++ b/docs/rds/umn/rds_faq_0059.html @@ -6,7 +6,7 @@

                                                                                                                                  Example:

                                                                                                                                  EXEC master.dbo.rds_read_errorlog 0,1,'FZYUN','2018-06-14 14:30','2018-06-14 14:31'

                                                                                                                                  Figure 1 shows the query results.

                                                                                                                                  -
                                                                                                                                  Figure 1 Example query results
                                                                                                                                  +
                                                                                                                                  Figure 1 Example query results

                                                                                                                                diff --git a/docs/rds/umn/rds_faq_0065.html b/docs/rds/umn/rds_faq_0065.html index c110d19e..b938864f 100644 --- a/docs/rds/umn/rds_faq_0065.html +++ b/docs/rds/umn/rds_faq_0065.html @@ -5,11 +5,11 @@

                                                                                                                                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.
                                                                                                                                5. In the DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                  Alternatively, click in the DB instance topology on the Basic Information page to manually trigger a primary/standby switchover.

                                                                                                                                  +
                                                                                                                                  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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                    Alternatively, click in the DB instance topology on the Basic Information page to manually trigger a primary/standby switchover.

                                                                                                                                    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 Switch Primary/Standby Instances 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
                                                                                                                                    +

                                                                                                                                  8. 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_0094.html b/docs/rds/umn/rds_faq_0094.html index 023d7360..f667282d 100644 --- a/docs/rds/umn/rds_faq_0094.html +++ b/docs/rds/umn/rds_faq_0094.html @@ -4,7 +4,7 @@

                                                                                                                                Symptom

                                                                                                                                An error shown in Figure 1 is reported on SQL Server Management Studio when a database is being deleted from RDS SQL Server primary/standby DB instances.

                                                                                                                                The database 'xxxx' is enabled for database mirroring. Database mirroring must be removed before you drop the database. Error: 3743

                                                                                                                                -
                                                                                                                                Figure 1 Error information
                                                                                                                                +
                                                                                                                                Figure 1 Error information

                                                                                                                                Possible Causes

                                                                                                                                The error details indicate that the SQL Server DB instance type is primary/standby and database mirroring is enabled for the standby DB instance. As a result, the database cannot be deleted.

                                                                                                                                Solution

                                                                                                                                Before deleting the database, run the following commands to disable the mirroring:

                                                                                                                                diff --git a/docs/rds/umn/rds_faq_0100.html b/docs/rds/umn/rds_faq_0100.html index 609b9647..2b545a95 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 Basic Information and Backups & Restorations pages, check connection and backup information.
                                                                                                                                5. On the Basic Information 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 Basic Information and Backups & Restorations pages, check connection and backup information.
                                                                                                                                5. On the Basic Information 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 6db1a572..1a7aad6f 100644 --- a/docs/rds/umn/rds_faq_0119.html +++ b/docs/rds/umn/rds_faq_0119.html @@ -3,7 +3,7 @@

                                                                                                                                Does RDS for PostgreSQL Support the test_decoding Plugin?

                                                                                                                                PostgreSQL 10, PostgreSQL 11, PostgreSQL 12 and PostgreSQL 13 support test_decoding. 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.
                                                                                                                                +
                                                                                                                                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_modify_availability.html b/docs/rds/umn/rds_modify_availability.html index 4cf00c2e..b62eed8a 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 target primary/standby DB instances.
                                                                                                                                5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                6. View the results on the Basic Information 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 target primary/standby DB instances.
                                                                                                                                5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                6. View the results on the Basic Information page.
                                                                                                                                diff --git a/docs/rds/umn/rds_modify_instance_name.html b/docs/rds/umn/rds_modify_instance_name.html index 731824b8..915e639f 100644 --- a/docs/rds/umn/rds_modify_instance_name.html +++ b/docs/rds/umn/rds_modify_instance_name.html @@ -3,9 +3,9 @@

                                                                                                                                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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 .
                                                                                                                                    +
                                                                                                                                    • To submit the change, click .
                                                                                                                                    • To cancel the change, click .

                                                                                                                                  5. View the results on the Basic Information page.
                                                                                                                                diff --git a/docs/rds/umn/rds_mysql_error_log.html b/docs/rds/umn/rds_mysql_error_log.html index 044d29bb..184c0385 100644 --- a/docs/rds/umn/rds_mysql_error_log.html +++ b/docs/rds/umn/rds_mysql_error_log.html @@ -3,10 +3,10 @@

                                                                                                                                Viewing Error Logs

                                                                                                                                RDS log management allows you to view database-level logs, including error logs and slow SQL query logs.

                                                                                                                                Error logs contain warning- and error-level logs generated during the database running. These can help you analyze problems with the database.

                                                                                                                                -

                                                                                                                                Viewing Log Details

                                                                                                                                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 Logs. On the Error Logs page, view details about error logs.

                                                                                                                                  • You can select a log level in the upper right corner to view logs of the selected level.

                                                                                                                                    For MySQL DB instances, the following levels of logs are displayed:

                                                                                                                                    +

                                                                                                                                    Viewing Log Details

                                                                                                                                    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 Logs. On the Error Logs page, view details about error logs.

                                                                                                                                      • You can select a log level in the upper right corner to view logs of the selected level.

                                                                                                                                        For MySQL DB instances, the following levels of logs are displayed:

                                                                                                                                        • ERROR
                                                                                                                                        • WARNING
                                                                                                                                        • NOTE
                                                                                                                                        -
                                                                                                                                      • You can click in the upper right corner to view error logs generated in different time segments.
                                                                                                                                      • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
                                                                                                                                      +
                                                                                                                                    6. You can click in the upper right corner to view error logs generated in different time segments.
                                                                                                                                    7. If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.

                                                                                                                                diff --git a/docs/rds/umn/rds_mysql_recycle.html b/docs/rds/umn/rds_mysql_recycle.html index f4b0c7a0..3e27e95b 100644 --- a/docs/rds/umn/rds_mysql_recycle.html +++ b/docs/rds/umn/rds_mysql_recycle.html @@ -7,10 +7,10 @@

                                                                                                                                Modifying Recycling Policy

                                                                                                                                A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

                                                                                                                                -
                                                                                                                                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 navigation pane on the left, choose Recycling Management.
                                                                                                                                5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                6. Then, 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. In the navigation pane on the left, choose Recycling Management.
                                                                                                                                5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                6. Then, click OK.

                                                                                                                                Rebuilding a DB Instance

                                                                                                                                You can rebuild the primary DB instances in the recycle bin within the retention period.

                                                                                                                                -
                                                                                                                                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 navigation pane on the left, choose Recycling Management.
                                                                                                                                5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                +
                                                                                                                                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 navigation pane on the left, choose Recycling Management.
                                                                                                                                5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                diff --git a/docs/rds/umn/rds_mysql_slow_query_log.html b/docs/rds/umn/rds_mysql_slow_query_log.html index 43e51be4..934f1d83 100644 --- a/docs/rds/umn/rds_mysql_slow_query_log.html +++ b/docs/rds/umn/rds_mysql_slow_query_log.html @@ -5,7 +5,7 @@
                                                                                                                                RDS supports the following statement types:
                                                                                                                                • SELECT
                                                                                                                                • INSERT
                                                                                                                                • UPDATE
                                                                                                                                • DELETE
                                                                                                                                • CREATE
                                                                                                                                -

                                                                                                                                Viewing Log Details

                                                                                                                                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 Logs. On the Slow Query Logs page, view details about slow query logs.

                                                                                                                                  • You can view the slow query log records of a specified execution statement type or a specific time period.
                                                                                                                                  • The long_query_time parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If long_query_time is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.
                                                                                                                                  +

                                                                                                                                  Viewing Log Details

                                                                                                                                  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 Logs. On the Slow Query Logs page, view details about slow query logs.

                                                                                                                                    • You can view the slow query log records of a specified execution statement type or a specific time period.
                                                                                                                                    • The long_query_time parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If long_query_time is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.

                                                                                                                                diff --git a/docs/rds/umn/rds_pg_05_0001.html b/docs/rds/umn/rds_pg_05_0001.html index 855972b7..ea3eb0af 100644 --- a/docs/rds/umn/rds_pg_05_0001.html +++ b/docs/rds/umn/rds_pg_05_0001.html @@ -8,6 +8,8 @@
                                                                                                                                diff --git a/docs/rds/umn/rds_pg_05_0003.html b/docs/rds/umn/rds_pg_05_0003.html new file mode 100644 index 00000000..6dc30029 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0003.html @@ -0,0 +1,21 @@ + + +

                                                                                                                                Upgrading a Minor Version

                                                                                                                                +

                                                                                                                                Scenarios

                                                                                                                                RDS for PostgreSQL supports minor version upgrades to improve performance, add new functions, and fix bugs.

                                                                                                                                +
                                                                                                                                +

                                                                                                                                Precautions

                                                                                                                                • When any new minor version is released to address vulnerabilities and other issues from the open source community, perform a minor version upgrade for your instance.
                                                                                                                                • The upgrade will cause the instance to reboot and interrupt services for a period of time. The length of the interruption depends on service volume. To minimize the impact of the upgrade, perform the upgrade during off-peak hours, or ensure that your applications support automatic reconnection.
                                                                                                                                • When you upgrade the minor version of a primary instance, the minor versions of read replicas (if any) will also be upgraded automatically. Read replicas cannot be upgraded separately.
                                                                                                                                • A minor version upgrade cannot be rolled back after the upgrade is complete. If the upgrade fails, the DB instance will be automatically rolled back to the source version.
                                                                                                                                • You are advised to perform a full backup before upgrading a minor version.
                                                                                                                                • You need to re-establish a DR relationship after upgrading the minor version of a DR instance.
                                                                                                                                • Before upgrading minor versions earlier than RDS for PostgreSQL 12.6, you need to stop all logical replications and delete all logical replication slots. Otherwise, the upgrade will fail.
                                                                                                                                  • Querying a replication slot: select * from pg_replication_slots;
                                                                                                                                  • Deleting a replication slot: select pg_drop_replication_slot('SLOT_NAME');
                                                                                                                                  +
                                                                                                                                +
                                                                                                                                +

                                                                                                                                Constraints

                                                                                                                                • The minor version cannot be upgraded for instances with abnormal nodes.
                                                                                                                                • The following minor versions cannot be upgraded:
                                                                                                                                  • Versions earlier than 11.2 for RDS for PostgreSQL 11
                                                                                                                                  +
                                                                                                                                • 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.
                                                                                                                                5. In the DB Information area on the Basic Information page, click Upgrade Minor Version next to the DB Engine Version field.
                                                                                                                                6. In the displayed dialog box, click OK.

                                                                                                                                  RDS upgrades the minor version to the latest version immediately.

                                                                                                                                  +

                                                                                                                                +
                                                                                                                                +
                                                                                                                                +
                                                                                                                                +
                                                                                                                                +
                                                                                                                                Parent topic: Instance Modifications
                                                                                                                                +
                                                                                                                                +
                                                                                                                                + diff --git a/docs/rds/umn/rds_pg_05_0017.html b/docs/rds/umn/rds_pg_05_0017.html index 7c74f132..b3a3d73e 100644 --- a/docs/rds/umn/rds_pg_05_0017.html +++ b/docs/rds/umn/rds_pg_05_0017.html @@ -3,9 +3,9 @@

                                                                                                                                Exporting DB Instance Information

                                                                                                                                Scenarios

                                                                                                                                You can export information about all or selected DB instances to view and analyze DB instance information.

                                                                                                                                -

                                                                                                                                Exporting Information About All DB Instances

                                                                                                                                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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                                                                                                                5. Find a .csv file locally after the export task is completed.
                                                                                                                                +

                                                                                                                                Exporting Information About All DB Instances

                                                                                                                                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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                                                                                                                5. Find a .csv file locally after the export task is completed.
                                                                                                                                -

                                                                                                                                Exporting Information About Selected DB Instances

                                                                                                                                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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                                                                                                                5. Find a .csv file locally after the export task is completed.
                                                                                                                                +

                                                                                                                                Exporting Information About Selected DB Instances

                                                                                                                                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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                                                                                                                5. Find a .csv file locally after the export task is completed.
                                                                                                                                diff --git a/docs/rds/umn/rds_pg_05_0018.html b/docs/rds/umn/rds_pg_05_0018.html index 86ce548f..434a0470 100644 --- a/docs/rds/umn/rds_pg_05_0018.html +++ b/docs/rds/umn/rds_pg_05_0018.html @@ -3,7 +3,7 @@

                                                                                                                                Applying a Parameter Template

                                                                                                                                Scenarios

                                                                                                                                You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.

                                                                                                                                -

                                                                                                                                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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                                                                                                                  • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                                                                                                                  • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
                                                                                                                                  +

                                                                                                                                  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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                                                                                                                    • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                                                                                                                    • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.

                                                                                                                                    A parameter template can be applied to one or more DB instances.

                                                                                                                                  5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

                                                                                                                                    After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

                                                                                                                                  diff --git a/docs/rds/umn/rds_pg_05_0023.html b/docs/rds/umn/rds_pg_05_0023.html index 4c76f281..64f00a78 100644 --- a/docs/rds/umn/rds_pg_05_0023.html +++ b/docs/rds/umn/rds_pg_05_0023.html @@ -3,8 +3,8 @@

                                                                                                                                  Changing a DB Instance Type from Single to Primary/Standby

                                                                                                                                  Scenarios

                                                                                                                                  • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.
                                                                                                                                  • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
                                                                                                                                  • Anti-affinity deployment is supported for primary/standby DB instances to prevent the entire instance unavailability due to the failure of a single host.
                                                                                                                                  -

                                                                                                                                  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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                                                                                                    Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                                                                                                    -

                                                                                                                                  5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                                                                                                                  6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                                                                                                    • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
                                                                                                                                    +

                                                                                                                                    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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                                                                                                      Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                                                                                                      +

                                                                                                                                    5. Select a standby AZ. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                                                                                                                    6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                                                                                                      • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.

                                                                                                                                  diff --git a/docs/rds/umn/rds_pg_05_0024.html b/docs/rds/umn/rds_pg_05_0024.html index 996fd1ac..78423da0 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.
                                                                                                                                  5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                                                                                                                  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.
                                                                                                                                    5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                                                                                                                    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_0034.html b/docs/rds/umn/rds_pg_05_0034.html index 2c2b9ad3..094cc671 100644 --- a/docs/rds/umn/rds_pg_05_0034.html +++ b/docs/rds/umn/rds_pg_05_0034.html @@ -16,8 +16,6 @@
                                                                                                                                5. Restoring from Backup Files to RDS for PostgreSQL
                                                                                                                                  6. -
                                                                                                                                6. Restoring from Full Backup Files to a Self-Built PostgreSQL Database
                                                                                                                                  -
                                                                                                                                7. Restoring a DB Instance to a Point in Time
                                                                                                                                8. Replicating a Backup
                                                                                                                                  diff --git a/docs/rds/umn/rds_pg_05_0038.html b/docs/rds/umn/rds_pg_05_0038.html index 129c2fa2..b33d4024 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. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
                                                                                                                                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. In the DB Information area on the Basic Information page, click Change in the Maintenance Window field.
                                                                                                                                  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_0055.html b/docs/rds/umn/rds_pg_05_0055.html index 7205d2c9..def2f8a2 100644 --- a/docs/rds/umn/rds_pg_05_0055.html +++ b/docs/rds/umn/rds_pg_05_0055.html @@ -5,7 +5,7 @@
                                                                                                                                  • You can create DB instances with the same configurations numerous times.
                                                                                                                                  • This function is unavailable for read replicas.
                                                                                                                                  -

                                                                                                                                  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 > Create Same DB Instance in the Operation column.
                                                                                                                                  5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

                                                                                                                                    For details about PostgreSQL DB instance configurations, see section Step 1: Create a 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 > Create Same DB Instance in the Operation column.
                                                                                                                                    5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

                                                                                                                                      For details about PostgreSQL DB instance configurations, see section Step 1: Create a DB Instance.

                                                                                                                                    6. Confirm the instance specifications.

                                                                                                                                    7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

                                                                                                                                      You can manage the DB instance on the Instances page.

                                                                                                                                    diff --git a/docs/rds/umn/rds_pg_05_0060.html b/docs/rds/umn/rds_pg_05_0060.html new file mode 100644 index 00000000..51250b60 --- /dev/null +++ b/docs/rds/umn/rds_pg_05_0060.html @@ -0,0 +1,18 @@ + + +

                                                                                                                                    Migrating a Standby DB Instance

                                                                                                                                    +

                                                                                                                                    Scenarios

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

                                                                                                                                    +
                                                                                                                                    • 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 DB Instance 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.
                                                                                                                                      • In the DB Information area on the Basic Information page, you can view the AZ hosting the standby DB instance.
                                                                                                                                      +

                                                                                                                                    +
                                                                                                                                    +

                                                                                                                                    +
                                                                                                                                    +
                                                                                                                                    +
                                                                                                                                    +
                                                                                                                                    Parent topic: Instance Modifications
                                                                                                                                    +
                                                                                                                                    +
                                                                                                                                    + diff --git a/docs/rds/umn/rds_pg_05_0098.html b/docs/rds/umn/rds_pg_05_0098.html index 8b13a6f6..57815262 100644 --- a/docs/rds/umn/rds_pg_05_0098.html +++ b/docs/rds/umn/rds_pg_05_0098.html @@ -3,7 +3,7 @@

                                                                                                                                    Viewing Application Records of a Parameter Template

                                                                                                                                    Scenarios

                                                                                                                                    You can view the application records of a parameter template.

                                                                                                                                    -

                                                                                                                                    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. Choose Parameter Template Management in the navigation pane on the left.
                                                                                                                                    5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                                                                                                      You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                                                                                                      +

                                                                                                                                      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. Choose Parameter Template Management in the navigation pane on the left.
                                                                                                                                      5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                                                                                                        You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                                                                                                    diff --git a/docs/rds/umn/rds_pg_05_0099.html b/docs/rds/umn/rds_pg_05_0099.html index d48357d7..ee2c21b0 100644 --- a/docs/rds/umn/rds_pg_05_0099.html +++ b/docs/rds/umn/rds_pg_05_0099.html @@ -5,11 +5,11 @@

                                                                                                                                    An exported or custom parameter template has initially a blank change history.

                                                                                                                                    -

                                                                                                                                    Viewing Change History of 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.
                                                                                                                                    5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                                                                                                      You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                                                                                                      +

                                                                                                                                      Viewing Change History of 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.
                                                                                                                                      5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                                                                                                        You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                                                                                                        You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

                                                                                                                                      -

                                                                                                                                      Viewing Change History of a Parameter Template

                                                                                                                                      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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                      5. On the displayed page, choose Change History in the navigation pane on the left.

                                                                                                                                        You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                                                                                                        +

                                                                                                                                        Viewing Change History of a Parameter Template

                                                                                                                                        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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                        5. On the displayed page, choose Change History in the navigation pane on the left.

                                                                                                                                          You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_05_0138.html b/docs/rds/umn/rds_pg_05_0138.html index 51003fc6..1b2d865c 100644 --- a/docs/rds/umn/rds_pg_05_0138.html +++ b/docs/rds/umn/rds_pg_05_0138.html @@ -4,7 +4,7 @@

                                                                                                                                      Scenarios

                                                                                                                                      This section describes how to download a manual or an automated backup file to a local device and restore data from the backup file.

                                                                                                                                      RDS for PostgreSQL enables you to download incremental backup files.

                                                                                                                                      -

                                                                                                                                      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. Choose Backups & Restorations in the navigation pane on the left. On the Incremental Backups page, locate the target backup to be downloaded and click Download in the Operation column.

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

                                                                                                                                        +

                                                                                                                                        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. Choose Backups & Restorations in the navigation pane on the left. On the Incremental Backups page, locate the target backup to be downloaded and click Download in the Operation column.

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

                                                                                                                                        5. After the download is complete, you can view the incremental backups locally.
                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_06_0003.html b/docs/rds/umn/rds_pg_06_0003.html index 80c3a5b6..28f22114 100644 --- a/docs/rds/umn/rds_pg_06_0003.html +++ b/docs/rds/umn/rds_pg_06_0003.html @@ -11,7 +11,7 @@
                                                                                                                                      • RDS has been running properly for about 10 minutes.

                                                                                                                                        For a newly created RDS DB instance, you need to wait a bit before you can view the 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                                                                                                        Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                                                                                                          Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

                                                                                                                                        5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

                                                                                                                                          Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

                                                                                                                                        diff --git a/docs/rds/umn/rds_pg_06_0005.html b/docs/rds/umn/rds_pg_06_0005.html index ccc62bf8..c873c62d 100644 --- a/docs/rds/umn/rds_pg_06_0005.html +++ b/docs/rds/umn/rds_pg_06_0005.html @@ -6,7 +6,7 @@

                                                                                                                                      Procedure

                                                                                                                                      1. Log in to the management console.
                                                                                                                                      2. Choose Management & Governance > Cloud Trace Service.
                                                                                                                                      3. Choose Trace List in the navigation pane on the left.
                                                                                                                                      4. Filter conditions to query traces. The details are described as follows:

                                                                                                                                        • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

                                                                                                                                          When you select Resource ID for Search By, you also need to select or enter a resource ID.

                                                                                                                                        • Operator: Select a specific operator from the drop-down list.
                                                                                                                                        • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
                                                                                                                                        • In the upper right corner of the page, you can specify a time range for querying traces.
                                                                                                                                        -

                                                                                                                                      5. Select the search criteria, and click Query.
                                                                                                                                      6. Click on the left of the required trace to expand its details.
                                                                                                                                      7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                                                                                                      8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                                                                                                        For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                                                                                                                        +

                                                                                                                                      9. Select the search criteria, and click Query.
                                                                                                                                      10. Click on the left of the required trace to expand its details.
                                                                                                                                      11. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                                                                                                      12. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                                                                                                        For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                                                                                                                    diff --git a/docs/rds/umn/rds_pg_06_0022.html b/docs/rds/umn/rds_pg_06_0022.html index e0c064e1..d7060acb 100644 --- a/docs/rds/umn/rds_pg_06_0022.html +++ b/docs/rds/umn/rds_pg_06_0022.html @@ -3,7 +3,7 @@

                                                                                                                                    Selecting Displayed Items

                                                                                                                                    Scenarios

                                                                                                                                    You can customize which instance items are displayed on the Instances 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 to edit columns displayed in the DB instance list.

                                                                                                                                      • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                                                                                        These default items cannot be deselected.

                                                                                                                                        +

                                                                                                                                        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 to edit columns displayed in the DB instance list.

                                                                                                                                          • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                                                                                            These default items cannot be deselected.

                                                                                                                                          • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.

                                                                                                                                        diff --git a/docs/rds/umn/rds_pg_07_0000.html b/docs/rds/umn/rds_pg_07_0000.html new file mode 100644 index 00000000..ca5b7e33 --- /dev/null +++ b/docs/rds/umn/rds_pg_07_0000.html @@ -0,0 +1,17 @@ + + +

                                                                                                                                        Permissions Management

                                                                                                                                        +
                                                                                                                                        + + diff --git a/docs/rds/umn/rds_pg_07_0002.html b/docs/rds/umn/rds_pg_07_0002.html new file mode 100644 index 00000000..0d5d2c03 --- /dev/null +++ b/docs/rds/umn/rds_pg_07_0002.html @@ -0,0 +1,26 @@ + + +

                                                                                                                                        Creating a User and Granting Permissions

                                                                                                                                        +

                                                                                                                                        This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:

                                                                                                                                        +
                                                                                                                                        • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing RDS resources.
                                                                                                                                        • Grant only the permissions required for users to perform a specific task.
                                                                                                                                        • Entrust a account or cloud service to perform efficient O&M on your RDS resources.
                                                                                                                                        +

                                                                                                                                        If your account does not require individual IAM users, skip this chapter.

                                                                                                                                        +

                                                                                                                                        This section describes the procedure for granting permissions (see Figure 1).

                                                                                                                                        +

                                                                                                                                        Prerequisites

                                                                                                                                        Learn about the permissions (see Permissions Management) supported by RDS and choose policies or roles according to your requirements.For the system policies of other services, see Permissions.

                                                                                                                                        +
                                                                                                                                        +

                                                                                                                                        Process Flow

                                                                                                                                        Figure 1 Process for granting RDS permissions
                                                                                                                                        +
                                                                                                                                        1. Create a user group and assign permissions to it.

                                                                                                                                          Create a user group on the IAM console, and attach the RDS ReadOnlyAccess policy to the group.

                                                                                                                                          +

                                                                                                                                          To use some interconnected services, you also need to configure permissions of such services.

                                                                                                                                          +

                                                                                                                                          For example, to connect to your DB instance through the console, configure the DAS FullAccess permission of Data Admin Service (DAS) besides RDS ReadOnlyAccess.

                                                                                                                                          +
                                                                                                                                          +
                                                                                                                                        2. Create an IAM user and add it to the user group.

                                                                                                                                          Create a user on the IAM console and add the user to the group created in 1.

                                                                                                                                          +
                                                                                                                                        3. Log in and verify permissions.

                                                                                                                                          Log in to the RDS console by using the created user, and verify that the user only has read permissions for RDS.

                                                                                                                                          +
                                                                                                                                          • Choose Service List > Relational Database Service and click Buy DB Instance. If a message appears indicating that you have insufficient permissions to perform the operation, the RDS ReadOnlyAccess policy has already been applied.
                                                                                                                                          • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the RDS ReadOnlyAccess policy has already taken effect.
                                                                                                                                          +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        Parent topic: Permissions Management
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        + diff --git a/docs/rds/umn/rds_pg_07_0003.html b/docs/rds/umn/rds_pg_07_0003.html new file mode 100644 index 00000000..b7160b0a --- /dev/null +++ b/docs/rds/umn/rds_pg_07_0003.html @@ -0,0 +1,32 @@ + + +

                                                                                                                                        RDS Custom Policies

                                                                                                                                        +

                                                                                                                                        Custom policies can be created to supplement the system policies of RDS.

                                                                                                                                        +

                                                                                                                                        You can create custom policies in either of the following two ways:

                                                                                                                                        +
                                                                                                                                        • Visual editor: Select cloud services, actions, resources, and request conditions without the need to know policy syntax.
                                                                                                                                        • JSON: Edit JSON policies from scratch or based on an existing policy.
                                                                                                                                        +

                                                                                                                                        For details, see Creating a Custom Policy. The following section contains examples of common RDS custom policies.

                                                                                                                                        +

                                                                                                                                        Example Custom Policies

                                                                                                                                        • Example 1: Allowing users to create RDS DB instances
                                                                                                                                          {
+	"Version": "1.1",
+	"Statement": [{
+		"Effect": "Allow",
+		"Action": ["rds:instance:create"]
+	}]
+}
                                                                                                                                          +
                                                                                                                                        • Example 2: Denying RDS DB instance deletion

                                                                                                                                          A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user include both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

                                                                                                                                          +

                                                                                                                                          The following method can be used if you need to assign permissions of the RDS FullAccess policy to a user but you want to prevent the user from deleting RDS DB instances. Create a custom policy for denying RDS DB instance deletion, and attach both policies to the group the user belongs to. Then, the user can perform all operations on RDS DB instances except deleting RDS DB instances. The following is an example deny policy:

                                                                                                                                          +
                                                                                                                                          {
+	"Version": "1.1",
+	"Statement": [{
+		"Action": ["rds:instance:delete"],
+		"Effect": "Deny"
+	}]
+}
                                                                                                                                          +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        Parent topic: Permissions Management
                                                                                                                                        +
                                                                                                                                        +
                                                                                                                                        + diff --git a/docs/rds/umn/rds_pg_08_0042.html b/docs/rds/umn/rds_pg_08_0042.html index 156ab0c2..562a415d 100644 --- a/docs/rds/umn/rds_pg_08_0042.html +++ b/docs/rds/umn/rds_pg_08_0042.html @@ -3,7 +3,7 @@

                                                                                                                                        Exporting a Parameter Template

                                                                                                                                        Scenarios

                                                                                                                                        • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
                                                                                                                                        • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
                                                                                                                                        -

                                                                                                                                        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.
                                                                                                                                        5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                                                                                          • Exporting to a custom template
                                                                                                                                            In the displayed dialog box, configure required information and click OK.
                                                                                                                                            • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                            • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                                                                            +

                                                                                                                                            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.
                                                                                                                                            5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                                                                                              • Exporting to a custom template
                                                                                                                                                In the displayed dialog box, configure required information and click OK.
                                                                                                                                                • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                                                                                After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

                                                                                                                                                diff --git a/docs/rds/umn/rds_pg_08_0044.html b/docs/rds/umn/rds_pg_08_0044.html deleted file mode 100644 index 16a44eb9..00000000 --- a/docs/rds/umn/rds_pg_08_0044.html +++ /dev/null @@ -1,23 +0,0 @@ - - -

                                                                                                                                                Restoring from Full Backup Files to a Self-Built PostgreSQL Database

                                                                                                                                                -

                                                                                                                                                You can download backup files by referring to Downloading a Full Backup File and restore data from them.

                                                                                                                                                -

                                                                                                                                                Prerequisites

                                                                                                                                                1. A tool for decompressing TAR files must be installed in a Unix-like system.
                                                                                                                                                2. Either python2.7 or python3 can be used.
                                                                                                                                                3. The following third-party packages need to be installed: lz4, gzip, and shutil.
                                                                                                                                                4. The version of the local database must be the same as that of the cloud database.
                                                                                                                                                5. Plugins of the same version as the cloud database are installed in the local database.
                                                                                                                                                -
                                                                                                                                                -

                                                                                                                                                Procedure

                                                                                                                                                1. Prepare a local directory for storing tablespaces.
                                                                                                                                                2. Stop the local database server.
                                                                                                                                                3. Store the following configuration files in the data directory of the local database to another directory: postgresql.conf, pg_hba.conf, and recovery.done.
                                                                                                                                                4. Clear the data directory of the local database.
                                                                                                                                                5. Download the decompression tool.
                                                                                                                                                6. Run the following command to decompress backup files to the directory prepared in Step 1:

                                                                                                                                                  python restore_obs_file.py src_file target_dir

                                                                                                                                                  -

                                                                                                                                                  Variables in the command are described as follows:

                                                                                                                                                  -

                                                                                                                                                  src_file: indicates the directory where PostgreSQL full backup files are stored.

                                                                                                                                                  -

                                                                                                                                                  target_dir: indicates the directory to which data is restored. The directory has been prepared in 1. The directory must be empty. If the directory does not exist, the system automatically creates it.

                                                                                                                                                  -

                                                                                                                                                  The following directories are generated after the decompression:

                                                                                                                                                  -
                                                                                                                                                  • data: stores full backup data. The recovery.done file has been deleted.
                                                                                                                                                  • xlog: stores incremental backup data.
                                                                                                                                                  • tblspc: stores tablespace directory files (if the original backup contains tablespace files).
                                                                                                                                                  -

                                                                                                                                                7. Copy the files in 6 to the specified directory of the local database.

                                                                                                                                                  1. Copy all the decompressed files in the data directory to the data directory of the local database, and then replace the three files in the data directory of the local database with the configuration files saved in step 3.
                                                                                                                                                  2. Copy the decompressed files in the xlog directory to the pg_xlog or pg_wal folder in the data directory of the local database. (The folder names vary according to database versions.)
                                                                                                                                                  3. Move the decompressed tablespace folder (if any) in the tblspc directory to the tablespace directory created in step 1 and modify the soft link of the corresponding tablespace in data\tablespace_map.

                                                                                                                                                    -
                                                                                                                                                  -

                                                                                                                                                8. Reboot the database and wait until the database restoration is complete.
                                                                                                                                                -
                                                                                                                                                -
                                                                                                                                                -
                                                                                                                                                -
                                                                                                                                                -
                                                                                                                                                Parent topic: Backups and Restorations
                                                                                                                                                -
                                                                                                                                                -
                                                                                                                                                - diff --git a/docs/rds/umn/rds_pg_10_0001.html b/docs/rds/umn/rds_pg_10_0001.html index 65e0ad84..047d7940 100644 --- a/docs/rds/umn/rds_pg_10_0001.html +++ b/docs/rds/umn/rds_pg_10_0001.html @@ -4,8 +4,7 @@

                                                                                                                                                Parameters are key configuration items in a database system. Improper parameter settings may adversely affect the stable running of databases. This section describes some important parameters for your reference. For details, visit the PostgreSQL official website.

                                                                                                                                                For details on how to modify PostgreSQL parameters on the console, see Modifying Instance Parameters.

                                                                                                                                                Sensitive Parameters

                                                                                                                                                The following parameters can result in system security and stability issues if set improperly:

                                                                                                                                                -
                                                                                                                                                • The search_path parameter must be set to a schema sequence where schemas are separated by commas (,). Ensure that the schemas exist. Otherwise, the database performance will be affected.
                                                                                                                                                • If you enable the parameter log_duration, SQL statements containing sensitive information may be recorded in logs. You are advised to disable this parameter.
                                                                                                                                                • log_min_duration_statement specifies how many milliseconds a query has to run before it has to be logged. The unit is millisecond. Setting this parameter to 0 means that all statements are recorded. Setting this parameter to -1 means that no statement is recorded. For details, see Viewing Slow Query Logs.
                                                                                                                                                • The parameters nls_timestamp_format and nls_date_format control the input and output formats of timestamp and date. They are available only for PostgreSQL Enhanced Edition.
                                                                                                                                                  • The nls_timestamp_format parameter defines the timestamp format. The nls_date_format defines the date format.
                                                                                                                                                  -
                                                                                                                                                • The temp_file_limit parameter specifies the maximum amount of disk space (in KB) that a session can use for temporary files. It supports PostgreSQL 11, 12, and 13 only. Changing this parameter value is a high-risk operation. Exercise caution when deciding to perform this operation.
                                                                                                                                                  • If the parameter value exceeds the threshold, the DB instance will become unavailable.
                                                                                                                                                  • If the parameter value is changed to a larger value for temporary use but is not changed to the original value after the use, the disk space will be continuously used to store temporary files. If the disk space is used up, services will be interrupted and the DB instance will become unavailable.
                                                                                                                                                  +
                                                                                                                                                  • The search_path parameter must be set to a schema sequence where schemas are separated by commas (,). Ensure that the schemas exist. Otherwise, the database performance will be affected.
                                                                                                                                                  • If you enable the parameter log_duration, SQL statements containing sensitive information may be recorded in logs. You are advised to disable this parameter.
                                                                                                                                                  • log_min_duration_statement specifies how many milliseconds a query has to run before it has to be logged. The unit is millisecond. Setting this parameter to 0 means that all statements are recorded. Setting this parameter to -1 means that no statement is recorded. For details, see Viewing Slow Query Logs.
                                                                                                                                                  • The temp_file_limit parameter specifies the maximum amount of disk space (in KB) that a session can use for temporary files. It supports PostgreSQL 11, 12, 13 and 14 only. Changing this parameter value is a high-risk operation. Exercise caution when deciding to perform this operation.
                                                                                                                                                    • If the parameter value exceeds the threshold, the DB instance will become unavailable.
                                                                                                                                                    • If the parameter value is changed to a larger value for temporary use but is not changed to the original value after the use, the disk space will be continuously used to store temporary files. If the disk space is used up, services will be interrupted and the DB instance will become unavailable.

                                                                                                                                                Performance Parameters

                                                                                                                                                The following parameters can affect database performance:

                                                                                                                                                diff --git a/docs/rds/umn/rds_pg_11_0004.html b/docs/rds/umn/rds_pg_11_0004.html index 2000a19f..bb46d612 100644 --- a/docs/rds/umn/rds_pg_11_0004.html +++ b/docs/rds/umn/rds_pg_11_0004.html @@ -1,11 +1,11 @@

                                                                                                                                                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 Basic Information 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 Basic Information page.
                                                                                                                                                -

                                                                                                                                                Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                                                                5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                                                                +

                                                                                                                                                Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                                                                5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                                                                -

                                                                                                                                                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.
                                                                                                                                                +

                                                                                                                                                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 63fcfc6e..e88bf026 100644 --- a/docs/rds/umn/rds_pg_11_0005.html +++ b/docs/rds/umn/rds_pg_11_0005.html @@ -10,11 +10,11 @@
                                                                                                                                              • Install the pgAdmin client on the prepared ECS or device.
                                                                                                                                            -

                                                                                                                                            Procedure

                                                                                                                                            1. Start pgAdmin.
                                                                                                                                            2. In the displayed login window, choose Servers > Create > Server.

                                                                                                                                              Figure 1 Creation
                                                                                                                                              +

                                                                                                                                              Procedure

                                                                                                                                              1. Start pgAdmin.
                                                                                                                                              2. In the displayed login window, choose Servers > Create > Server.

                                                                                                                                                Figure 1 Creation

                                                                                                                                                -

                                                                                                                                              3. On the General page, specify Name. On the Connection page, specify information about the DB instance to be connected. Then, click Save.

                                                                                                                                                Figure 2 General page
                                                                                                                                                +

                                                                                                                                              4. On the General page, specify Name. On the Connection page, specify information about the DB instance to be connected. Then, click Save.

                                                                                                                                                Figure 2 General page

                                                                                                                                                -
                                                                                                                                                Figure 3 Connection page
                                                                                                                                                +
                                                                                                                                                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 Connection Information area on the Basic Information 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.

                                                                                                                                              5. In the login window, check that the connection information is correct. The target DB instance is successfully connected.
                                                                                                                                              diff --git a/docs/rds/umn/rds_pg_change_database_port.html b/docs/rds/umn/rds_pg_change_database_port.html index 86c66928..32a847a9 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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                                                                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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                                                                  A PostgreSQL database can use ports 2100 to 9500.

                                                                                                                                                  -
                                                                                                                                                  • To submit the change, click .
                                                                                                                                                    • In the dialog box, click Yes.
                                                                                                                                                      1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                                                      2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
                                                                                                                                                      3. This process takes 1-5 minutes.
                                                                                                                                                      +
                                                                                                                                                      • To submit the change, click .
                                                                                                                                                        • In the dialog box, click Yes.
                                                                                                                                                          1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                                                          2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will be rebooted.
                                                                                                                                                          3. This process takes 1-5 minutes.
                                                                                                                                                        • In the dialog box, click No to cancel the modification.
                                                                                                                                                        -
                                                                                                                                                      • To cancel the change, click .
                                                                                                                                                      +
                                                                                                                                                    • To cancel the change, click .

                                                                                                                                                  • View the results on the Basic Information page.
                                                                                                                                                diff --git a/docs/rds/umn/rds_pg_configuration.html b/docs/rds/umn/rds_pg_configuration.html index 0159ef54..87fbab4f 100644 --- a/docs/rds/umn/rds_pg_configuration.html +++ b/docs/rds/umn/rds_pg_configuration.html @@ -7,7 +7,7 @@

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

                                                                                                                                                RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

                                                                                                                                                -

                                                                                                                                                Modifying Parameters of 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.
                                                                                                                                                5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

                                                                                                                                                  Available operations are Save, Cancel, and Preview:

                                                                                                                                                  +

                                                                                                                                                  Modifying Parameters of 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.
                                                                                                                                                  5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

                                                                                                                                                    Available operations are Save, Cancel, and Preview:

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

                                                                                                                                                    After parameters are modified, you can view parameter change history by referring to section Viewing Parameter Change History.

                                                                                                                                                  -

                                                                                                                                                  Modifying Parameter Template Parameters

                                                                                                                                                  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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                  5. On the Parameters page, modify parameters as required.

                                                                                                                                                    Available operations are Save, Cancel, and Preview:

                                                                                                                                                    +

                                                                                                                                                    Modifying Parameter Template Parameters

                                                                                                                                                    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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                    5. On the Parameters page, modify parameters as required.

                                                                                                                                                      Available operations are Save, Cancel, and Preview:

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

                                                                                                                                                    6. After the parameter values are modified, you can click View Change History to view the modification details.
                                                                                                                                                    7. The modifications take effect only after you apply the parameter template to DB instances. For details, see Applying a Parameter Template.
                                                                                                                                                    8. View the status of the DB instance to which the parameter template was applied.

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

                                                                                                                                                      • A DB instance reboot caused by instance class changes will not make parameter modifications take effect.
                                                                                                                                                      • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
                                                                                                                                                      • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_modify_availability.html b/docs/rds/umn/rds_pg_modify_availability.html index 645a4161..62ebd2be 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 target primary/standby DB instances.
                                                                                                                                                      5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                                      6. View the results on the Basic Information 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 target primary/standby DB instances.
                                                                                                                                                      5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                                      6. View the results on the Basic Information page.
                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_modify_instance_name.html b/docs/rds/umn/rds_pg_modify_instance_name.html index f86decad..ed3b3418 100644 --- a/docs/rds/umn/rds_pg_modify_instance_name.html +++ b/docs/rds/umn/rds_pg_modify_instance_name.html @@ -3,9 +3,9 @@

                                                                                                                                                      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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 .
                                                                                                                                                          +
                                                                                                                                                          • To submit the change, click .
                                                                                                                                                          • To cancel the change, click .

                                                                                                                                                        5. View the results on the Basic Information page.
                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_parameter_group.html b/docs/rds/umn/rds_pg_parameter_group.html index 3d57a43e..a615ab7f 100644 --- a/docs/rds/umn/rds_pg_parameter_group.html +++ b/docs/rds/umn/rds_pg_parameter_group.html @@ -8,11 +8,11 @@

                                                                                                                                                      If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

                                                                                                                                                      When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

                                                                                                                                                      The following are the key points you should know when using parameters in a parameter template:

                                                                                                                                                      -
                                                                                                                                                      • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
                                                                                                                                                      • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
                                                                                                                                                      +
                                                                                                                                                      • The changes to parameter values in a custom parameter template take effect only after you apply the template to DB instances. For details, see Applying a Parameter Template.
                                                                                                                                                      • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.

                                                                                                                                                      RDS does not share parameter template quotas with DDS.

                                                                                                                                                      You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

                                                                                                                                                      -

                                                                                                                                                      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 Parameter Template Management page, click Create Parameter Template.
                                                                                                                                                      5. In the displayed dialog box, configure required information and click OK.

                                                                                                                                                        • Select a DB engine for the parameter template.
                                                                                                                                                        • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                                                                                        +

                                                                                                                                                        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 Parameter Template Management page, click Create Parameter Template.
                                                                                                                                                        5. In the displayed dialog box, configure required information and click OK.

                                                                                                                                                          • Select a DB engine for the parameter template.
                                                                                                                                                          • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                          • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_public_accessibility.html b/docs/rds/umn/rds_pg_public_accessibility.html index 1eec51bb..d589f20b 100644 --- a/docs/rds/umn/rds_pg_public_accessibility.html +++ b/docs/rds/umn/rds_pg_public_accessibility.html @@ -7,11 +7,11 @@

                                                                                                                                                      Prerequisites

                                                                                                                                                      • You have assigned an EIP on the VPC console.
                                                                                                                                                      • You can bind an EIP to a primary DB instance or a read replica only.
                                                                                                                                                      • If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
                                                                                                                                                      -

                                                                                                                                                      Binding an EIP

                                                                                                                                                      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 EIPs page, click Bind EIP.
                                                                                                                                                      6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
                                                                                                                                                      7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

                                                                                                                                                        You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                        +

                                                                                                                                                        Binding an EIP

                                                                                                                                                        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 EIPs page, click Bind EIP.
                                                                                                                                                        6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
                                                                                                                                                        7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

                                                                                                                                                          You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                          To unbind the EIP from the DB instance, see Unbinding an EIP.

                                                                                                                                                        -

                                                                                                                                                        Unbinding an EIP

                                                                                                                                                        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 that has an EIP bound.
                                                                                                                                                        5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                        6. On the EIPs page, view the unbinding result.

                                                                                                                                                          You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                          +

                                                                                                                                                          Unbinding an EIP

                                                                                                                                                          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 that has an EIP bound.
                                                                                                                                                          5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                          6. On the EIPs page, view the unbinding result.

                                                                                                                                                            You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                            To bind an EIP to the DB instance again, see Binding an EIP.

                                                                                                                                                          diff --git a/docs/rds/umn/rds_pg_recycle.html b/docs/rds/umn/rds_pg_recycle.html index 282f7a19..d1d4d163 100644 --- a/docs/rds/umn/rds_pg_recycle.html +++ b/docs/rds/umn/rds_pg_recycle.html @@ -7,10 +7,10 @@

                                                                                                                                                        Modifying Recycling Policy

                                                                                                                                                        A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

                                                                                                                                                        -
                                                                                                                                                        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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                        5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                                        6. Then, 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. In the navigation pane on the left, choose Recycling Management.
                                                                                                                                                        5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                                        6. Then, click OK.

                                                                                                                                                        Rebuilding a DB Instance

                                                                                                                                                        You can rebuild the primary DB instances in the recycle bin within the retention period.

                                                                                                                                                        -
                                                                                                                                                        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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                        5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                                        6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                                        +
                                                                                                                                                        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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                        5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                                        6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_reset_password.html b/docs/rds/umn/rds_pg_reset_password.html index 38e91713..6dafb0a6 100644 --- a/docs/rds/umn/rds_pg_reset_password.html +++ b/docs/rds/umn/rds_pg_reset_password.html @@ -6,14 +6,14 @@
                                                                                                                                                      • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
                                                                                                                                                      • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
                                                                                                                                                      • To protect against brute force hacking attempts and ensure system security, change your password periodically, such as every three or six months.
                                                                                                                                                      -

                                                                                                                                                      Method 1

                                                                                                                                                      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 > Reset Password in the Operation column.
                                                                                                                                                      5. Enter and confirm a new password.

                                                                                                                                                        Keep this password secure. The system cannot retrieve it.

                                                                                                                                                        +

                                                                                                                                                        Method 1

                                                                                                                                                        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 > Reset Password in the Operation column.
                                                                                                                                                        5. 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.

                                                                                                                                                        -

                                                                                                                                                        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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
                                                                                                                                                        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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
                                                                                                                                                          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 2b6cbf3a..7edfb55d 100644 --- a/docs/rds/umn/rds_pg_scale_cluster.html +++ b/docs/rds/umn/rds_pg_scale_cluster.html @@ -8,7 +8,7 @@

                                                                                                                                                            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:

                                                                                                                                                              +

                                                                                                                                                              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 Basic Information page. In the Storage Space area, click Scale.

                                                                                                                                                              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.
                                                                                                                                                                @@ -16,7 +16,7 @@

                                                                                                                                                              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:

                                                                                                                                                                +
                                                                                                                                                                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 Basic Information page. In the Storage Space area, click Scale.

                                                                                                                                                                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.
                                                                                                                                                                  diff --git a/docs/rds/umn/rds_pg_scale_rds.html b/docs/rds/umn/rds_pg_scale_rds.html index a351c06f..bb6618fd 100644 --- a/docs/rds/umn/rds_pg_scale_rds.html +++ b/docs/rds/umn/rds_pg_scale_rds.html @@ -6,7 +6,7 @@

                                                                                                                                                                  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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

                                                                                                                                                                    +

                                                                                                                                                                    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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

                                                                                                                                                                    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 Basic Information 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_start.html b/docs/rds/umn/rds_pg_start.html index 07157fd3..83bf0ddb 100644 --- a/docs/rds/umn/rds_pg_start.html +++ b/docs/rds/umn/rds_pg_start.html @@ -5,7 +5,7 @@

                                                                                                                                                                      Constraints

                                                                                                                                                                      • If you start a primary instance, read replicas (if there are any) will also be started.
                                                                                                                                                                      • Only instances in Stopped state can be started. After this function is enabled, billing for instance usage duration will start.
                                                                                                                                                                      -

                                                                                                                                                                      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 primary instance that you want to start and choose More > Start in the Operation column.
                                                                                                                                                                      5. In the displayed dialog box, click Yes.
                                                                                                                                                                      6. Refresh the instance list and view the status of the instance. If the status is Available, the instance is started successfully.
                                                                                                                                                                      +

                                                                                                                                                                      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 primary instance that you want to start and choose More > Start in the Operation column.
                                                                                                                                                                      5. In the displayed dialog box, click Yes.
                                                                                                                                                                      6. Refresh the instance list and view the status of the instance. If the status is Available, the instance is started successfully.
                                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_stop.html b/docs/rds/umn/rds_pg_stop.html index 8832f132..68c758e6 100644 --- a/docs/rds/umn/rds_pg_stop.html +++ b/docs/rds/umn/rds_pg_stop.html @@ -5,7 +5,7 @@

                                                                                                                                                                      Constraints

                                                                                                                                                                      • If you stop a primary instance, read replicas (if there are any) will also be stopped. They are stopped for up to seven days. You cannot stop a read replica without stopping the primary instance.
                                                                                                                                                                      • A stopped instance will not be moved to the recycle bin after being deleted.
                                                                                                                                                                      • If you do not manually start your stopped DB instance after seven days, your DB instance is automatically started during the next maintenance window. For details about the maintenance window, see Changing the Maintenance Window. To start a DB instance, see Starting an Instance.
                                                                                                                                                                      • After a DB instance is stopped, billing for instance usage duration will stop.
                                                                                                                                                                      -

                                                                                                                                                                      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 primary instance that you want to stop and choose More > Stop in the Operation column.
                                                                                                                                                                      5. In the displayed dialog box, click Yes.
                                                                                                                                                                      6. Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.
                                                                                                                                                                      +

                                                                                                                                                                      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 primary instance that you want to stop and choose More > Stop in the Operation column.
                                                                                                                                                                      5. In the displayed dialog box, click Yes.
                                                                                                                                                                      6. Refresh the instance list and view the status of the instance. If the status is Stopped, the instance is stopped successfully.
                                                                                                                                                                      diff --git a/docs/rds/umn/rds_pg_switch_ha.html b/docs/rds/umn/rds_pg_switch_ha.html index 9c6cb567..99cccb51 100644 --- a/docs/rds/umn/rds_pg_switch_ha.html +++ b/docs/rds/umn/rds_pg_switch_ha.html @@ -5,11 +5,11 @@

                                                                                                                                                                      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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                        Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                        +

                                                                                                                                                                        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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                          Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                          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 Switch Primary/Standby Instances 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.
                                                                                                                                                                          +

                                                                                                                                                                        8. 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_pg_tag.html b/docs/rds/umn/rds_pg_tag.html index df573035..b87da8ab 100644 --- a/docs/rds/umn/rds_pg_tag.html +++ b/docs/rds/umn/rds_pg_tag.html @@ -4,13 +4,13 @@

                                                                                                                                                                      Scenarios

                                                                                                                                                                      Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

                                                                                                                                                                      • You are advised to set predefined tags on the TMS console.
                                                                                                                                                                      • A tag consists of a key and value. You can add only one value for each key.
                                                                                                                                                                      • Up to 20 tags can be added for each DB instance.
                                                                                                                                                                      -

                                                                                                                                                                      Adding a Tag

                                                                                                                                                                      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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                        • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
                                                                                                                                                                        • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                        +

                                                                                                                                                                        Adding a Tag

                                                                                                                                                                        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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                          • The tag key must be unique. It can consist of up to 128 characters. Each tag key allows letters, numbers, spaces, and the following characters: _ . : = + - @. It cannot start or end with a space, or start with _sys_.
                                                                                                                                                                          • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                        6. After a tag has been added, you can view and manage it on the Tags page.
                                                                                                                                                                        -

                                                                                                                                                                        Editing a Tag

                                                                                                                                                                        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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                          • Only the tag value can be edited.
                                                                                                                                                                          • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                          +

                                                                                                                                                                          Editing a Tag

                                                                                                                                                                          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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                            • Only the tag value can be edited.
                                                                                                                                                                            • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                          6. After a tag has been edited, you can view and manage it on the Tags page.
                                                                                                                                                                          -

                                                                                                                                                                          Deleting a Tag

                                                                                                                                                                          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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                          6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                          +

                                                                                                                                                                          Deleting a Tag

                                                                                                                                                                          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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                          6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                          diff --git a/docs/rds/umn/rds_public_accessibility.html b/docs/rds/umn/rds_public_accessibility.html index d8f0c69d..024dd97a 100644 --- a/docs/rds/umn/rds_public_accessibility.html +++ b/docs/rds/umn/rds_public_accessibility.html @@ -7,11 +7,11 @@

                                                                                                                                                                          Prerequisites

                                                                                                                                                                          • You have assigned an EIP on the VPC console.
                                                                                                                                                                          • You can bind an EIP to a primary DB instance or a read replica only.
                                                                                                                                                                          • If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
                                                                                                                                                                          -

                                                                                                                                                                          Binding an EIP

                                                                                                                                                                          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 EIPs. On the displayed page, click Bind EIP.
                                                                                                                                                                          6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP to obtain one.
                                                                                                                                                                          7. On the EIPs page, view the EIP that has been bound to the DB instance.

                                                                                                                                                                            You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                                            +

                                                                                                                                                                            Binding an EIP

                                                                                                                                                                            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 EIPs. On the displayed page, click Bind EIP.
                                                                                                                                                                            6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP to obtain one.
                                                                                                                                                                            7. On the EIPs page, view the EIP that has been bound to the DB instance.

                                                                                                                                                                              You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                                              To unbind the EIP from the DB instance, see Unbinding an EIP.

                                                                                                                                                                            -

                                                                                                                                                                            Unbinding an EIP

                                                                                                                                                                            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 that has an EIP bound.
                                                                                                                                                                            5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                                            6. On the EIPs page, view the unbinding result.

                                                                                                                                                                              You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                                              +

                                                                                                                                                                              Unbinding an EIP

                                                                                                                                                                              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 that has an EIP bound.
                                                                                                                                                                              5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                                              6. On the EIPs page, view the unbinding result.

                                                                                                                                                                                You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                                                To bind an EIP to the DB instance again, see Binding an EIP.

                                                                                                                                                                              diff --git a/docs/rds/umn/rds_recent_log.html b/docs/rds/umn/rds_recent_log.html index 1926a341..4ddf6666 100644 --- a/docs/rds/umn/rds_recent_log.html +++ b/docs/rds/umn/rds_recent_log.html @@ -3,10 +3,10 @@

                                                                                                                                                                              Viewing Error Logs

                                                                                                                                                                              Scenarios

                                                                                                                                                                              Error logs contain logs generated during the database running. These can help you analyze problems with the database.

                                                                                                                                                                              -

                                                                                                                                                                              Viewing Log Details

                                                                                                                                                                              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 Logs. On the Error Logs page, view details about error logs.

                                                                                                                                                                                • You can select a log level in the upper right corner of the log list.

                                                                                                                                                                                  For PostgreSQL DB instances, the following levels of logs are displayed:

                                                                                                                                                                                  +

                                                                                                                                                                                  Viewing Log Details

                                                                                                                                                                                  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 Logs. On the Error Logs page, view details about error logs.

                                                                                                                                                                                    • You can select a log level in the upper right corner of the log list.

                                                                                                                                                                                      For PostgreSQL DB instances, the following levels of logs are displayed:

                                                                                                                                                                                      • ERROR
                                                                                                                                                                                      • FATAL
                                                                                                                                                                                      • PANIC
                                                                                                                                                                                      -
                                                                                                                                                                                    • You can click in the upper right corner to view error logs generated in different time segments.
                                                                                                                                                                                    • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
                                                                                                                                                                                    +
                                                                                                                                                                                  6. You can click in the upper right corner to view error logs generated in different time segments.
                                                                                                                                                                                  7. If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.

                                                                                                                                                                              diff --git a/docs/rds/umn/rds_reset_password.html b/docs/rds/umn/rds_reset_password.html index 67e27579..430c7500 100644 --- a/docs/rds/umn/rds_reset_password.html +++ b/docs/rds/umn/rds_reset_password.html @@ -6,14 +6,14 @@

                                                                                                                                                                            Precautions

                                                                                                                                                                            • If you have changed the administrator password of the primary DB instance, the administrator passwords of the standby DB instance and read replicas (if any) will also be changed accordingly.
                                                                                                                                                                            • The time required for the new password to take effect depends on the amount of service data currently being processed by the primary DB instance.
                                                                                                                                                                            • To protect against brute force hacking attempts and ensure system security, change your password periodically.
                                                                                                                                                                            -

                                                                                                                                                                            Method 1

                                                                                                                                                                            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 > Reset Password in the Operation column.
                                                                                                                                                                            5. Enter and confirm a new password.

                                                                                                                                                                              Keep this password secure. The system cannot retrieve it.

                                                                                                                                                                              +

                                                                                                                                                                              Method 1

                                                                                                                                                                              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 > Reset Password in the Operation column.
                                                                                                                                                                              5. 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.

                                                                                                                                                                              -

                                                                                                                                                                              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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
                                                                                                                                                                              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. In the DB Information area on the Basic Information page, click Reset Password in the Administrator field.
                                                                                                                                                                                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_sql_auditing_log.html b/docs/rds/umn/rds_sql_auditing_log.html index 4ec2bc20..ef7aafb3 100644 --- a/docs/rds/umn/rds_sql_auditing_log.html +++ b/docs/rds/umn/rds_sql_auditing_log.html @@ -8,10 +8,10 @@

                                                                                                                                                                                  Constraints

                                                                                                                                                                                  Only the versions listed below support SQL audit. .
                                                                                                                                                                                  • MySQL 5.6.43 and later versions for DB instances using cloud disks, MySQL 5.6.47.3 and later versions for DB instances using local disks
                                                                                                                                                                                  • MySQL 5.7.23 and later versions for DB instances using cloud disks, MySQL 5.7.29.3 and later versions for DB instances using local disks
                                                                                                                                                                                  • MySQL 8.0
                                                                                                                                                                                  -

                                                                                                                                                                                  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.
                                                                                                                                                                                  5. In the navigation pane on the left, choose SQL Audits. On the displayed page, click Set SQL Audit above the list. In the displayed dialog box, configure information as required and click OK.

                                                                                                                                                                                    Enabling or setting SQL audit
                                                                                                                                                                                    • To retain SQL audit logs, set (disabled) to (enabled).
                                                                                                                                                                                    • Audit logs are retained for 7 days by default but can be retained from anywhere from 1 to 732 days 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 target DB instance.
                                                                                                                                                                                    5. In the navigation pane on the left, choose SQL Audits. On the displayed page, click Set SQL Audit above the list. In the displayed dialog box, configure information as required and click OK.

                                                                                                                                                                                      Enabling or setting SQL audit
                                                                                                                                                                                      • To retain SQL audit logs, set (disabled) to (enabled).
                                                                                                                                                                                      • Audit logs are retained for 7 days by default but can be retained from anywhere from 1 to 732 days if needed.

                                                                                                                                                                                      Disabling SQL audit

                                                                                                                                                                                      -

                                                                                                                                                                                      To disable SQL audit, toggle (enabled) to (disabled).

                                                                                                                                                                                      +

                                                                                                                                                                                      To disable SQL audit, toggle (enabled) to (disabled).

                                                                                                                                                                                      • If you select the check box "I acknowledge that after audit log is disabled, all audit logs are deleted.", all audit logs will be deleted.

                                                                                                                                                                                        Deleted audit logs cannot be recovered. Exercise caution when performing this operation.

                                                                                                                                                                                      • If you do not select the check box "I acknowledge that after audit log is disabled, all audit logs are deleted.", the audit logs will be retained.
                                                                                                                                                                                      diff --git a/docs/rds/umn/rds_sqlserver_0025.html b/docs/rds/umn/rds_sqlserver_0025.html index 9c9e8c93..e4937e4c 100644 --- a/docs/rds/umn/rds_sqlserver_0025.html +++ b/docs/rds/umn/rds_sqlserver_0025.html @@ -7,11 +7,11 @@

                                                                                                                                                                                    Prerequisites

                                                                                                                                                                                    • You have assigned an EIP on the VPC console.
                                                                                                                                                                                    • You can bind an EIP to a primary DB instance or a read replica only.
                                                                                                                                                                                    • If a DB instance has already been bound with an EIP, you must unbind the EIP from the DB instance first before binding a new EIP to it.
                                                                                                                                                                                    -

                                                                                                                                                                                    Binding an EIP

                                                                                                                                                                                    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 EIPs page, click Bind EIP.
                                                                                                                                                                                    6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
                                                                                                                                                                                    7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

                                                                                                                                                                                      You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                                                      +

                                                                                                                                                                                      Binding an EIP

                                                                                                                                                                                      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 EIPs page, click Bind EIP.
                                                                                                                                                                                      6. In the displayed dialog box, all unbound EIPs are listed. Select the EIP to be bound and click OK. If no available EIPs are displayed, click View EIP and obtain an EIP.
                                                                                                                                                                                      7. On the EIPs page of the RDS console, view the EIP that has been bound to the DB instance.

                                                                                                                                                                                        You can also view the progress and result of binding an EIP to a DB instance on the Task Center page.

                                                                                                                                                                                        To unbind the EIP from the DB instance, see Unbinding an EIP.

                                                                                                                                                                                      -

                                                                                                                                                                                      Unbinding an EIP

                                                                                                                                                                                      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 that has an EIP bound.
                                                                                                                                                                                      5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                                                      6. On the EIPs page, view the unbinding result.

                                                                                                                                                                                        You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                                                        +

                                                                                                                                                                                        Unbinding an EIP

                                                                                                                                                                                        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 that has an EIP bound.
                                                                                                                                                                                        5. On the EIPs page, locate the target EIP to be unbound and click Unbind. In the displayed dialog box, click Yes.
                                                                                                                                                                                        6. On the EIPs page, view the unbinding result.

                                                                                                                                                                                          You can also view the progress and result of unbinding an EIP from a DB instance on the Task Center page.

                                                                                                                                                                                          To bind an EIP to the DB instance again, see Binding an EIP.

                                                                                                                                                                                        diff --git a/docs/rds/umn/rds_sqlserver_01_0001.html b/docs/rds/umn/rds_sqlserver_01_0001.html index 9835b51b..728a0727 100644 --- a/docs/rds/umn/rds_sqlserver_01_0001.html +++ b/docs/rds/umn/rds_sqlserver_01_0001.html @@ -7,19 +7,19 @@

                                                                                                                                                                                      Constraints

                                                                                                                                                                                      • Distributed transactions are enabled for newly created DB instances by default.
                                                                                                                                                                                      • Read replicas do not support distributed transactions.
                                                                                                                                                                                      • Once enabled, distributed transactions cannot be disabled.
                                                                                                                                                                                      • Enabling distributed transactions will cause DB instance to reboot. Exercise caution when you perform this operation.
                                                                                                                                                                                      • After a database link is created for a Microsoft SQL Server DB instance, if a primary/standby switchover or failover occurs, the database link will not be automatically synchronized to the new primary DB instance. You need to create a database link on the new primary DB instance again.
                                                                                                                                                                                      -

                                                                                                                                                                                      Enabling Distributed Transactions

                                                                                                                                                                                      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 Distributed Transactions. On the displayed page, click in the Distributed Transaction field.
                                                                                                                                                                                      6. In the displayed dialog box, click Yes to enable the distributed transaction function. The DB instance will be rebooted during this process.
                                                                                                                                                                                      +

                                                                                                                                                                                      Enabling Distributed Transactions

                                                                                                                                                                                      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 Distributed Transactions. On the displayed page, click in the Distributed Transaction field.
                                                                                                                                                                                      6. In the displayed dialog box, click Yes to enable the distributed transaction function. The DB instance will be rebooted during this process.
                                                                                                                                                                                      -

                                                                                                                                                                                      Adding Hosts

                                                                                                                                                                                      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 Distributed Transactions. On the displayed page, click Add Host.
                                                                                                                                                                                      6. In the displayed dialog box, enter host names and IP addresses, and click Test Connection. After all host connection tests are successful, click OK.

                                                                                                                                                                                        • Host IP name: Enter the names of the hosts for which you want to create distributed transactions with the RDS DB instance. Each host name must be unique and contains 1 to 64 characters, including only letters, digits, and hyphens (-).
                                                                                                                                                                                        • Host IP address: Enter the IP addresses of the hosts for which you want to create distributed transactions with the RDS DB instance. You need to configure the inbound and outbound rules in the security group for the host IP addresses first.
                                                                                                                                                                                          • If the hosts to be added are ECSs that are in the same VPC as your RDS DB instance, enter the private IP address of the ECS. You can obtain the ECS's private IP address on the ECS details page.
                                                                                                                                                                                          • If the hosts to be added are ECSs that are in different VPCs from the RDS DB instance, enter the public IP addresses of the ECSs. You need to bind an EIP to the RDS DB instance by referring to Binding and Unbinding an EIP.
                                                                                                                                                                                          +

                                                                                                                                                                                          Adding Hosts

                                                                                                                                                                                          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 Distributed Transactions. On the displayed page, click Add Host.
                                                                                                                                                                                          6. In the displayed dialog box, enter host names and IP addresses, and click Test Connection. After all host connection tests are successful, click OK.

                                                                                                                                                                                            • Host IP name: Enter the names of the hosts for which you want to create distributed transactions with the RDS DB instance. Each host name must be unique and contains 1 to 64 characters, including only letters, digits, and hyphens (-).
                                                                                                                                                                                            • Host IP address: Enter the IP addresses of the hosts for which you want to create distributed transactions with the RDS DB instance. You need to configure the inbound and outbound rules in the security group for the host IP addresses first.
                                                                                                                                                                                              • If the hosts to be added are ECSs that are in the same VPC as your RDS DB instance, enter the private IP address of the ECS. You can obtain the ECS's private IP address on the ECS details page.
                                                                                                                                                                                              • If the hosts to be added are ECSs that are in different VPCs from the RDS DB instance, enter the public IP addresses of the ECSs. You need to bind an EIP to the RDS DB instance by referring to Binding and Unbinding an EIP.

                                                                                                                                                                                          -

                                                                                                                                                                                          Resolving Names on Remote Servers (ECSs)

                                                                                                                                                                                          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 navigation pane on the left, choose Distributed Transactions. On the displayed page, obtain information about the RDS DB instance.
                                                                                                                                                                                          5. Add the RDS DB instance information to the hosts file in C:\Windows\System32\drivers\etc\hosts.
                                                                                                                                                                                          +

                                                                                                                                                                                          Resolving Names on Remote Servers (ECSs)

                                                                                                                                                                                          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 navigation pane on the left, choose Distributed Transactions. On the displayed page, obtain information about the RDS DB instance.
                                                                                                                                                                                          5. Add the RDS DB instance information to the hosts file in C:\Windows\System32\drivers\etc\hosts.
                                                                                                                                                                                          -

                                                                                                                                                                                          Configuring MSDTC on a Remote Server

                                                                                                                                                                                          1. Click Start and choose Control Panel > Administrative Tools > Component Services.
                                                                                                                                                                                          2. Expand the nodes in the Console pane Choose Computers > My Computer > Distributed Transaction Coordinator.
                                                                                                                                                                                          3. Right-click Local DTC and choose Properties.
                                                                                                                                                                                          4. In the displayed dialog box, click the Security tab. Configure information as required as shown in Figure 1 and click OK.

                                                                                                                                                                                            Figure 1 Local DTC properties
                                                                                                                                                                                            +

                                                                                                                                                                                            Configuring MSDTC on a Remote Server

                                                                                                                                                                                            1. Click Start and choose Control Panel > Administrative Tools > Component Services.
                                                                                                                                                                                            2. Expand the nodes in the Console pane Choose Computers > My Computer > Distributed Transaction Coordinator.
                                                                                                                                                                                            3. Right-click Local DTC and choose Properties.
                                                                                                                                                                                            4. In the displayed dialog box, click the Security tab. Configure information as required as shown in Figure 1 and click OK.

                                                                                                                                                                                              Figure 1 Local DTC properties

                                                                                                                                                                                            -

                                                                                                                                                                                            Deleting Hosts

                                                                                                                                                                                            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 Distributed Transactions. In the host list, locate the host to be deleted and click Delete in the Operation column.

                                                                                                                                                                                              Alternatively, select one or more hosts to be deleted and click Delete above the list to delete hosts in batches.

                                                                                                                                                                                              +

                                                                                                                                                                                              Deleting Hosts

                                                                                                                                                                                              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 Distributed Transactions. In the host list, locate the host to be deleted and click Delete in the Operation column.

                                                                                                                                                                                                Alternatively, select one or more hosts to be deleted and click Delete above the list to delete hosts in batches.

                                                                                                                                                                                              6. In the displayed dialog box, click Yes.
                                                                                                                                                                                            diff --git a/docs/rds/umn/rds_sqlserver_01_0002.html b/docs/rds/umn/rds_sqlserver_01_0002.html index 16cd7c60..4fa6740e 100644 --- a/docs/rds/umn/rds_sqlserver_01_0002.html +++ b/docs/rds/umn/rds_sqlserver_01_0002.html @@ -3,9 +3,9 @@

                                                                                                                                                                                            Viewing System Logs

                                                                                                                                                                                            Scenarios

                                                                                                                                                                                            System logs contain logs generated during the database running. These can help you analyze problems with the database.

                                                                                                                                                                                            -

                                                                                                                                                                                            Viewing Log Details

                                                                                                                                                                                            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 Logs. On the System Logs page, view details about system logs.

                                                                                                                                                                                              • You can select a log level in the upper right corner to view logs of the selected level.

                                                                                                                                                                                                For Microsoft SQL Server DB instances, only info-level logs are displayed currently.

                                                                                                                                                                                                +

                                                                                                                                                                                                Viewing Log Details

                                                                                                                                                                                                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 Logs. On the System Logs page, view details about system logs.

                                                                                                                                                                                                  • You can select a log level in the upper right corner to view logs of the selected level.

                                                                                                                                                                                                    For Microsoft SQL Server DB instances, only info-level logs are displayed currently.

                                                                                                                                                                                                    -
                                                                                                                                                                                                  • You can click in the upper right corner to view logs generated in different time segments.
                                                                                                                                                                                                  • If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.
                                                                                                                                                                                                  +
                                                                                                                                                                                                6. You can click in the upper right corner to view logs generated in different time segments.
                                                                                                                                                                                                7. If the description of a log is truncated, locate the log and move your pointer over the description in the Description column to view details.

                                                                                                                                                                                            diff --git a/docs/rds/umn/rds_sqlserver_05_0017.html b/docs/rds/umn/rds_sqlserver_05_0017.html index db4acb41..701ae76b 100644 --- a/docs/rds/umn/rds_sqlserver_05_0017.html +++ b/docs/rds/umn/rds_sqlserver_05_0017.html @@ -3,9 +3,9 @@

                                                                                                                                                                                            Exporting DB Instance Information

                                                                                                                                                                                            Scenarios

                                                                                                                                                                                            You can export information about all or selected DB instances to view and analyze DB instance information.

                                                                                                                                                                                            -

                                                                                                                                                                                            Exporting Information About All DB Instances

                                                                                                                                                                                            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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                                                                                                                                                                            5. Find a .csv file locally after the export task is completed.
                                                                                                                                                                                            +

                                                                                                                                                                                            Exporting Information About All DB Instances

                                                                                                                                                                                            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 in the upper right corner of the page. By default, information about all DB instances are exported. In the displayed dialog box, you can select the items to be exported and click Export.
                                                                                                                                                                                            5. Find a .csv file locally after the export task is completed.
                                                                                                                                                                                            -

                                                                                                                                                                                            Exporting Information About Selected DB Instances

                                                                                                                                                                                            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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                                                                                                                                                                            5. Find a .csv file locally after the export task is completed.
                                                                                                                                                                                            +

                                                                                                                                                                                            Exporting Information About Selected DB Instances

                                                                                                                                                                                            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, filter DB instances by DB engine, DB instance name, DB instance ID, DB instance tag, and floating IP address, or select the DB instances to be exported, and click in the upper right corner of the page. In the displayed dialog box, select the items to be exported and click Export.
                                                                                                                                                                                            5. Find a .csv file locally after the export task is completed.
                                                                                                                                                                                            diff --git a/docs/rds/umn/rds_sqlserver_05_0018.html b/docs/rds/umn/rds_sqlserver_05_0018.html index 2666f75b..2c01f3bb 100644 --- a/docs/rds/umn/rds_sqlserver_05_0018.html +++ b/docs/rds/umn/rds_sqlserver_05_0018.html @@ -3,7 +3,7 @@

                                                                                                                                                                                            Applying a Parameter Template

                                                                                                                                                                                            Scenarios

                                                                                                                                                                                            You can apply parameter templates to DB instances as needed. A parameter template can be applied only to DB instances of the same version.

                                                                                                                                                                                            -

                                                                                                                                                                                            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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                                                                                                                                                                              • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                                                                                                                                                                              • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.
                                                                                                                                                                                              +

                                                                                                                                                                                              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 Parameter Template Management page, perform the following operations based on the type of the parameter template to be applied:

                                                                                                                                                                                                • If you intend to apply a default parameter template to DB instances, click Default Templates, locate the target parameter template, and click Apply in the Operation column.
                                                                                                                                                                                                • If you intend to apply a custom parameter template to DB instances, click Custom Templates, locate the target parameter template, and choose More > Apply in the Operation column.

                                                                                                                                                                                                A parameter template can be applied to one or more DB instances.

                                                                                                                                                                                              5. In the displayed dialog box, select one or more DB instances to which the parameter template will be applied and click OK.

                                                                                                                                                                                                After the parameter template is successfully applied, you can view the application records by referring to section Viewing Application Records of a Parameter Template.

                                                                                                                                                                                              diff --git a/docs/rds/umn/rds_sqlserver_05_0023.html b/docs/rds/umn/rds_sqlserver_05_0023.html index 5aa6a491..8a595504 100644 --- a/docs/rds/umn/rds_sqlserver_05_0023.html +++ b/docs/rds/umn/rds_sqlserver_05_0023.html @@ -3,8 +3,8 @@

                                                                                                                                                                                              Changing a DB Instance Type from Single to Primary/Standby

                                                                                                                                                                                              Scenarios

                                                                                                                                                                                              • RDS enables you to change single DB instances to primary/standby DB instances to improve instance reliability.
                                                                                                                                                                                              • Primary/standby DB instances support automatic failover. If the primary DB instance fails, the standby DB instance takes over services quickly. You are advised to deploy primary and standby DB instances in different AZs for high availability and disaster recovery.
                                                                                                                                                                                              -

                                                                                                                                                                                              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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                                                                                                                                                                Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                                                                                                                                                                -

                                                                                                                                                                                              5. Select a standby AZ and enter the original administrator password. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                                                                                                                                                                              6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                                                                                                                                                                • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.
                                                                                                                                                                                                +

                                                                                                                                                                                                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 single DB instance and choose More > Change Type to Primary/Standby in the Operation column.

                                                                                                                                                                                                  Alternatively, click the target DB instance. In the DB instance topology, click on the left to change the instance type from single to primary/standby.

                                                                                                                                                                                                  +

                                                                                                                                                                                                5. Select a standby AZ and enter the original administrator password. Other configurations are the same as those of the primary DB instance by default. Confirm the configurations and click Submit.
                                                                                                                                                                                                6. After a single DB instance is changed to primary/standby instance, you can view and manage it on the Instances page.

                                                                                                                                                                                                  • The DB instance is in the Changing type to primary/standby status. 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 DB instance type is changed to primary/standby, the instance status will change to Available and the instance type will change to Primary/Standby.

                                                                                                                                                                                              diff --git a/docs/rds/umn/rds_sqlserver_05_0024.html b/docs/rds/umn/rds_sqlserver_05_0024.html index 78a9245d..1dcfce66 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.
                                                                                                                                                                                              5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                                                                                                                                                                              6. In the displayed dialog box, enter a new floating IP address. 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.
                                                                                                                                                                                                5. In the Connection Information area on the Basic Information page, click Change in the Floating IP Address field.
                                                                                                                                                                                                6. In the displayed dialog box, enter a new floating IP address. 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_0055.html b/docs/rds/umn/rds_sqlserver_05_0055.html index f3c24d8f..8a81d34b 100644 --- a/docs/rds/umn/rds_sqlserver_05_0055.html +++ b/docs/rds/umn/rds_sqlserver_05_0055.html @@ -5,7 +5,7 @@
                                                                                                                                                                                              • You can create DB instances with the same configurations numerous times.
                                                                                                                                                                                              • This function is unavailable for read replicas.
                                                                                                                                                                                              -

                                                                                                                                                                                              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 > Create Same DB Instance in the Operation column.
                                                                                                                                                                                              5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

                                                                                                                                                                                                For details about Microsoft SQL Server DB instance configurations, see section Step 1: Create a 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 > Create Same DB Instance in the Operation column.
                                                                                                                                                                                                5. On the displayed page, the configurations are the same as those of the selected DB instance. You can change them as required. Then, click Next.

                                                                                                                                                                                                  For details about Microsoft SQL Server DB instance configurations, see section Step 1: Create a DB Instance.

                                                                                                                                                                                                6. Confirm the instance specifications.

                                                                                                                                                                                                7. Refresh the DB instance list and view the status of the DB instance. If the status is Available, it has been created successfully.

                                                                                                                                                                                                  You can manage the DB instance on the Instances page.

                                                                                                                                                                                                diff --git a/docs/rds/umn/rds_sqlserver_05_0098.html b/docs/rds/umn/rds_sqlserver_05_0098.html index 8d0e3085..f77301af 100644 --- a/docs/rds/umn/rds_sqlserver_05_0098.html +++ b/docs/rds/umn/rds_sqlserver_05_0098.html @@ -3,7 +3,7 @@

                                                                                                                                                                                                Viewing Application Records of a Parameter Template

                                                                                                                                                                                                Scenarios

                                                                                                                                                                                                You can view the application records of a parameter template.

                                                                                                                                                                                                -

                                                                                                                                                                                                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. Choose Parameter Template Management in the navigation pane on the left.
                                                                                                                                                                                                5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                                                                                                                                                                  You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                                                                                                                                                                  +

                                                                                                                                                                                                  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. Choose Parameter Template Management in the navigation pane on the left.
                                                                                                                                                                                                  5. On the Default Templates page, locate the target parameter template and click View Application Record in the Operation column. Alternatively, on the Custom Templates page, choose More > View Application Record in the Operation column.

                                                                                                                                                                                                    You can view the name or ID of the DB instance that the parameter template applies to, as well as the application status, application time, and failure cause (if failed).

                                                                                                                                                                                                diff --git a/docs/rds/umn/rds_sqlserver_05_0099.html b/docs/rds/umn/rds_sqlserver_05_0099.html index 67b63e8a..ed31712c 100644 --- a/docs/rds/umn/rds_sqlserver_05_0099.html +++ b/docs/rds/umn/rds_sqlserver_05_0099.html @@ -5,11 +5,11 @@

                                                                                                                                                                                                An exported or custom parameter template has initially a blank change history.

                                                                                                                                                                                                -

                                                                                                                                                                                                Viewing Change History of 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.
                                                                                                                                                                                                5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                                                                                                                                                                  You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                                                                                                                                                                  +

                                                                                                                                                                                                  Viewing Change History of 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.
                                                                                                                                                                                                  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

                                                                                                                                                                                                    You can view the parameter name, original parameter value, new parameter value, modification status, modification time, application status, and application time.

                                                                                                                                                                                                    You can apply the parameter template to DB instances as required by referring to section Applying a Parameter Template.

                                                                                                                                                                                                  -

                                                                                                                                                                                                  Viewing Change History of a Parameter Template

                                                                                                                                                                                                  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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                                                                  5. On the displayed page, choose Change History in the navigation pane on the left.

                                                                                                                                                                                                    You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                                                                                                                                                                    +

                                                                                                                                                                                                    Viewing Change History of a Parameter Template

                                                                                                                                                                                                    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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                                                                    5. On the displayed page, choose Change History in the navigation pane on the left.

                                                                                                                                                                                                      You can view the parameter name, original parameter value, new parameter value, modification status, and modification time.

                                                                                                                                                                                                  diff --git a/docs/rds/umn/rds_sqlserver_06_0003.html b/docs/rds/umn/rds_sqlserver_06_0003.html index 4c5ceb5a..66c7c720 100644 --- a/docs/rds/umn/rds_sqlserver_06_0003.html +++ b/docs/rds/umn/rds_sqlserver_06_0003.html @@ -11,7 +11,7 @@
                                                                                                                                                                                                  • RDS has been running properly for about 10 minutes.

                                                                                                                                                                                                    For a newly created RDS DB instance, you need to wait a bit before you can view the 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                                                                                                                                                                  Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye 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, locate the target DB instance and click View Metric in the Operation column to go to the Cloud Eye console.

                                                                                                                                                                                                    Alternatively, click the target DB instance. On the displayed page, click View Metric in the upper right corner of the page to go to the Cloud Eye console.

                                                                                                                                                                                                  5. On the Cloud Eye console, view monitoring metrics of the primary DB instance.

                                                                                                                                                                                                    Cloud Eye can monitor performance metrics from the last 1 hour, 3 hours, 12 hours, 1 day, 30 days, and 7 days.

                                                                                                                                                                                                  diff --git a/docs/rds/umn/rds_sqlserver_06_0005.html b/docs/rds/umn/rds_sqlserver_06_0005.html index 1e4c0189..bf7f94d0 100644 --- a/docs/rds/umn/rds_sqlserver_06_0005.html +++ b/docs/rds/umn/rds_sqlserver_06_0005.html @@ -6,7 +6,7 @@

                                                                                                                                                                                                Procedure

                                                                                                                                                                                                1. Log in to the management console.
                                                                                                                                                                                                2. Choose Management & Governance > Cloud Trace Service.
                                                                                                                                                                                                3. Choose Trace List in the navigation pane on the left.
                                                                                                                                                                                                4. Filter conditions to query traces. The details are described as follows:

                                                                                                                                                                                                  • Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.

                                                                                                                                                                                                    When you select Resource ID for Search By, you also need to select or enter a resource ID.

                                                                                                                                                                                                  • Operator: Select a specific operator from the drop-down list.
                                                                                                                                                                                                  • Trace Status: Available options include All trace statuses, Normal, Warning, and Incident. You can only select one of them.
                                                                                                                                                                                                  • In the upper right corner of the page, you can specify a time range for querying traces.
                                                                                                                                                                                                  -

                                                                                                                                                                                                5. Select the search criteria, and click Query.
                                                                                                                                                                                                6. Click on the left of the required trace to expand its details.
                                                                                                                                                                                                7. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                                                                                                                                                                8. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                                                                                                                                                                  For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                                                                                                                                                                                  +

                                                                                                                                                                                                9. Select the search criteria, and click Query.
                                                                                                                                                                                                10. Click on the left of the required trace to expand its details.
                                                                                                                                                                                                11. Click View Trace in the Operation column. On the displayed dialog box, the trace structure details are displayed.
                                                                                                                                                                                                12. Click Export on the right. CTS exports traces collected in the past seven days to a CSV file. The CSV file contains all information related to traces on the management console.

                                                                                                                                                                                                  For details about key fields in the trace structure, see sections "Trace Structure" and "Trace Examples" in the Cloud Trace Service User Guide.

                                                                                                                                                                                                diff --git a/docs/rds/umn/rds_sqlserver_06_0022.html b/docs/rds/umn/rds_sqlserver_06_0022.html index ea5df0be..11419e9a 100644 --- a/docs/rds/umn/rds_sqlserver_06_0022.html +++ b/docs/rds/umn/rds_sqlserver_06_0022.html @@ -3,7 +3,7 @@

                                                                                                                                                                                                Selecting Displayed Items

                                                                                                                                                                                                Scenarios

                                                                                                                                                                                                You can customize which instance items are displayed on the Instances 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 to edit columns displayed in the DB instance list.

                                                                                                                                                                                                  • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                                                                                                                                                    These default items cannot be deselected.

                                                                                                                                                                                                    +

                                                                                                                                                                                                    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 to edit columns displayed in the DB instance list.

                                                                                                                                                                                                      • The following items are displayed by default: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, and operation.

                                                                                                                                                                                                        These default items cannot be deselected.

                                                                                                                                                                                                      • In a single project, you can select up to 9 items: DB instance name/ID, DB instance type, DB engine version, status, floating IP address, creation time, database port, storage type, and operation.

                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_07_0000.html b/docs/rds/umn/rds_sqlserver_07_0000.html new file mode 100644 index 00000000..ce69a8d0 --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_07_0000.html @@ -0,0 +1,17 @@ + + +

                                                                                                                                                                                                    Permissions Management

                                                                                                                                                                                                    +
                                                                                                                                                                                                    + + diff --git a/docs/rds/umn/rds_sqlserver_07_0002.html b/docs/rds/umn/rds_sqlserver_07_0002.html new file mode 100644 index 00000000..8c16663f --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_07_0002.html @@ -0,0 +1,26 @@ + + +

                                                                                                                                                                                                    Creating a User and Granting Permissions

                                                                                                                                                                                                    +

                                                                                                                                                                                                    This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your RDS resources. With IAM, you can:

                                                                                                                                                                                                    +
                                                                                                                                                                                                    • Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing RDS resources.
                                                                                                                                                                                                    • Grant only the permissions required for users to perform a specific task.
                                                                                                                                                                                                    • Entrust a account or cloud service to perform efficient O&M on your RDS resources.
                                                                                                                                                                                                    +

                                                                                                                                                                                                    If your account does not require individual IAM users, skip this chapter.

                                                                                                                                                                                                    +

                                                                                                                                                                                                    This section describes the procedure for granting permissions (see Figure 1).

                                                                                                                                                                                                    +

                                                                                                                                                                                                    Prerequisites

                                                                                                                                                                                                    Learn about the permissions (see Permissions Management) supported by RDS and choose policies or roles according to your requirements.For the system policies of other services, see Permissions.

                                                                                                                                                                                                    +
                                                                                                                                                                                                    +

                                                                                                                                                                                                    Process Flow

                                                                                                                                                                                                    Figure 1 Process for granting RDS permissions
                                                                                                                                                                                                    +
                                                                                                                                                                                                    1. Create a user group and assign permissions to it.

                                                                                                                                                                                                      Create a user group on the IAM console, and attach the RDS ReadOnlyAccess policy to the group.

                                                                                                                                                                                                      +

                                                                                                                                                                                                      To use some interconnected services, you also need to configure permissions of such services.

                                                                                                                                                                                                      +

                                                                                                                                                                                                      For example, to connect to your DB instance through the console, configure the DAS FullAccess permission of Data Admin Service (DAS) besides RDS ReadOnlyAccess.

                                                                                                                                                                                                      +
                                                                                                                                                                                                      +
                                                                                                                                                                                                    2. Create an IAM user and add it to the user group.

                                                                                                                                                                                                      Create a user on the IAM console and add the user to the group created in 1.

                                                                                                                                                                                                      +
                                                                                                                                                                                                    3. Log in and verify permissions.

                                                                                                                                                                                                      Log in to the RDS console by using the created user, and verify that the user only has read permissions for RDS.

                                                                                                                                                                                                      +
                                                                                                                                                                                                      • Choose Service List > Relational Database Service and click Buy DB Instance. If a message appears indicating that you have insufficient permissions to perform the operation, the RDS ReadOnlyAccess policy has already been applied.
                                                                                                                                                                                                      • Choose any other service in Service List. If a message appears indicating that you have insufficient permissions to access the service, the RDS ReadOnlyAccess policy has already taken effect.
                                                                                                                                                                                                      +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    Parent topic: Permissions Management
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    + diff --git a/docs/rds/umn/rds_sqlserver_07_0003.html b/docs/rds/umn/rds_sqlserver_07_0003.html new file mode 100644 index 00000000..1481cbae --- /dev/null +++ b/docs/rds/umn/rds_sqlserver_07_0003.html @@ -0,0 +1,32 @@ + + +

                                                                                                                                                                                                    RDS Custom Policies

                                                                                                                                                                                                    +

                                                                                                                                                                                                    Custom policies can be created to supplement the system policies of RDS.

                                                                                                                                                                                                    +

                                                                                                                                                                                                    You can create custom policies in either of the following two ways:

                                                                                                                                                                                                    +
                                                                                                                                                                                                    • Visual editor: Select cloud services, actions, resources, and request conditions without the need to know policy syntax.
                                                                                                                                                                                                    • JSON: Edit JSON policies from scratch or based on an existing policy.
                                                                                                                                                                                                    +

                                                                                                                                                                                                    For details, see Creating a Custom Policy. The following section contains examples of common RDS custom policies.

                                                                                                                                                                                                    +

                                                                                                                                                                                                    Example Custom Policies

                                                                                                                                                                                                    • Example 1: Allowing users to create RDS DB instances
                                                                                                                                                                                                      {
+	"Version": "1.1",
+	"Statement": [{
+		"Effect": "Allow",
+		"Action": ["rds:instance:create"]
+	}]
+}
                                                                                                                                                                                                      +
                                                                                                                                                                                                    • Example 2: Denying RDS DB instance deletion

                                                                                                                                                                                                      A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user include both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

                                                                                                                                                                                                      +

                                                                                                                                                                                                      The following method can be used if you need to assign permissions of the RDS FullAccess policy to a user but you want to prevent the user from deleting RDS DB instances. Create a custom policy for denying RDS DB instance deletion, and attach both policies to the group the user belongs to. Then, the user can perform all operations on RDS DB instances except deleting RDS DB instances. The following is an example deny policy:

                                                                                                                                                                                                      +
                                                                                                                                                                                                      {
+	"Version": "1.1",
+	"Statement": [{
+		"Action": ["rds:instance:delete"],
+		"Effect": "Deny"
+	}]
+}
                                                                                                                                                                                                      +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    Parent topic: Permissions Management
                                                                                                                                                                                                    +
                                                                                                                                                                                                    +
                                                                                                                                                                                                    + diff --git a/docs/rds/umn/rds_sqlserver_08_0042.html b/docs/rds/umn/rds_sqlserver_08_0042.html index 0d9d0a62..73776814 100644 --- a/docs/rds/umn/rds_sqlserver_08_0042.html +++ b/docs/rds/umn/rds_sqlserver_08_0042.html @@ -3,7 +3,7 @@

                                                                                                                                                                                                    Exporting a Parameter Template

                                                                                                                                                                                                    Scenarios

                                                                                                                                                                                                    • You can export a parameter template of a DB instance for future use. You can also apply the exported parameter template to DB instances by referring to Applying a Parameter Template.
                                                                                                                                                                                                    • You can export the parameter template information (parameter names, values, and descriptions) of a DB instance to a CSV file for viewing and analysis.
                                                                                                                                                                                                    -

                                                                                                                                                                                                    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.
                                                                                                                                                                                                    5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                                                                                                                                                      • Exporting to a custom template
                                                                                                                                                                                                        In the displayed dialog box, configure required information and click OK.
                                                                                                                                                                                                        • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                                                                                                                                        +

                                                                                                                                                                                                        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.
                                                                                                                                                                                                        5. In the navigation pane on the left, choose Parameters. On the displayed page, click Export above the parameter list.

                                                                                                                                                                                                          • Exporting to a custom template
                                                                                                                                                                                                            In the displayed dialog box, configure required information and click OK.
                                                                                                                                                                                                            • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                                                                            • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                                                                                                                                            After the parameter template is exported, a new template is generated in the list on the Parameter Template Management page.

                                                                                                                                                                                                            diff --git a/docs/rds/umn/rds_sqlserver_11_0002.html b/docs/rds/umn/rds_sqlserver_11_0002.html index 8ab845c2..54d2a08e 100644 --- a/docs/rds/umn/rds_sqlserver_11_0002.html +++ b/docs/rds/umn/rds_sqlserver_11_0002.html @@ -1,7 +1,7 @@

                                                                                                                                                                                                            Introducing Read Replicas

                                                                                                                                                                                                            -

                                                                                                                                                                                                            Introduction

                                                                                                                                                                                                            Only RDS for SQL Server 2017 Enterprise Edition supports read replicas.

                                                                                                                                                                                                            +

                                                                                                                                                                                                            Introduction

                                                                                                                                                                                                            Only RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.

                                                                                                                                                                                                            In read-intensive scenarios, a single DB instance may be unable to handle the read pressure and service performance may be affected. To expand the DB instance read ability to offload read pressure on the database, you can create one or more read replicas in a region. These read replicas can process a large number of read requests and increase application throughput. You need to separately configure connection addresses of the primary DB instance and each read replica on your applications so that all read requests can be sent to read replicas and write requests to the primary DB instance.

                                                                                                                                                                                                            A read replica uses a single-node architecture (without a slave node). Changes to the primary DB instance are also automatically synchronized to all associated read replicas through the native SQL Server replication function. The synchronization is not affected by network latency. Read replicas and the primary DB instance must be in the same region but can be in different AZs.

                                                                                                                                                                                                            diff --git a/docs/rds/umn/rds_sqlserver_11_0004.html b/docs/rds/umn/rds_sqlserver_11_0004.html index dd803698..425a2651 100644 --- a/docs/rds/umn/rds_sqlserver_11_0004.html +++ b/docs/rds/umn/rds_sqlserver_11_0004.html @@ -1,11 +1,11 @@

                                                                                                                                                                                                            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 Basic Information 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 Basic Information page.
                                                                                                                                                                                                            -

                                                                                                                                                                                                            Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                                                                                                                            5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                                                                                                                            +

                                                                                                                                                                                                            Entering the Management Interface Through 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. Click the name of the primary DB instance with which the target read replica is associated to go to the Basic Information page.
                                                                                                                                                                                                            5. In the DB instance topology, click the target read replica. You can view and manage it in the displayed pane.
                                                                                                                                                                                                            -

                                                                                                                                                                                                            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.
                                                                                                                                                                                                            +

                                                                                                                                                                                                            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 1236eaa3..210320e1 100644 --- a/docs/rds/umn/rds_sqlserver_change_database_port.html +++ b/docs/rds/umn/rds_sqlserver_change_database_port.html @@ -3,13 +3,13 @@

                                                                                                                                                                                                            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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                                                                                                                              The DB instance port is 1433 by default or it can be set to a value from 2100 to 9500, excluding 5355 and 5985.

                                                                                                                                                                                                              +

                                                                                                                                                                                                              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. In the Connection Information area on the Basic Information page, click in the Database Port field.

                                                                                                                                                                                                                The DB instance port is 1433 by default or it can be set to a value from 2100 to 9500, excluding 5355 and 5985.

                                                                                                                                                                                                                -
                                                                                                                                                                                                                • To submit the change, click .
                                                                                                                                                                                                                  • In the dialog box, click Yes.
                                                                                                                                                                                                                    1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                                                                                                                    2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will reboot.

                                                                                                                                                                                                                      For RDS for SQL Server, only 2017 Enterprise Edition supports read replicas.

                                                                                                                                                                                                                      +
                                                                                                                                                                                                                      • To submit the change, click .
                                                                                                                                                                                                                        • In the dialog box, click Yes.
                                                                                                                                                                                                                          1. If you change the database port of the primary DB instance, that of the standby DB instance will also be changed and both DB instances will be rebooted.
                                                                                                                                                                                                                          2. If you change the database port of a read replica, the change will not affect other DB instances. Only the read replica will reboot.

                                                                                                                                                                                                                            RDS for SQL Server 2019 Enterprise Edition and 2017 Enterprise Edition support read replicas.

                                                                                                                                                                                                                          3. This process takes 1-5 minutes.
                                                                                                                                                                                                                        • In the dialog box, click No to cancel the modification.
                                                                                                                                                                                                                        -
                                                                                                                                                                                                                      • To cancel the change, click .
                                                                                                                                                                                                                      +
                                                                                                                                                                                                                    3. To cancel the change, click .

                                                                                                                                                                                                                • View the results on the Basic Information page.
                                                                                                                                                                                                              diff --git a/docs/rds/umn/rds_sqlserver_configuration.html b/docs/rds/umn/rds_sqlserver_configuration.html index 21074b9a..142451d0 100644 --- a/docs/rds/umn/rds_sqlserver_configuration.html +++ b/docs/rds/umn/rds_sqlserver_configuration.html @@ -7,7 +7,7 @@

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

                                                                                                                                                                                                              RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.

                                                                                                                                                                                                              -

                                                                                                                                                                                                              Modifying Parameter Template Parameters

                                                                                                                                                                                                              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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                                                                              5. On the Parameters page, modify parameters as required.

                                                                                                                                                                                                                Relevant parameters are as follows:

                                                                                                                                                                                                                +

                                                                                                                                                                                                                Modifying Parameter Template Parameters

                                                                                                                                                                                                                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. Choose Parameter Template Management in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
                                                                                                                                                                                                                5. On the Parameters page, modify parameters as required.

                                                                                                                                                                                                                  Relevant parameters are as follows:

                                                                                                                                                                                                                  • Set remote access to 0 (default value) to prevent locally stored procedures from running on a remote server and remotely stored procedures from running on a local server.
                                                                                                                                                                                                                  • The max server memory (MB) parameter indicates the server memory. The default value equals to the OS memory (MB) minus 520 (MB). Its minimum value is 1024 MB.

                                                                                                                                                                                                                  Available operations are as follows:

                                                                                                                                                                                                                  • To save the modifications, click Save.
                                                                                                                                                                                                                  • To cancel the modifications, click Cancel.
                                                                                                                                                                                                                  • To preview the modifications, click Preview.
                                                                                                                                                                                                                  @@ -15,7 +15,7 @@
                                                                                                                                                                                                                  • A DB instance reboot caused by instance class changes will not make parameter modifications take effect.
                                                                                                                                                                                                                  • If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
                                                                                                                                                                                                                  • If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.

                                                                                                                                                                                                                -

                                                                                                                                                                                                                Modifying Instance Parameters

                                                                                                                                                                                                                1. Log in to the 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 displayed page, modify parameters as required.

                                                                                                                                                                                                                  Relevant parameters are as follows:
                                                                                                                                                                                                                  • Set remote access to 0 (default value) to prevent locally stored procedures from running on a remote server and remotely stored procedures from running on a local server.
                                                                                                                                                                                                                  • The max server memory (MB) parameter indicates the server memory. The default value equals to the OS memory (MB) minus 520 (MB). Its minimum value is 1024 MB.
                                                                                                                                                                                                                  +

                                                                                                                                                                                                                  Modifying Instance Parameters

                                                                                                                                                                                                                  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 displayed page, modify parameters as required.

                                                                                                                                                                                                                    Relevant parameters are as follows:
                                                                                                                                                                                                                    • Set remote access to 0 (default value) to prevent locally stored procedures from running on a remote server and remotely stored procedures from running on a local server.
                                                                                                                                                                                                                    • The max server memory (MB) parameter indicates the server memory. The default value equals to the OS memory (MB) minus 520 (MB). Its minimum value is 1024 MB.

                                                                                                                                                                                                                    Available operations are Save, Cancel, and Preview.

                                                                                                                                                                                                                    • To save the modifications, click Save.
                                                                                                                                                                                                                    • To cancel the modifications, click Cancel.
                                                                                                                                                                                                                    • To preview the modifications, click Preview.
                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_modify_availability.html b/docs/rds/umn/rds_sqlserver_modify_availability.html index e3640c08..f51b4fc3 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 target primary/standby DB instances.
                                                                                                                                                                                                                    5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                                                                                                    6. View the results on the Basic Information 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 target primary/standby DB instances.
                                                                                                                                                                                                                    5. In the DB Information area on the displayed Basic Information page, click Change in the Failover Priority field. In the displayed dialog box, select a priority and click OK.
                                                                                                                                                                                                                    6. View the results on the Basic Information page.
                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_modify_instance_name.html b/docs/rds/umn/rds_sqlserver_modify_instance_name.html index f6b3d7e3..c45841c6 100644 --- a/docs/rds/umn/rds_sqlserver_modify_instance_name.html +++ b/docs/rds/umn/rds_sqlserver_modify_instance_name.html @@ -3,9 +3,9 @@

                                                                                                                                                                                                                    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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 Basic Information page. In the DB Instance Name field in the DB Information area, 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 .
                                                                                                                                                                                                                        +
                                                                                                                                                                                                                        • To submit the change, click .
                                                                                                                                                                                                                        • To cancel the change, click .

                                                                                                                                                                                                                      5. View the results on the Basic Information page.
                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_parameter_group.html b/docs/rds/umn/rds_sqlserver_parameter_group.html index 7e936788..2cb0e9bc 100644 --- a/docs/rds/umn/rds_sqlserver_parameter_group.html +++ b/docs/rds/umn/rds_sqlserver_parameter_group.html @@ -8,11 +8,11 @@

                                                                                                                                                                                                                    If you want to use a custom parameter template, you simply create a parameter template and select it when you create a DB instance or apply it to an existing DB instance following the instructions provided in section Applying a Parameter Template.

                                                                                                                                                                                                                    When you have already created a parameter template and want to include most of the custom parameters and values from that template in a new parameter template, you can replicate that parameter template following the instructions provided in section Replicating a Parameter Template.

                                                                                                                                                                                                                    The following are the key points you should know when using parameters in a parameter template:

                                                                                                                                                                                                                    -
                                                                                                                                                                                                                    • When you change a dynamic parameter value in a parameter template and save the change, the change takes effect immediately. When you change a static parameter value in a parameter template and save the change, the change will take effect only after you manually reboot the DB instances that the parameter template applies to.
                                                                                                                                                                                                                    • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
                                                                                                                                                                                                                    +
                                                                                                                                                                                                                    • The changes to parameter values in a custom parameter template take effect only after you apply the template to DB instances. For details, see Applying a Parameter Template.
                                                                                                                                                                                                                    • Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.

                                                                                                                                                                                                                    RDS does not share parameter template quotas with DDS.

                                                                                                                                                                                                                    You can create a maximum of 100 parameter templates for RDS DB instances. All RDS DB engines share the parameter template quota.

                                                                                                                                                                                                                    -

                                                                                                                                                                                                                    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 Parameter Template Management page, click Create Parameter Template.
                                                                                                                                                                                                                    5. In the displayed dialog box, configure required information and click OK.

                                                                                                                                                                                                                      • Select a DB engine for the parameter template.
                                                                                                                                                                                                                      • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                                                                                      • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=
                                                                                                                                                                                                                      +

                                                                                                                                                                                                                      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 Parameter Template Management page, click Create Parameter Template.
                                                                                                                                                                                                                      5. In the displayed dialog box, configure required information and click OK.

                                                                                                                                                                                                                        • Select a DB engine for the parameter template.
                                                                                                                                                                                                                        • The template name must consist of 1 to 64 characters. It can contain only uppercase letters, lowercase letters, digits, hyphens (-), underscores (_), and periods (.).
                                                                                                                                                                                                                        • The description consists of a maximum of 256 characters and cannot contain carriage return characters or the following special characters: >!<"&'=

                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_recycle.html b/docs/rds/umn/rds_sqlserver_recycle.html index d62b8ffd..b72786f5 100644 --- a/docs/rds/umn/rds_sqlserver_recycle.html +++ b/docs/rds/umn/rds_sqlserver_recycle.html @@ -7,10 +7,10 @@

                                                                                                                                                                                                                    Modifying Recycling Policy

                                                                                                                                                                                                                    A new recycling policy only applies to DB instances that were put in the recycle bin after the new policy was put into effect. For DB instances that were in the recycle bin before the modification, the original recycling policy takes effect.

                                                                                                                                                                                                                    -
                                                                                                                                                                                                                    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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                                                                                    5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                                                                                                    6. Then, 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. In the navigation pane on the left, choose Recycling Management.
                                                                                                                                                                                                                    5. On the Recycling Management page, click Modify Recycling Policy. In the displayed dialog box, set the retention period for the deleted DB instances from 1 day to 7 days.
                                                                                                                                                                                                                    6. Then, click OK.

                                                                                                                                                                                                                    Rebuilding a DB Instance

                                                                                                                                                                                                                    You can rebuild the primary DB instances in the recycle bin within the retention period.

                                                                                                                                                                                                                    -
                                                                                                                                                                                                                    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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                                                                                    5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                                                                                                    6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                                                                                                    +
                                                                                                                                                                                                                    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 navigation pane on the left, choose Recycling Management.
                                                                                                                                                                                                                    5. On the Recycling Management page, locate the target DB instance to be rebuilt and click Rebuild in the Operation column.
                                                                                                                                                                                                                    6. On the Rebuild DB Instance page, configure required information and submit the rebuild task. For details, see Restoring from Backup Files to DB Instances.
                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_sqlserver_scale_cluster.html b/docs/rds/umn/rds_sqlserver_scale_cluster.html index 3b08129e..c12ce629 100644 --- a/docs/rds/umn/rds_sqlserver_scale_cluster.html +++ b/docs/rds/umn/rds_sqlserver_scale_cluster.html @@ -8,7 +8,7 @@

                                                                                                                                                                                                                    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:

                                                                                                                                                                                                                      +

                                                                                                                                                                                                                      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 Basic Information page. In the Storage Space area, click Scale.

                                                                                                                                                                                                                      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.
                                                                                                                                                                                                                        diff --git a/docs/rds/umn/rds_sqlserver_scale_rds.html b/docs/rds/umn/rds_sqlserver_scale_rds.html index fcecf1b3..750d280c 100644 --- a/docs/rds/umn/rds_sqlserver_scale_rds.html +++ b/docs/rds/umn/rds_sqlserver_scale_rds.html @@ -6,7 +6,7 @@

                                                                                                                                                                                                                        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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

                                                                                                                                                                                                                          +

                                                                                                                                                                                                                          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 Basic Information page. In the DB Information area, click Change in the Instance Class field.

                                                                                                                                                                                                                          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 Basic Information 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 a6b99017..80249c8d 100644 --- a/docs/rds/umn/rds_sqlserver_switch_ha.html +++ b/docs/rds/umn/rds_sqlserver_switch_ha.html @@ -5,11 +5,11 @@

                                                                                                                                                                                                                          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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                                                                            Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                                                                            +

                                                                                                                                                                                                                            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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                                                                              Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                                                                              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 Switch Primary/Standby Instances 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.
                                                                                                                                                                                                                              +

                                                                                                                                                                                                                            8. 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_sqlserver_tag.html b/docs/rds/umn/rds_sqlserver_tag.html index bf57724b..dea22a7d 100644 --- a/docs/rds/umn/rds_sqlserver_tag.html +++ b/docs/rds/umn/rds_sqlserver_tag.html @@ -4,13 +4,13 @@

                                                                                                                                                                                                                          Scenarios

                                                                                                                                                                                                                          Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

                                                                                                                                                                                                                          • You are advised to set predefined tags on the TMS console.
                                                                                                                                                                                                                          • A tag consists of a key and value. You can add only one value for each key.
                                                                                                                                                                                                                          • Up to 20 tags can be added for each DB instance.
                                                                                                                                                                                                                          -

                                                                                                                                                                                                                          Adding a Tag

                                                                                                                                                                                                                          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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                                                                            • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
                                                                                                                                                                                                                            • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                                                                            +

                                                                                                                                                                                                                            Adding a Tag

                                                                                                                                                                                                                            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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                                                                              • The tag key must be unique. It can consist of up to 128 characters. Each tag key allows letters, numbers, spaces, and the following characters: _ . : = + - @. It cannot start or end with a space, or start with _sys_.
                                                                                                                                                                                                                              • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                                                                            6. After a tag has been added, you can view and manage it on the Tags page.
                                                                                                                                                                                                                            -

                                                                                                                                                                                                                            Editing a Tag

                                                                                                                                                                                                                            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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                                                                              • Only the tag value can be edited.
                                                                                                                                                                                                                              • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                                                                              +

                                                                                                                                                                                                                              Editing a Tag

                                                                                                                                                                                                                              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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                                                                                • Only the tag value can be edited.
                                                                                                                                                                                                                                • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                                                                              6. After a tag has been edited, you can view and manage it on the Tags page.
                                                                                                                                                                                                                              -

                                                                                                                                                                                                                              Deleting a Tag

                                                                                                                                                                                                                              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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                                                                              6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                                                                              +

                                                                                                                                                                                                                              Deleting a Tag

                                                                                                                                                                                                                              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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                                                                              6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                                                                              diff --git a/docs/rds/umn/rds_sqlserver_task_0001.html b/docs/rds/umn/rds_sqlserver_task_0001.html index e80738ad..114b748a 100644 --- a/docs/rds/umn/rds_sqlserver_task_0001.html +++ b/docs/rds/umn/rds_sqlserver_task_0001.html @@ -5,7 +5,7 @@

                                                                                                                                                                                                                              You can view and manage the following tasks:

                                                                                                                                                                                                                              • Creating DB instances
                                                                                                                                                                                                                              • Creating read replicas
                                                                                                                                                                                                                              • Changing single DB instances to primary/standby
                                                                                                                                                                                                                              • Scaling up storage space
                                                                                                                                                                                                                              • Binding EIPs to DB instances
                                                                                                                                                                                                                              • Unbinding EIPs from DB instances
                                                                                                                                                                                                                              • Switching primary/standby DB instances
                                                                                                                                                                                                                              • Rebooting DB instances
                                                                                                                                                                                                                              • Restoring data to new DB instances
                                                                                                                                                                                                                              -

                                                                                                                                                                                                                              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. Choose Task Center in the navigation pane on the left. Locate the target task and view its details.

                                                                                                                                                                                                                                • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                • You can click in the upper right corner to view the progress and status of tasks in a specific period.

                                                                                                                                                                                                                                  The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

                                                                                                                                                                                                                                  +

                                                                                                                                                                                                                                  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. Choose Task Center in the navigation pane on the left. Locate the target task and view its details.

                                                                                                                                                                                                                                    • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                    • You can click in the upper right corner to view the progress and status of tasks in a specific period. The default period is seven days.

                                                                                                                                                                                                                                      The task list shows tasks that have been executed in the past 30 days.

                                                                                                                                                                                                                                    • You can view instant tasks in the following statuses:
                                                                                                                                                                                                                                      • Running
                                                                                                                                                                                                                                      • Completed
                                                                                                                                                                                                                                      • Failed
                                                                                                                                                                                                                                    • View the task creation and completion time.

                                                                                                                                                                                                                                  diff --git a/docs/rds/umn/rds_sqlserver_task_0002.html b/docs/rds/umn/rds_sqlserver_task_0002.html index cf0edf41..2e1fe7df 100644 --- a/docs/rds/umn/rds_sqlserver_task_0002.html +++ b/docs/rds/umn/rds_sqlserver_task_0002.html @@ -4,11 +4,11 @@

                                                                                                                                                                                                                                  You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

                                                                                                                                                                                                                                  Deleted task records cannot be recovered. Exercise caution when performing this operation.

                                                                                                                                                                                                                                  -

                                                                                                                                                                                                                                  Deleting an Instant Task Record

                                                                                                                                                                                                                                  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. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                    You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                    +

                                                                                                                                                                                                                                    Deleting an Instant Task Record

                                                                                                                                                                                                                                    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. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                      You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                      • Running
                                                                                                                                                                                                                                      • Completed
                                                                                                                                                                                                                                      • Failed

                                                                                                                                                                                                                                    -

                                                                                                                                                                                                                                    Deleting a Scheduled Task Record

                                                                                                                                                                                                                                    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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

                                                                                                                                                                                                                                      • If yes, go to 5.
                                                                                                                                                                                                                                      • If no, go to 6.
                                                                                                                                                                                                                                      +

                                                                                                                                                                                                                                      Deleting a Scheduled Task Record

                                                                                                                                                                                                                                      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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

                                                                                                                                                                                                                                        • If yes, go to 5.
                                                                                                                                                                                                                                        • If no, go to 6.

                                                                                                                                                                                                                                      5. Click Cancel in the Operation column. In the displayed dialog box, click Yes to cancel the task. Then, click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.
                                                                                                                                                                                                                                      6. Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.

                                                                                                                                                                                                                                        You can delete the records of scheduled tasks in any of the following statuses:

                                                                                                                                                                                                                                        • Running
                                                                                                                                                                                                                                        • Completed
                                                                                                                                                                                                                                        • Failed
                                                                                                                                                                                                                                        • Canceled
                                                                                                                                                                                                                                        • To be executed
                                                                                                                                                                                                                                        • To be authorized

                                                                                                                                                                                                                                      diff --git a/docs/rds/umn/rds_switch_ha.html b/docs/rds/umn/rds_switch_ha.html index eba6d41b..15bf82c7 100644 --- a/docs/rds/umn/rds_switch_ha.html +++ b/docs/rds/umn/rds_switch_ha.html @@ -5,11 +5,11 @@

                                                                                                                                                                                                                                      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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                                                                                        Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                                                                                        +

                                                                                                                                                                                                                                        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 DB Information area on the displayed Basic Information page, click Switch in the DB Instance Type field.

                                                                                                                                                                                                                                          Alternatively, click in the DB instance topology on the Basic Information page to perform a primary/standby switchover.

                                                                                                                                                                                                                                          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 Switch Primary/Standby Instances 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.
                                                                                                                                                                                                                                          +

                                                                                                                                                                                                                                        8. 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_log.html b/docs/rds/umn/rds_switch_log.html index 0f336214..be9469a4 100644 --- a/docs/rds/umn/rds_switch_log.html +++ b/docs/rds/umn/rds_switch_log.html @@ -4,7 +4,7 @@

                                                                                                                                                                                                                                      You can view failover or switchover logs of MySQL DB instances to evaluate the impact on services.

                                                                                                                                                                                                                                      Only failover and switchover logs within 30 days are 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 DB instance.
                                                                                                                                                                                                                                      5. In the navigation pane on the left, choose Logs. On the displayed page, click Failover/Switchover Logs to view log details.
                                                                                                                                                                                                                                      +

                                                                                                                                                                                                                                      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.
                                                                                                                                                                                                                                      5. In the navigation pane on the left, choose Logs. On the displayed page, click Failover/Switchover Logs to view log details.
                                                                                                                                                                                                                                      diff --git a/docs/rds/umn/rds_tag.html b/docs/rds/umn/rds_tag.html index 7659ad96..ee58a6d9 100644 --- a/docs/rds/umn/rds_tag.html +++ b/docs/rds/umn/rds_tag.html @@ -4,13 +4,13 @@

                                                                                                                                                                                                                                      Scenarios

                                                                                                                                                                                                                                      Tag Management Service (TMS) enables you to use tags on the management console to manage resources. TMS works with other cloud services to manage tags. TMS manages tags globally. Other cloud services manage only their own tags.

                                                                                                                                                                                                                                      • You are advised to set predefined tags on the TMS console.
                                                                                                                                                                                                                                      • A tag consists of a key and value. You can add only one value for each key.
                                                                                                                                                                                                                                      • Up to 20 tags can be added for each DB instance.
                                                                                                                                                                                                                                      -

                                                                                                                                                                                                                                      Adding a Tag

                                                                                                                                                                                                                                      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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                                                                                        • The tag key must be unique. It can consist of up to 36 characters. Only letters, digits, hyphens (-), underscores (_), and at signs (@) are allowed.
                                                                                                                                                                                                                                        • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                                                                                        +

                                                                                                                                                                                                                                        Adding a Tag

                                                                                                                                                                                                                                        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 Tags page, click Add Tag. In the displayed dialog box, enter a tag key and a tag value, and click OK.

                                                                                                                                                                                                                                          • The tag key must be unique. It can consist of up to 128 characters. Each tag key allows letters, numbers, spaces, and the following characters: _ . : = + - @. It cannot start or end with a space, or start with _sys_.
                                                                                                                                                                                                                                          • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                                                                                        6. After a tag has been added, you can view and manage it on the Tags page.
                                                                                                                                                                                                                                        -

                                                                                                                                                                                                                                        Editing a Tag

                                                                                                                                                                                                                                        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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                                                                                          • Only the tag value can be edited.
                                                                                                                                                                                                                                          • The tag value (optional) can consist of up to 43 characters. Only letters, digits, hyphens (-), underscores (_), periods (.), and at Signs (@) are allowed.
                                                                                                                                                                                                                                          +

                                                                                                                                                                                                                                          Editing a Tag

                                                                                                                                                                                                                                          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 Tags page, locate the tag to be edited and click Edit in the Operation column. In the displayed dialog box, change the tag value and click OK.

                                                                                                                                                                                                                                            • Only the tag value can be edited.
                                                                                                                                                                                                                                            • The tag value (optional) can consist of up to 255 characters. Each tag value allows letters, numbers, spaces, and the following characters: _ . : / = + - @. The tag value can start or end with a space, and it will be truncated.

                                                                                                                                                                                                                                          6. After a tag has been edited, you can view and manage it on the Tags page.
                                                                                                                                                                                                                                          -

                                                                                                                                                                                                                                          Deleting a Tag

                                                                                                                                                                                                                                          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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                                                                                          6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                                                                                          +

                                                                                                                                                                                                                                          Deleting a Tag

                                                                                                                                                                                                                                          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 Tags page, locate the tag to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.
                                                                                                                                                                                                                                          6. After a tag has been deleted, it will no longer be displayed on the Tags page.
                                                                                                                                                                                                                                          diff --git a/docs/rds/umn/rds_task_0001.html b/docs/rds/umn/rds_task_0001.html index 57b3f456..5d681b95 100644 --- a/docs/rds/umn/rds_task_0001.html +++ b/docs/rds/umn/rds_task_0001.html @@ -7,12 +7,12 @@

                                                                                                                                                                                                                                          RDS allows you to view and manage the following scheduled tasks:

                                                                                                                                                                                                                                          • Changing MySQL DB instance classes
                                                                                                                                                                                                                                          • Upgrading minor versions of MySQL DB instances
                                                                                                                                                                                                                                        -

                                                                                                                                                                                                                                        Viewing an Instant Task

                                                                                                                                                                                                                                        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. Choose Task Center in the navigation pane on the left. Locate the target task and view its details on the displayed Instant Tasks page.

                                                                                                                                                                                                                                          • To identify the target task, you can use the task name, order ID, or DB instance name/ID, or simply enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                          • You can view the progress and status of tasks in a specific period.

                                                                                                                                                                                                                                            The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

                                                                                                                                                                                                                                            +

                                                                                                                                                                                                                                            Viewing an Instant Task

                                                                                                                                                                                                                                            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. Choose Task Center in the navigation pane on the left. Locate the target task and view its details on the displayed Instant Tasks page.

                                                                                                                                                                                                                                              • To identify the target task, you can use the task name, order ID, or DB instance name/ID, or simply enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                              • You can view the progress and status of tasks in a specific period. The default period is seven days.

                                                                                                                                                                                                                                                The task list shows tasks that have been executed in the past 30 days.

                                                                                                                                                                                                                                              • You can view instant tasks in the following statuses:
                                                                                                                                                                                                                                                • Running
                                                                                                                                                                                                                                                • Completed
                                                                                                                                                                                                                                                • Failed
                                                                                                                                                                                                                                              • You can view the task creation and completion time.

                                                                                                                                                                                                                                            -

                                                                                                                                                                                                                                            Viewing a Scheduled Task

                                                                                                                                                                                                                                            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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, view the task progress and results.

                                                                                                                                                                                                                                              • To identify the target task, you can use the DB instance name/ID or enter the target DB instance ID in the search box in the upper right corner.
                                                                                                                                                                                                                                              • You can view the scheduled tasks in the following statuses:
                                                                                                                                                                                                                                                • Running
                                                                                                                                                                                                                                                • Completed
                                                                                                                                                                                                                                                • Failed
                                                                                                                                                                                                                                                • Canceled
                                                                                                                                                                                                                                                • To be executed
                                                                                                                                                                                                                                                • To be authorized
                                                                                                                                                                                                                                                +

                                                                                                                                                                                                                                                Viewing a Scheduled Task

                                                                                                                                                                                                                                                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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, view the task progress and results.

                                                                                                                                                                                                                                                  • To identify the target task, you can use the DB instance name/ID or enter the target DB instance ID in the search box in the upper right corner.
                                                                                                                                                                                                                                                  • You can view the scheduled tasks in the following statuses:
                                                                                                                                                                                                                                                    • Running
                                                                                                                                                                                                                                                    • Completed
                                                                                                                                                                                                                                                    • Failed
                                                                                                                                                                                                                                                    • Canceled
                                                                                                                                                                                                                                                    • To be executed
                                                                                                                                                                                                                                                    • To be authorized

                                                                                                                                                                                                                                                diff --git a/docs/rds/umn/rds_task_0002.html b/docs/rds/umn/rds_task_0002.html index ce2d5e9d..d133f2b1 100644 --- a/docs/rds/umn/rds_task_0002.html +++ b/docs/rds/umn/rds_task_0002.html @@ -4,11 +4,11 @@

                                                                                                                                                                                                                                                You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

                                                                                                                                                                                                                                                Deleted task records cannot be recovered. Exercise caution when performing this operation.

                                                                                                                                                                                                                                                -

                                                                                                                                                                                                                                                Deleting an Instant Task Record

                                                                                                                                                                                                                                                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. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                                  You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                                  +

                                                                                                                                                                                                                                                  Deleting an Instant Task Record

                                                                                                                                                                                                                                                  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. Choose Task Center in the navigation pane on the left. On the displayed Instant Tasks page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                                    You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                                    • Running
                                                                                                                                                                                                                                                    • Completed
                                                                                                                                                                                                                                                    • Failed

                                                                                                                                                                                                                                                  -

                                                                                                                                                                                                                                                  Deleting a Scheduled Task Record

                                                                                                                                                                                                                                                  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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

                                                                                                                                                                                                                                                    • If yes, go to 5.
                                                                                                                                                                                                                                                    • If no, go to 6.
                                                                                                                                                                                                                                                    +

                                                                                                                                                                                                                                                    Deleting a Scheduled Task Record

                                                                                                                                                                                                                                                    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. Choose Task Center in the navigation pane on the left. On the Scheduled Tasks page, locate the target task record to be deleted and check whether the task status is To be executed or To be authorized.

                                                                                                                                                                                                                                                      • If yes, go to 5.
                                                                                                                                                                                                                                                      • If no, go to 6.

                                                                                                                                                                                                                                                    5. Click Cancel in the Operation column. In the displayed dialog box, click Yes to cancel the task. Then, click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.
                                                                                                                                                                                                                                                    6. Click Delete in the Operation column. In the displayed dialog box, click Yes to delete the task record.

                                                                                                                                                                                                                                                      You can delete the records of scheduled tasks in any of the following statuses:

                                                                                                                                                                                                                                                      • Running
                                                                                                                                                                                                                                                      • Completed
                                                                                                                                                                                                                                                      • Failed
                                                                                                                                                                                                                                                      • Canceled
                                                                                                                                                                                                                                                      • To be executed
                                                                                                                                                                                                                                                      • To be authorized

                                                                                                                                                                                                                                                    diff --git a/docs/rds/umn/rds_task_pg_0001.html b/docs/rds/umn/rds_task_pg_0001.html index e85fdae4..dd2864ee 100644 --- a/docs/rds/umn/rds_task_pg_0001.html +++ b/docs/rds/umn/rds_task_pg_0001.html @@ -5,7 +5,7 @@

                                                                                                                                                                                                                                                    You can view and manage the following tasks:

                                                                                                                                                                                                                                                    • Creating DB instances
                                                                                                                                                                                                                                                    • Creating read replicas
                                                                                                                                                                                                                                                    • Changing single DB instances to primary/standby
                                                                                                                                                                                                                                                    • Scaling up storage space
                                                                                                                                                                                                                                                    • Binding EIPs to DB instances
                                                                                                                                                                                                                                                    • Unbinding EIPs from DB instances
                                                                                                                                                                                                                                                    • Switching primary/standby DB instances
                                                                                                                                                                                                                                                    • Rebooting DB instances
                                                                                                                                                                                                                                                    • Restoring data to new DB instances
                                                                                                                                                                                                                                                    -

                                                                                                                                                                                                                                                    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 Task Center page, locate the target task and view its details.

                                                                                                                                                                                                                                                      • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                                      • You can view the progress and status of tasks in a specific period.

                                                                                                                                                                                                                                                        The retention duration of failed tasks is 7 days, and of completed tasks is 1 days by default. It is controlled by two parameters on background. The retention duration cannot exceed 30 days. To set the retention duration contact O&M personnel.

                                                                                                                                                                                                                                                        +

                                                                                                                                                                                                                                                        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 Task Center page, locate the target task and view its details.

                                                                                                                                                                                                                                                          • To identify the target task, you can use the task name and DB instance name/ID or enter the target task name in the search box in the upper right corner.
                                                                                                                                                                                                                                                          • You can view the progress and status of tasks in a specific period. The default period is seven days.

                                                                                                                                                                                                                                                            The task list shows tasks that have been executed in the past 30 days.

                                                                                                                                                                                                                                                          • You can view instant tasks in the following statuses:
                                                                                                                                                                                                                                                            • Running
                                                                                                                                                                                                                                                            • Completed
                                                                                                                                                                                                                                                            • Failed
                                                                                                                                                                                                                                                          • View the task creation and completion time.

                                                                                                                                                                                                                                                        diff --git a/docs/rds/umn/rds_task_pg_0002.html b/docs/rds/umn/rds_task_pg_0002.html index c739b494..62b524b3 100644 --- a/docs/rds/umn/rds_task_pg_0002.html +++ b/docs/rds/umn/rds_task_pg_0002.html @@ -4,7 +4,7 @@

                                                                                                                                                                                                                                                        You can delete task records so that they are no longer displayed in the task list. This operation only deletes the task records, and does not delete the DB instances or terminate the tasks that are being executed.

                                                                                                                                                                                                                                                        Deleted task records cannot be recovered. Exercise caution when performing this operation.

                                                                                                                                                                                                                                                        -

                                                                                                                                                                                                                                                        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. Choose Task Center in the navigation pane on the left. On the displayed page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                                          You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                                          +

                                                                                                                                                                                                                                                          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. Choose Task Center in the navigation pane on the left. On the displayed page, locate the target task record to be deleted and click Delete in the Operation column. In the displayed dialog box, click Yes.

                                                                                                                                                                                                                                                            You can delete the records of instant tasks in any of the following statuses:

                                                                                                                                                                                                                                                            • Running
                                                                                                                                                                                                                                                            • Completed
                                                                                                                                                                                                                                                            • Failed

                                                                                                                                                                                                                                                          diff --git a/docs/rds/umn/slow_query_log-pg.html b/docs/rds/umn/slow_query_log-pg.html index 6cbf3846..6b57272f 100644 --- a/docs/rds/umn/slow_query_log-pg.html +++ b/docs/rds/umn/slow_query_log-pg.html @@ -27,7 +27,7 @@
                                                                                                                          Table 1 Audit log field description

                                                                                                                          Parameter
                                                                                                                        -

                                                                                                                        Viewing Log Details

                                                                                                                        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 Logs. On the Slow Query Logs page, view details about slow query logs.

                                                                                                                          • You can view the slow query log records of a specified execution statement type or a specific time period.
                                                                                                                          • The log_min_duration_statement parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If log_min_duration_statement is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.
                                                                                                                          +

                                                                                                                          Viewing Log Details

                                                                                                                          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 Logs. On the Slow Query Logs page, view details about slow query logs.

                                                                                                                            • You can view the slow query log records of a specified execution statement type or a specific time period.
                                                                                                                            • The log_min_duration_statement parameter determines when a slow query log is recorded. However, changes to this parameter do not affect already recorded logs. If log_min_duration_statement is changed from 1s to 0.1s, none of the previously recorded logs that do not meet the new threshold are deleted. For example, a 1.5s SQL statement that was recorded when the threshold was 1s will not be deleted now that the new threshold is 2s.

                                                                                                                        diff --git a/docs/rds/umn/slow_query_log-sqlserver.html b/docs/rds/umn/slow_query_log-sqlserver.html index 84260391..de151cdd 100644 --- a/docs/rds/umn/slow_query_log-sqlserver.html +++ b/docs/rds/umn/slow_query_log-sqlserver.html @@ -14,7 +14,7 @@

                                                                                      Specifies how many microseconds a SQL query has to take to be defined as a slow query log. The default value is 1s. When the execution time of an SQL statement exceeds the value of this parameter, the SQL statement is recorded in slow query logs.

                                                                                      You can modify the slow log threshold as required.

                                                                                      -
                                                                                      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 Logs. On the Slow Query Logs page, click in the Threshold of Slow Query Log (long_query_time) field to change the threshold.
                                                                                        • To submit the change, click .
                                                                                        • To cancel the change, click .
                                                                                        +
                                                                                        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 Logs. On the Slow Query Logs page, click in the Threshold of Slow Query Log (long_query_time) field to change the threshold.
                                                                                          • To submit the change, click .
                                                                                          • To cancel the change, click .
                                                                                          NOTE:

                                                                                          The recommended value is 1s. The lock wait time is not calculated into the query time.

                                                                                        @@ -24,7 +24,7 @@
                                                                                      -

                                                                                      Viewing Slow Query Logs

                                                                                      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 Logs. On the Slow Query Logs page, click to enable the slow query log function.
                                                                                      6. The generated slow query logs are displayed.

                                                                                        Enabling slow query log slightly affects DB instance performance.

                                                                                        +

                                                                                        Viewing Slow Query Logs

                                                                                        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 Logs. On the Slow Query Logs page, click to enable the slow query log function.
                                                                                        6. The generated slow query logs are displayed.

                                                                                          Enabling slow query log slightly affects DB instance performance.

                                                                                        7. Connect to the DB instance through the Microsoft SQL Server client.
                                                                                        8. After the DB instance is connected, run the following command to view slow query log details:

                                                                                          select * from ::fn_trace_gettable('D:\SQLTrace\audit\XXX', default)

                                                                                          XXX indicates the name of the slow query log recorded in 6.

                                                                                          @@ -32,10 +32,10 @@

                                                                                          Example:

                                                                                          select * from ::fn_trace_gettable('D:\SQLTrace\audit\SQLTrace.trc', default)

                                                                                          The result is shown in Figure 1.

                                                                                          -
                                                                                          Figure 1 Slow query log details
                                                                                          +
                                                                                          Figure 1 Slow query log details

                                                                                        -

                                                                                        Downloading a Log

                                                                                        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 Logs. On the Slow Query Logs page, click to enable the slow query log function.

                                                                                          Enabling slow query log slightly affects DB instance performance.

                                                                                          +

                                                                                          Downloading a Log

                                                                                          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 Logs. On the Slow Query Logs page, click to enable the slow query log function.

                                                                                            Enabling slow query log slightly affects DB instance performance.

                                                                                          6. Locate a log to be downloaded and click Download in the Operation column.

                                                                                            1. The system automatically loads the downloading preparation tasks. The loading duration is determined by the log file size and network environment.
                                                                                              • When the log is being prepared for download, the log status is Preparing.
                                                                                              • When the log is ready for download, the log status is Preparation completed.
                                                                                              • If the preparation for download fails, the log status is Abnormal.
                                                                                            2. In the displayed dialog box, click OK to download the log whose status is Preparation completed. If you click Cancel, the system does not download the log.

                                                                                              The download link is valid for 5 minutes. After the download link expires, a message is displayed indicating that the download link has expired. You can close the window and repeat the procedure 6 to try to download a log again.