Configuring Multi-tenancy

Scenarios

This section describes how to enable and disable multi-tenancy.

Prerequisites

• Before enabling multi-tenancy, ensure that the existing database names, usernames, and tablespace names do not contain at signs (@), or the function fails to be enabled.
• The kernel version of your TaurusDB instance must be 2.0.57.240900 or later.
• Thread Pool must be enabled.

Constraints

• Multi-tenancy can only isolate tenant data, tenant vCPUs, and user vCPUs.
• Serverless instances do not support multi-tenancy.

Enabling Multi-tenancy

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > TaurusDB.
4. On the Instances page, click the instance name to go to the Basic Information page.
5. In the Instance Information area, click under Multi-tenancy. In the displayed dialog box, click OK.
6. Check that the instance status changes from Configuring multi-tenancy to Available, which means multi-tenancy is enabled successfully.

Disabling Multi-tenancy

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page and choose Databases > TaurusDB.
4. On the Instances page, click the instance name to go to the Basic Information page.
5. In the Instance Information area, click under Multi-tenancy.
6. In the displayed dialog box, click OK.
7. Check that the instance status changes from Configuring multi-tenancy to Available, which means multi-tenancy is disabled successfully.