Teradata-Specific Database Guidelines for Oracle Business Analytics Warehouse
3-8
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
database data.
Full load:
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
Warehouse
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
Nested triggers
1
Network packet size
8192 B
Default is 4096.
Open objects
0
Priority boost
0
Query governor cost limit
0
Modify to 60 only if CPU is high.
Query wait
1 sec
Recovery interval
0 min
Remote access
1
Remote login timeout
20 sec
Remote proc trans
0
Remote query timeout
600 sec
Scan for startup procs
0
Set working set size
0
Two-digit year cutoff
2049
User connections
0
User options
0
Table 34
(Cont.) Recommended Variable Settings for SQL Server Databases
Parameter
Recommended
Setting
Notes