Teradata-Specific Database Guidelines for Oracle Business Analytics Warehouse
Oracle Business Intelligence Applications Installation Guide for Informatica PowerCenter Users
SQL Server memory:
Make sure adequate memory is available.
Transaction logs and TempDB:
Reside on a separate disk from those used by
Full Recovery model for the database.
Incremental (Refresh) load:
Change from Full to Bulk-Logged Recovery model.
3.5 Teradata-Specific Database Guidelines for Oracle Business Analytics
This sections contains the recommended best practices and guidelines for maximizing
performance in Teradata deployments. It contains the following topics:
Section 3.5.1, "Installation of Required JDBC Driver for Teradata Databases"
Section 3.5.2, "General Guidelines for Teradata Deployments"
Section 3.5.3, "Best Practices For Teradata Deployments"
3.5.1 Installation of Required JDBC Driver for Teradata Databases
The Data Warehouse Administration Console (DAC) requires JDBC drivers for
database connectivity. You should only use JDBC drivers that are compatible with the
supported databases. For information about supported databases, see System
Requirements and Supported Platforms for Oracle Business Intelligence Applications. Since
JDBC drivers show variations with different database versions, only drivers that are
shipped with the database or downloaded from the database vendor site and are
Network packet size
Default is 4096.
Query governor cost limit
Modify to 60 only if CPU is high.
Remote login timeout
Remote proc trans
Remote query timeout
Scan for startup procs
Set working set size
Two-digit year cutoff
(Cont.) Recommended Variable Settings for SQL Server Databases