Browse Prior Art Database

System and method for speed up database test data population

IP.com Disclosure Number: IPCOM000219435D
Publication Date: 2012-Jun-29
Document File: 3 page(s) / 38K

Publishing Venue

The IP.com Prior Art Database

Abstract

Here are proposed a system and method to fastly populate a database with the required performance test database data.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

System and method for speed up database test data population

Agile methodology and always faster and faster development processes do not fit with end to end performance test and the required database population needed to emulate customer environments or meaningful workloads. Moreover customer database are not easily accessible and often not at the release level needed to be tested.

Using specifically developed SQL scripts requires to know and understand the schema and all the constraints could exist, but this is typically not easy and time consuming without development help. Automation tool, can also be used for that even if this is not their main purpose but they require specific tests (step sequence) to be developed and they will interact with the product as any other user would do, introducing therefore the additional processing associated with the UI.

Basically this way consists in realizing a work around using an existing tool not specifically designed for that.

What it is proposed here here is a system and method to fastly populate a database with the required performance test database data. The system and method proposed consists in:


a recording phase during which interaction with the database will be sniffed. This means the user will execute from UI at least once all the steps needed to create the object involved (with all its attributes and relationships). It is provided the capability to start and stop the sniffing phase from the user, so that it can restrict what will be recorded to the specific interesting part.


when closing the sniffing phase all the recorded SQLs will be made available to the user for checking them and removing the not needed ones that could be triggered from statistics and maintenance tasks for instance. The tool will highlights all the correlated values and/or the values that could be feed from different external data.

Basically th...

Processing...
Loading...