The Database Services (DBS) and multi-tenancy (MT) enables DBaaS or allows cloud service providers to integrate the SQL/MX RDBMS into their cloud environment, thus providing self-servicing, seamless provisioning and managing of SQL/MX databases. The existing NonStop SQL/MX users can leverage DBS by configuring the existing system to host multiple databases on a single NonStop server, maximizing system utilization without compromising on security.

Traditionally, SQL/MX is a single instance RDBMS on a NonStop server. All users on the system have access to metadata tables in system schemas (in the system catalog) and definition schemas (in the user catalogs). Resources such as CPUs and TMF audited volumes are available for database use. Any user connected to the RDBMS has visibility into all user catalogs.

SQL/MX provides MT support for cloud environments with the ability to host multiple, isolated instances of a database on a single NonStop server. The databases in MT environment are isolated from each other, that is, a user accessing a database in an MT environment does not have visibility into other databases on the system or other user catalogs. Dedicated data volumes are assigned to each database in an MT environment. The data volumes are protected by Safeguard allowing access only to the users associated with the database. The MT isolation features prevent database users from using data volumes that are not associated with the database.

DBS is a deployment model where the application owners acquire access to a database, maintained by a database provider. A user database is isolated from other databases in the system, though, they may be served by the same server and DBMS. To create and manage databases in an MT environment, use the mxdbs utility, which is an OSS command-line tool. The mxdbs utility can be integrated with management tools or a cloud platform as a self-service model for end users.