Why does the root account not have the super permissions?
The eSurfing Cloud RDS for MySQL does not provide super permissions for the root account. The super permissions allow you to execute many management commands, such as set global..., kill..., etc., which is likely to destroy the instance cluster and cause the instance to fail. For some scenarios that require super permissions, RDS for MySQL provides service-based capacities, allowing you to bypass super permission restrictions in other ways. Here are some examples:
• Global parameter modification: When you log in to the database and use set global parameter name = parameter value to modify the global parameter, an error about insufficient permissions will be reported. You can implement parameter modification and parameter management on the console.
• Execution of other parameters: When you execute the create definer='root'@'%’ trigger(procedure)…, an error about insufficient permissions will be reported due to a lack of super permissions. You can remove the definer='root' keyword to resolve this issue.
Introduction to RDS for MySQL Built-in Accounts
The built-in account of eSurfing Cloud RDS for MySQL is automatically created when the instance is created (not available for the users). They are used to provide comprehensive background operation and maintenance management services for the database instance. The list is as follows:
• RDS_sla: Used for data synchronization.
• RDS_agent: Used for cluster management, database backup, and restoration.
• RDS_gw: Used for access control.
• RDS_orzdba: Used for indicator monitoring.
• RDS_telemonitor: Used for database control.
Does RDS for MySQL support multiple accounts?
Yes, RDS for MySQL supports multiple accounts. You can create accounts and manage account permissions on the console to control different accounts and access different tables.
Can multiple users log in to the database through DMS? Will the accounts be locked if I enter the wrong password several times?
Multiple users can log in to the database through DMS. The accounts will not be locked if you enter the wrong password several times.
If you forget your database account password, you can reset it on the console. For details, see User Guide-Instance Management-Modifying the Instance Password.
How do I view the authorized databases after account login?
After connecting to the database on a local client, execute select user(); to view the current user information. Then, execute the following two commands to view the database that can be viewed by the current user, where user_name is the user name of the current account and ip is the client IP.
show grants for 'user_name'@'ip'; |
show grants for 'user_name'@'%'; |