Creating multiple database instancesAdded by IBM on February 11, 2013 | Version 1 (Original)
|Create multiple instances of a database for a more versatile database environment.
Before you begin
This is an optional procedure. If you need to have only one database instance (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 group.
Note: If you are using DB2®, add the new user to the DB2ADMNS group as well.
- Remove the user account from the Users group.
- Grant rights to the new user:
- Click Start -> Run and enter secpol.msc.
- Expand Local Policies and click User Rights Assignment.
- Open each of the following rights, click Add User or Group, and add 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 several benefits:
- the ability to use different instances for development and production.
- restricted access to sensitive information.
- an optimized 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 restarting 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.
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.
- Ensure that Named Pipes is enabled in the SQL Server Network Configuration for all instances. For more information, refer to your SQL Server documentation.
- Use the same collation that you are using for the application databases; that is: Latin1_General_BIN. Ensure that the ancillary databases, such as the master, model, tempdb, and msdb databases, use that collation.
- 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
Configuring the DB2 databases for unicode
Creating databases with the database wizard
Creating databases with SQL scripts
Enabling NO FILE SYSTEM CACHING for DB2 on System z