Load Data into Database module
The Load Data into Database module is an automation tools module for Data integrity testing. This module loads a data set from a source database into a target database. It's a handy tool if your data is distributed across different database systems and you need to perform multi-source comparisons. Simply load the data from various database systems into one system and then run your tests.
You can also use the Load Data into Database module as a preparatory step for reconciliation tests as your target database becomes a repository that you can compare to a different data set.
Limitations
When it comes to loading data, keep the following things in mind:
-
Moving data around extensively is not a best practice. Try to limit the data sets you move.
-
If you're working with large data sets, you may run into performance issues with the Load Data into Database Module. For large data sets, we recommend using a tool designed for data moves instead of the Module.
Fill out the module test steps
The Load Data into Database Module helps you run tests with distributed data. This section explains the module's test steps.
You can connect to the source of your data via ODBC or JDBC.
ODBC connections have the following test steps:
|
Value |
Description |
Optional |
|---|---|---|
|
Connection |
The Data Integrity connection that you want to use. Type the connection name in the value field or select it from the dropdown menu. |
|
|
SQL Statement |
SQL statement that you want to execute. |
|
JDBC connections have the following test steps:
|
Value |
Description |
Optional |
|---|---|---|
|
Connection String |
JDBC connection string to access the database. For example: jdbc:sqlserver://1.2.3.4:49789;instanceName=SampleInstance;databaseName=TestDB;user=myUser;password=myPassword |
|
|
Class Name |
JDBC driver class name that you want to instantiate. Example: com.mysql.jdbc.Driver |
|
|
Driver Directory |
Directory of the JDBC driver. |
|
|
SQL Statement |
SQL statement that you want to execute. |
|
ODBC connections have the following test steps:
|
Value |
Description |
Optional |
|---|---|---|
|
Connection |
The Data Integrity connection that you want to use. Type the connection name in the value field. |
|
JDBC connections have the following test steps:
|
Value |
Description |
Optional |
|---|---|---|
|
Connection String |
JDBC connection string to access the database. For example: jdbc:sqlserver://1.2.3.4:49789;instanceName=SampleInstance;databaseName=TestDB;user=myUser;password=myPassword |
|
|
Class Name |
JDBC driver class name that you want to instantiate. Example: com.mysql.jdbc.Driver |
|
|
Driver Directory |
Directory of the JDBC driver. |
|
The Target section has additional test steps to define the target table:
|
Value |
Description |
Optional |
|---|---|---|
|
Table Name |
Name of the table into which Tosca Cloud loads the data. |
|
|
Create Table Statement |
To create a new table during the data load, enter a statement that specifies how to create the target table. |
X |
The Load Behavior section has the following test steps:
|
Value |
Description |
Optional |
|---|---|---|
|
Keep Existing Table Entries |
To add the data to an existing table, enter True. If you don't, Tosca Cloud drops the table before loading new data. |
X |
|
Number of rows per transaction |
Maximum number of rows that Tosca Cloud loads at a time. The default value is 1000. |
X |