Databases

Installation Options

From 7.0 SP02 on, databases can be installed:

  • on one physical server, in the same SQL instance, and in the same database. This was the only supported method in SP00 and SP01.

  • on one physical server, in the same SQL instance, and in different databases. This requires that MSDTC is running.

  • on one physical server, in different SQL instances, and in different databases. This requires that MSDTC is running.

  • on several physical servers, in different SQL instances, and in different databases. This requires that MSDTC is running.

The first option – databases installed on one physical server, in the same SQL instance, and in the same database – can be used for small systems for its efficiency and easy maintenance.

To prepare for the possible later distribution on separate database servers, or to optimize functions of a specific logical database (such as searches on Directory database), it is advisable to locate databases in different databases already on a single server. Thus, databases can be later on moved on separate disks without specific data migration process.

For example, consider the following issues:

  • Requirements for Directory, Operative, and Configuration database optimization may be different because of their different usage model: Directory database includes large amounts of information that is only searched, and typically updated with large batch updates, whereas Operative database is constantly updated with several small updates, and Configuration database is relatively static but its availability and search response time affect a lot to users’ logon experience. Response time of relatively small operations in Operative database has a remarkable effect on overall response time. Thus, some customers may want to guarantee Configuration and Operative database availability and response times in all circumstances by separating those databases from the Directory database.

  • The customers that run large Outbound campaigns may benefit of locating the Outbound database on a separate disk.

  • The customers that can afford massive top-speed disk packs do not need to worry about location issues to the same extent as the customers with limited disk resources.