Preview: Complete Row by Row Comparison (DI Agent)

The Preview - Row by Row Comparison (DI Agent) Module is a preview Module that you can try out. Since this Module requires further development, Tricentis can't guarantee full functionality or usability at this stage.

With the Preview - Row by Row Comparison (DI Agent) Module, you can run a row-by-row-level comparison on an agent that is installed either locally or on a remote computer.

For information on the Data Integrity Agent, see chapter "Preview: Data Integrity Agent".

For information on how to run row-by-row tests in Tricentis Data Integrity, see chapter "Run Reconciliation tests".

Get the Preview - Row by Row Comparison (DI Agent) Module

The Module is part of the Data Integrity Agent installation package Tosca Data Integrity Agent Package <version>. You can download it from the Tricentis Support Hub.

Create a Row by Row Comparison (DI Agent) TestCase

A TestCase that you create with the Preview - Row by Row Comparison (DI Agent) Module has the same ModuleAttributes as regular reconciliation tests, with two notable exceptions:

  • The Preview - Row by Row Comparison (DI Agent) TestCase has an additional TestStep named Agent, where you specify the connection to the agent.

  • Instead of a Databases TestStep, the TestCase has a JDBC TestStep because the Data Integrity Agent is exclusively for JDBC.

To create a TestCase with the Preview - Row by Row Comparison (DI Agent) Module, follow these steps:

  1. Create a new TestCase.

  2. Drag and drop the Preview - Row by Row Comparison (DI Agent) Module onto the TestCase or use Fuzzy Search.

  3. Fill out Agent:

Parameter

Description

Address

Address of the machine where the Data Integrity Agent runs. You can use localhost, the name of the remote computer, or an IP address.

By default, the agent communicates on HTTP port 80 and HTTPS port 443. If you have specified your own port, add it after the agent name separated by colon.

Examples: localhost, RemoteComputerName:1234, 1.2.3.4:1234, localhost:1234

  1. If your source and/or target data is a database, perform the following actions:

ModuleAttribute

Description

Optional

Connection String

JDBC connection string to access the database.

Example: jdbc:sqlserver://1.2.3.4:49789;instanceName=SampleInstance;databaseName=TestDB;user=myUser;password=myPassword

  

Class Name

Name of the class in the JDBC driver. If you don't know the class name, see our FAQ page for help.

Example: com.mysql.jdbc.Driver

  

SQL Statement

Enter any SQL statement. You can use the SQL Editor to create and test SQL statements before you run your TestCase.

 

Options - Fetch Size

Number of rows that the TestCase fetches from the database in one request. If you don't specify the fetch size, Data Integrity uses the default value of your JDBC driver.

We recommend that you fetch 10 to 20 percent of your data size. When you compare large data sets, the small default fetch size of some JDBC drivers results in a high number of requests to the database server. This reduces the comparison speed.

  • If your rows have little information, you can increase the fetch size. This reduces the number of calls to the server and increases speed.

  • If your rows have a lot of information, we recommend that you use a smaller fetch size to save memory space.

X

  1. Fill out all other TestStepValues. Click here for information on reconciliation TestStepValues.

In this example, you compare data from a database to a local Parquet file. To do so, you enter the following information into your Preview - Complete Row by Row Comparison (DI Agent) TestCase:

  • Agent->Address contains the address of the machine where the agent runs.

  • Your source is a database, so you specify the connection details in Source->JDBC.

  • To specify the target data, you enter the path to the file into Target->Parquet->Local->Path.

Row-by-row comparison between a database and a Parquet file

You can now run your TestCase.

What's next

Now that you've created your TestCase, you are ready to run your tests.

Once execution is finished, you can check the logs and error reports that the Data Integrity Agent creates.