Using a Single Database[6]

Instead of creating multiple databases for each of your datastores, region databases and cross-region databases, MFDBFH allows you to store multiple datastores, region-databases, and a single cross-region database, in a single physical database. This is facilitated by using unique database schema names to differentiate between the resources. If you view the contents of your databases in your vendor's database management tool, you can see the resources grouped under their own unique schemas:

Resource type	Schema Name Format	Notes
Cross-region	DBRG__XREGN_	This is a fixed schema name used for cross-regions, meaning that only one cross-region may exist in any given physical database.
Datastore	DBFH_<datastore-name>	For example, if the datastore name is VSAM, its associated schema name will be DBFH_VSAM
Region	DBRG_<region-name>	For example, if the region name is ESDEMO, its associated schema name will be DBRG_ESDEMO

Using a single database is optional, but from a performance point of view, it is advantageous to store related resources all in one place. It also allows connection sharing, which significantly reduces the number of connections required for each process; see Sharing Database Connections.

The alternative to using a single database is that you use individual databases for each resource (datastores, region databases, and cross-region database). For a single operation/transaction, each resource will require separate connections, which is obviously less efficient.

Note: Regardless of the storage method you use, additional connections may also be required for other MFDBFH-related processes.

The database creation instructions within the configuration sections explain how to create the resources using both a single and separate databases.