Database Compare
Learn how to set-up and configure the Database Compare activity. Running a comparison can compare data across schemas, databases or using snapshots. This page shows the Test Automation Data Activity for Database Compare.
There are 3 ways of running a Database Compare (1) as a High Watermark Comparison (8mins 14secs), as a Snapshot Comparison (7mins 42secs) and Database to Database (not shown - the mechanism is the same as Snapshot Comparison but using another connection profile rather then a Snapshot). Also see the benefits overview clip of Database Compare (2 mins).
Database Compare - Overview (2 mins)
https://www.youtube.com/watch?v=qAcSFi3mpiQDatabase Compare - How to:
Run a High Watermark Comparison (8mins 14secs)
https://www.youtube.com/watch?v=0v_i8TBwXk4Tip for usage of High Watermark comparison method: when you don’t have control over the database to create a new schema or table, look for the most recently inserted data before and after a test has finished.
What you’ll see covered in the clip - Initial set-up:
Checking for a Database Scan and ensure you have a Definition
Creating a new item and choose a type
Attaching the pre-defined and most recent version of a database Definition
Creating a configuation list to automatically generate the SQL statements
Choosing and executing a specific schema
Picking up a configuration list
Choosing the run type
Previewing the outcome
Then, you’ll see covered:
Creating and checking for new rows only list
Querying database with connection profile
Picking off the recent/highest values in all the Primary Keys for the tables (at this point in time)
Seeing the testing process
Detecting using the High Watermark method
Comparing the configuring lists for changes
Running a compare of newly inserted data
Downloading database compare results to verify which rows of newly inserted data have been added before and after the process you want to test
Run a Snapshot Comparison (7mins 42secs)
Snapshot an Oracle database as an example to compare data before and after testing is finished.
https://www.youtube.com/watch?v=JdKAO6DOUzMTip for usage of Snapshot Comparison method: when you are going across a database set the _SNAP to blank*.
What you’ll see covered in the clip - Initial set-up:
Selecting a database a a registered Definition
Executing a build compare configuration list
Previewing the tables you want to work with
Seeing the attached component, ie list, in the Data Activity
Previewing the list of the information for the compare process to run with Primary Keys and source/target SELECT clauses
Seeing and redefining _SNAP* which indicates database snaphots will be created to compare against
Then, you’ll see covered:
Checking and previewing jobs and attachments in the activity audit in descending time order
Seeing the SQL that’s been issues to Snapshot the database (5 different file types)
Creating a SQL script and moving it to the server for use in a form for the user to create a Snaphot and Compare the the database, they normally don’t come into the Activity to run it
Locating and modifying the parameters in the generated form
Executing the Snapshot
Creating a Submit form for the compare activity
Run a Database to Database Comparison
(not shown - the mechanism is the same as Snapshot comparison using another connection profile rather then a Snapshot)
General info on running Jobs for Data Activities
A database activity is created by adding components into the activity including and not exclusively: a Definition version, Submit form, an existing Compare Configuaration list. Also see the available specific Actions, including but not exclusively, for a user to Submit the compare, or generate a form to Snapshot a database.
A Data Activity job can be executed from within the Data Activity space or from the VIP Executor (where a user normally requests jobs). The user then sees a spreadsheet to show the differences in rows of inserted or edited data before and after a test has finished.
Available Data Activities
Data Activities are tools for the classification, organisation and versioning of core data assets across the development cycle.
