This topic describes the permission scope of each account type. This topic also describes how to modify the permissions of a standard account or a privileged account on an ApsaraDB RDS for SQL Server instance. A system admin account has all permissions on all databases. You do not need to modify the permissions of a system admin account.
Account permissions
For security purposes, ApsaraDB RDS limits specific permissions. The limited permissions are encapsulated in stored procedures. You can run the stored procedures to perform the operations on which the permissions are limited. For more information, see Stored procedures.
You can grant accounts the permissions on the databases of your RDS instance in the ApsaraDB RDS console. If you want to grant accounts the permissions on specific database objects, such as tables, you can execute the required SQL statements. For more information, see GRANT object permissions (Transact-SQL).
System admin account
Authorization objects: all databases.
Permissions: all permissions on the RDS instance. For more information, see Permissions (Database Engine).
Standard account and privileged account
Authorization objects: databases of the account.
Permission type | Role | Permission |
Owner |
| |
read-only |
| |
Read and write permissions (DML) |
|
Global read-only account
Authorization objects: All user databases on the instance.
Permission type: Read-only. These permissions automatically apply to new databases.
Modify the permissions of an account
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
In the navigation pane on the left of the page that appears, click Accounts.
Find the account for which you want to modify permissions and click Change Permissions.

In the Edit Account Permissions panel, modify the permissions of the account.
Change the authorized databases: Select the databases for which you want to grant the permissions to the account and click the
or
icon to change the authorized databases. Modify the account permissions: In the Authorized Databases section, configure the permissions as needed.
Read-Only: Assigns the
db_datareaderdatabase role in SQL Server.Read/Write (DML): Assigns the
db_datawriteranddb_datareaderdatabase roles in SQL Server.Owner: Assigns the
db_ownerdatabase role in SQL Server.
For more information about database-level roles, see Database-level roles.
Click OK in the message that appears.
FAQ
I cannot use the account that has the read/write (DML) permissions to create a table in the database. Why?
A: An account with Read/Write (DML) permissions is assigned the standard
db_datareaderanddb_datawriterdatabase roles in SQL Server. These roles do not include theCREATE TABLEpermission. For more information, see Account permissions. To create tables in the database, you can use one of the following methods:Method 1: Execute the required SQL statements. For more information, see GRANT Database Permissions (Transact-SQL) and Database-level roles.
Method 2: Log on to the ApsaraDB RDS console. On the Accounts page of your RDS instance, change the permission type of the account to Owner. The Owner permission type has most permissions, including creating tables. Proceed with caution. For more information, see Modify the permissions of an account.
If you only need to grant the
CREATE TABLEpermission, use Method 1. This method provides a higher level of security.