Table of Contents

Search

  1. Introduction
  2. Samples and Examples
  3. Tools and Utilities
  4. SDK Resources

Database Performance Test Properties

Database Performance Test Properties

Before you run the database performance testing utility, configure the database performance test properties in the
TestIO.properties
file.
The following table describes the database performance test properties that you can configure in the
TestIO.properties
file:
Property
Description
jdbcUrl
JDBC URL to connect to the database.
If you specify the JDBC URL, do not specify the following database connection properties:
  • database_type
  • hostname
  • port
  • servicename
  • databasename
database_type
Type of database.
Specify one of the following values:
  • oracle. Specify if the database type is Oracle.
  • SqlServer. Specify if the database type is Microsoft SQL Server.
  • DB2. Specify if the database type is IBM Db2.
hostname
Name of the machine that hosts the database.
port
Port number on which the database is listening.
servicename
Oracle only. Name of the Oracle Service. If the Oracle connection type is SID, or if it is a Oracle RAC environment, use the
jdbcUrl
property instead.
databasename
Microsoft SQL Server and IBM Db2 only.
For Microsoft SQL Server, specify the name of the Operational Reference Store.
For IBM Db2, specify the name of the database instance in which the Operational Reference Store is present.
username
Name of the Operational Reference Store user.
password
Database password.
no_of_records
Number of records to be processed. Default is
1000
.
output_result_filename
Name of the file in which the database performance test results must be saved when the database performance testing utility is run.
If you specify only the file name, the database performance testing utility creates the file in the directory from where you run the utility.
If you specify the file name with a relative or complete path, the database performance testing utility creates the file in the specified directory.
By default, the database performance test results appear in the command window.
INFORMATICA_TESTIO_MAX_UPDATE_DELETE_ROWS
Maximum number of rows to update or delete when the database performance testing utility runs. Default is
200000
.
INFORMATICA_TESTIO_MAX_THREADS
Maximum number of Java threads to use for the DML operations of the database performance test. Default is
10
.
INFORMATICA_TESTIO_COMMIT_RECORDS
Number of rows to process before committing a DML operation. Default is
500
.

0 COMMENTS

We’d like to hear from you!