Hi everyone, welcome to the sixth chapter in our Tencent Cloud sys ops associate course, cloud database operation practices. At the end of this chapter you'll be able to configure a variety of Tencent cloud database products, connect and access Tencent cloud databases and migrate data to Tencent cloud databases. In this chapter, we'll cover eight sections, TencentDB for MySQL, TencentDB for MariaDB, TencentDB for SQL server, TencentDB for PostgreSQL, TencentDB for Redis, TencentDB for MongoDB, Tencent distributed SQL TDSQL and Data Transmission Service DTS. This video will cover the first section, TencentDB for MySQL configuration. Subsequent videos will cover the remaining sections. Let's start with section one, TencentDB for MySQL configuration. In this video we'll cover the TencentDB for MySQL configuration process, initializing TencentDB for MySQL databases, accessing TencentDB for my SQL cloud databases. TencentDB for MySQL management, importing and migrating data offline and TencentDB for MySQL instance and lifecycle management. The objective of this section is to introduce the basic operations of TencentDB for MySQL including database initialization, access, data importing and migration and database instance and lifecycle management. To initialize TencentDB for MySQL databases, log into the Tencent cloud console and navigate to TencentDB for MySQL. Go into the instance list, select a created MySQL database and click initialize, then configure the initialization parameters including the supported character set whether the table name is case sensitive, the custom port and the root account password. Accessing TencentDB for MySQL databases can be done either through private network access or public network access. You can use private network access to access TencentDB for MySQL databases, on Windows, you can access the databases from the Windows system using a standard SQL client. On Linux instances, you can access databases using the MySQL client. To access TencentDB for MySQL databases using public network access, first enable the public network access on the TencentDB for MySQL console as shown in the image here. Use the command shown here and enter your password when prompted to access the database from the public network. Now let's look at TencentDB for MySQL management, there are various TencentDB for MySQL management operations including viewing the instance details, instance monitoring, managing databases, configuring security groups, back up and restoration, operation logs, setting read only instances and connection checks. To import and migrate data offline first create a new DTS data migration service, then choose the database and download the backup file to the local computer. Finally restore the data using the MySQL command line tool. You can create a new DTS data migration task by logging into DTS on the Tencent cloud console. Then choose a database and download the backup file to the local computer as shown in the image here. Finally, restore the data using the MySQL command line tool to complete data migration. You'll need to enter the backup file name and your password to complete this process. Now let's look at TencentDB for MySQL database instance and lifecycle management. A master instance is an instance containing a read only instance that is both readable and writable and is visible in the instance list. A read only instance is an instance that only provides the read function and must belong to a master instance. A disaster recovery instance provides disaster recovery across availability zones and regions. The disaster recovery instance is only readable during synchronization but can be upgraded as the master instance. There are several different replication types for TencentDB for MySQL database instance and lifecycle management. Asynchronous, semi-synchronous and strongly synchronized replication. During asynchronous replication, the primary instance immediately returns the response to the application after performing the update. And then the primary instance copies the data back to the secondary instance. The primary instance does not need to wait for the secondary instance to respond during the day to update process. During semi-synchronous replication, the primary instance copies the data to the secondary instance immediately after performing the update. The secondary instance receives the data, writes it to the relay log and returns the success message to the primary instance. During strongly synchronized replication, the primary instance copies the data to the secondary instance immediately after performing the update, the secondary instance returns the success message to the primary instance only after it receives the data and executes it. You can also perform data roll back to a specific point in time. On the TencentDB for MySQL console, navigate to the instance list and click on more and roll back to begin this process.