TeamConnect Data Warehouse has the following prerequisites:

• Understanding of relational databases
• Knowledge of information systems
• Basic command line and shell scripting skills
• Basic knowledge of enterprise reporting
• SQL Query Analyzer for MS SQL server
• SQL*Plus for Oracle
• Administrative privileges for database access. The user who runs the Data Warehouse scripts and the routine refresh jobs must have the same database privileges as those mentioned in the Installation Requirements section. In addition, on Oracle, the user must have the privilege CREATE MATERIALIZED VIEW. For "target" databases in Oracle, your user ID must have DDL privileges assigned directly to that user ID, not through a role.
• If your TeamConnect database is Oracle, you need the TeamConnect schema name and user information.
• If your TeamConnect database is SQL Server, you need the TeamConnect database name and user information.
• During configuration you must specify a "source" database (the one which contains your existing TeamConnect data) and a "target" database, which will contain the transformed tables used by Data Warehouse. The "target" database, and an appropriate user ID, must exist before you run the Data Warehouse installation. Based on testing of Data Warehouse, you should expect the target database size to be between 80% and 150% of the size of the source database, excluding space occupied by documents in the source database. However, your actual size may vary due to the size and complexity of your TeamConnect design and your usage of custom fields and categories. To determine the approximate space used by documents, run the following query:

select round(sum(document_size)/(1024*1024),2) SIZE_MB from t_document

Subtract this number from the overall size of the source database, in megabytes. Then multiply the answer by a factor between 0.8 and 1.5 and use the result as the size of the target database.

• During execution of Data Warehouse scripts (both installation and routine refreshes) a large number of simultaneous database connections are required—approximately 60 connections to the source database and 150 connections to the target database during the most intensive portions of the job. You must insure that your database servers are able to accept these additional connections, in addition to performing whatever other tasks are running at the time.
• The source database must not contain custom field names that are considered reserved words by the database server. Examples of reserved words are TABLE, SELECT, DEFAULT, CHECK, etc. If such custom field names already exist in your source database, a workaround is to alter the custom field definitions and insure that the check box "Include in Reporting" (or "Include in Data Warehouse") is not checked.
• The source database server and the target database server must use the same character set.