This section provides guidelines for creating the Tivoli® Data Warehouse database
using Microsoft SQL Server
2000, 2005, and 2008.
For specific instructions on how to create a Microsoft SQL Server database, see the Microsoft SQL Server documentation
or have a database administrator create the database for you.
When you create the warehouse database using Microsoft SQL Server, follow these guidelines:
- Connect to the Microsoft SQL
database server and create the Tivoli Data
Warehouse database using the system administrator (sa) user.
- Create a database user login name and password that the warehousing
components (portal server, Warehouse Proxy Agent, and Summarization
and Pruning Agent) can use to access the data warehouse. In these
instructions, this user account is referred to as the warehouse
user.
You must have SQL Server authentication to create the
warehouse user.
Note: The warehousing components must not use
the system administrator (sa) user to connect to the data warehouse.
- Consider using the default values shown in the following table
for the warehouse name and warehouse user. The default values are
used in the configuration procedures for connecting the warehousing
components to the warehouse database.
Table 1. Default
values for Tivoli Data Warehouse
parameters| Parameter |
Default value |
| Tivoli Data
Warehouse database name Note: When connecting to a DB2® on z/OS® database,
this value is unnecessary.
|
WAREHOUS |
| User name |
ITMUser |
| User password |
itmpswd1 |
- If the Warehouse Proxy and Summarization and Pruning Agents create
database objects at runtime, you must give the warehouse user public and db_owner privileges
to the Tivoli Data Warehouse
database.
The warehouse user may have much fewer rights if the
schema publication tool is used to create the database objects. If
the schema tool is used, the warehouse user needs only the db_datareader and db_datawriter roles.
If the warehouse user has limited privileges, the schema tool must
be used to create any additional database objects (using the schema
tool's updated mode) if the historical configuration is changed; see Schema Publication Tool.
- For Microsoft SQL Server
2005 and 2008, do the following:
- Create a schema with the same name (and owner) as the database
user login name (for example, ITMUser) and change
the default schema for the user from dbo to this
login name. (This step is not necessary if you are using Microsoft SQL Server 2000.)
- Make sure the database is set up to support inbound network TCP/IP
connections.