When you create a Database Table instance for a class, the table name equals the Couchbase bucket.

1. If the database platform of the additional database differs from the database platform of Pega Platform, or does not use postgresSQL, define Pega Platform the database driver. For more information, see Defining the database driver.
2. In the header of Dev Studio, click CreateSysAdminDatabase.
3. Enter a short description, and in the Database field, enter a name for the additional database.
   The database name is case-sensitive.
4. Click Create and open. The Edit <YourNewDatabaseName> Database page appears.
5. Optional: To indicate the system of record, in the Integration system field, press the Down arrow key and select the name of the integration system to associate with this database.
   The value that you select is for informational purposes only, and does not affect the behavior of the database instance. You can use this value to organize rules for integration connectors, data types, and sources for data pages.
6. In the How to connect list, click Use Cassandra configuration listed below.
7. In the Cassandra Hostnames and Ports section, click Add Host, and then enter a hostname or IP address and port for a node in the Cassandra cluster.
   You can specify multiple hosts.
8. In the Cassandra Cluster section, enter the Keyspace, Username, and Password that you use when connecting to the database.
9. Optional: On the Advanced tab, specify the names of other database instances that should be reachable by views in this database.
   1. Under the Database Name list, click the Add item icon.
   2. In the Database Name field, press the Down arrow key, and select the name of a database instance that views in the external database need to access.
   For example: This database instance describes the EXTERNAL1 database. Your Pega application needs to access a view in EXTERNAL1 that joins data from the DATA1 and DATA2 databases. Do the following steps:

   • Define database instances for DATA1 and DATA2.
   • On the database instance for EXTERNAL1, list DATA1 and DATA2 as other databases.
10. Click Save.
11. To test the database connection, on the Database tab, click Test connection.
    • If the test fails, diagnostic information appears in a new window. Modify the database instance until the test succeeds.
    • This test does not test the administrative user, if any, that you might have specified.