Before you begin
This is an optional procedure. If you need to have only one database instance (or, in Oracle terminology, one database), you can skip this task.
® only) Complete the following steps for each instance that you plan to create:
- Create a new user and add it to the Administrators and DB2ADMNS groups.
- Remove the user account from the Users group.
- In the Local Security Policy utility, add these rights to the new user:
- Act as part of the operating system
- Adjust memory quotas|Increase quotas for a process
- Create a token object
- Debug programs
- Lock pages in memory
- Log on as a service
- Replace a process level token
The new account uses the local system as the domain.
About this task
A database environment with multiple instances provides the flexibility to tune an instance for a particular configuration, use different instances for development and production, restrict access to sensitive information, and optimize the database manager configuration for each instance. For example, if you need to make changes to one of the instances, you can restart just that instance instead of the whole system. Similarly, if you need to take an instance offline, only the databases that are hosted on that instance are unavailable during the outage, while your other databases are unaffected.
® only. If you are hosting IBM
on a single 32-bit system, you should create multiple DB2
instances. A single DB2
instance on a 32-bit system can manage a maximum of 2 GB of data in memory and this can become a constraint when you install multiple IBM
Connections applications. At a minimum, create two DB2
instances when you are installing all the applications, but also consider creating separate instances for the Activities and Communities databases because they are usually the most memory-intensive databases. Ideally, you would install one DB2
instance per IBM
Connections application. If you are hosting DB2
on a 64-bit system, you do not need to create multiple instances, provided the system has sufficient RAM.
Multiple instances require additional system resources.
To create multiple instances of a database, complete the following steps:
Choose your database type:
- Run the SQL Server installation wizard. On the Instance Name panel of the installation wizard, select Named instance, and then specify a new instance name in the field.
- Edit your firewall configuration to allow the new instances to communicate through their listening ports.
- Use the same collation that you are using for the application databases; that is: Latin1_General_BIN
- For Authentication mode, use Mixed Mode (Windows Authentication and SQL Server Authentication)
- If you receive any warnings or errors from the System Configuration Check dialog, correct them from the SQL Server 2005 instance installation
For more information, go to the Microsoft SQL Server Developer Center web site
to view the SQL Server documentation:
What to do next
When you create multiple database instances, you must install the databases on each instance. If you are using the database wizard to install the databases, you must prepare and run the database wizard once for each instance and if you are using the scripts to install the databases, you must run the scripts once for each instance.
Parent topic: Creating databases
Registering the DB2 product license key
Creating a dedicated DB2 user
Creating databases with the database wizard
Creating databases with SQL scripts
Enabling NO FILE SYSTEM CACHING for DB2 on System z