Overview
This tool can be used to quickly generate multiple rows for each of the application transactional tables to easily support database load testing.
Key Features & Functionality
If you have ideas for more generators, please leave a comment!
Good afternoon!
I have the following data structure, and I am currently having issues getting the data generator to work as I intended..
CREATE TABLE dbo.Entity (pk_EntityId INT PRIMARY KEY IDENTITY(1,1) , EntityTypeId INT --1 Store, 2 Product ) CREATE TABLE dbo.Store (pk_StoreId INT PRIMARY KEY IDENTITY(1,1) , fk_EntityId INT , StoreName NVARCHAR(50) ) CREATE TABLE dbo.Product (pk_ProductId INT PRIMARY KEY IDENTITY(1,1) , fk_EntityId INT , fk_StoreId INT , ProductName NVARCHAR(50) )
What I need to do is create random number of stores, which also have random number of products. The thing is, we have an Entity table that we must first create an entity for each store/product, before we can actually create the store/product. I can I make the data generator work so that it can use current identity +n whenever it is creating a new Entity for Store/Product?
Hi Michael, I am on the latest version (1.2.1) and the issue above is still happening for me. Changing the deleteSettings value in the DG_TABLE table with the text "null" rather than null value is solving the issue for me.
Hi, would it be possible to add functionality to allow an appian constant as the start index for BUSINESS - ID Sequential rather than a manually entered integer every time?
Thanks
I will get it added soon to the downloadable.
Hi,
I've downloaded the zip file but I cannot find the jar file of the plugin. My installation is on prem.
Can you please help?
v1.2.0 Release Notes
Is it important that all of the results are unique? Could you, for example, just input a string generated for that purpose or a list of strings.
There isn't currently a rule generator, although it might be possible to update the plugin to allow it. Remember though, for load generation, it's not always necessary to create accurate data for testing the performance. So you might be able to get away with having a single encrypted value that is the same across all rows.