Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Installing Software AG Products On Premises | Installing Products, Creating Database Components, and Connecting Products to Database Components | Installing Products Using Software AG Installer and Creating Database Components Using Database Component Configurator | Create Database Components Using Database Component Configurator
 
Create Database Components Using Database Component Configurator
 
Install the Database Component Configurator and Database Scripts
Database Component Configurator Graphical User Interface
Database Component Configurator Command
Examples
This section explains how to use the Database Component Configurator to create or drop database users and storage, and to create or drop Software AG database components. When creating these objects, follow the guidelines below.
*Never create your own database tables in the same schema or database as a Software AG database component.
*Software AG strongly recommends using the Database Component Configurator to create database storage, tablespaces, and filegroups, and to create database users for all RDBMSs, with two exceptions (see below). If you must instead create these objects manually (for example, because of security requirements), go to the Software AG_directory /common/db/DCC/Storage/scripts/release/RDBMS directory, open the RDBMS_str_c_ddl_user.sql file, and grant the permissions listed in that file.
The two exceptions are PostgreSQL or when using non-DBO schemas for SQL Server. For these two cases, do not use the Database Component Configurator to create database users and storage, but instead follow the instructions in the previous sections.
*You can create one database user for multiple database components, or you can create a separate database user for each database component.
*You can create all database components in the same storage, or you can create each database component in its own storage.
*For Oracle and Tibero, Software AG scripts require ALTER SESSION permission at the time of creating database tables. You can revoke this permission after the tables have been created.
*The table below shows the storage convention that all Software AG database components follow by default. You can use a different convention when you create storage. (For PostgreSQL there are no storage conventions and tablespaces are not used.)
RDBMS
Data Storage Unit
Index Storage Unit
BLOB Storage Unit
DB2 tablespaces
WEBMDATA
WEBMINDX
WEBMBLOB
MySQL
Default
Default
Default
Oracle or Tibero tablespaces
WEBMDATA
WEBMINDX
WEBMDATA
SQL Server filegroups
Primary
Primary
Primary