User Name and Password Problems

Consistent use of user names and passwords is often a problem in installing, configuring, and using Integration Services, because of the numerous software components and computers that make up the system.

Tip:	During installation, configuration, and testing, keep a list of all user names and passwords that you use to create or to modify the system, including the applications with which the user names and passwords are associated and the purpose of each application.

In a smaller, single-server implementation of Integration Services, where Integration Server, Essbase Server, and the data source are all run on a single computer, you must manage five user name and password sets and use them consistently:

User account on the Integration Services client computer
User account on the computer that runs all the server software
OLAP Metadata Catalog database in the data source
Data source database in the data source
Essbase Server software

In a fully distributed, three-server implementation, where Integration Server, Essbase Server, and the data source are all run on separate computers, you must manage seven user name and password sets and use them consistently:

User account on the Integration Services client computer
User account on the computer that runs Integration Server
User account on the computer that runs the data source
OLAP Metadata Catalog database in the data source
Data source database
User account on the computer that runs Essbase Server
Essbase Server software

Adding aliases or synonyms to the data source databases adds to the number of user name and password sets you must manage.

Tip:	During installation and connection testing, use a single set of user names and passwords to avoid confusion. Add user aliases or synonyms after the system is configured and running.