Create two blank databases - one for Collaboration and one for uPerform.

Create one blank database with two schemas - one for Collaboration and one for uPerform.

Account Information for Microsoft SQL Server

Three accounts are needed for the uPerform databases and are described in the following table. The installer will prompt for names and passwords at the appropriate times.

Account Information

Description

SQL DBA Account

The installation requires an account with DBA privileges. The SQL DBA Account is used only during the installation, and can be a different account than the one used by the SQL DBA for normal database administration. If you do not wish to create a special Installation Account, you can allow the installer to use the Microsoft SQL Server system (sa) account for this purpose. If you create an SQL DBA Account for use with the installation, it must have the following privileges:

CREATE ROLES

CREATE LOGIN

GRANT PRIVILEGES

GRANT DB ACCESS

ADD MEMBER TO ROLE

NOTE: During installation, the SQL DBA Account is used to create a role called INTRASPECT_USER inside the Collaboration database and assigns it to the Collaboration User Account with the following privileges:

CREATE_TABLE

CREATE PROCEDURE

Collaboration User Account

Although the application is multi-user, during normal operation it uses one Microsoft SQL Server account called the Collaboration User Account to communicate with the Collaboration database. The application maintains all information about its users and access policies internally and does not rely on Microsoft SQL Server for managing individual user accounts. The Collaboration User Account is created as part of the installation, and your administrator chooses the user name and password at that time. All Collaboration database tables and indexes used are owned by this account.

Database User Account

Although the application is multi-user, during normal operation it uses one Microsoft SQL Server account called the Database User Account to communicate with the database. The application maintains all information about its users and access policies internally and does not rely on Microsoft SQL Server for managing individual user accounts. The Database User Account is created as part of the installation, and your administrator chooses the user name and password at that time. All database tables and indexes used are owned by this account.

NOTE: During installation, the Database User Account is assigned the role of DB_OWNER for the database if you do not specify a pre-existing database user. If you specify a pre-existing user, that user must have the database set as the default database and cannot have the system administrator role.