Information

Author: Appian Corporation
Type: Plug-in (Function & Smart Service)
Support: This plug-in or utility is not supported by the author. The content is free to use with a licensed product, but it is made available as-is and Community supported.
Industry: All Industries
Compatible Version(s): 23.2
First Released: 2 May 2020
Last Updated: 22 Mar 2024
Cost: Free

Video

Database Load Generation

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

Reads database metadata to automatically pull tables and columns
Provides multiple generators for generating data of different types (users, groups, folders, documents, location data, health data, personal data, etc..)
Connects to Appian database to generate and populate data in one step
Support the addition of new generators

If you have ideas for more generators, please leave a comment!

Parents

Appian AppMarket over 4 years ago
v1.0.8 Release Notes
- Added configurable number of values in each database insert statement using DG_NUMBER_VALUES - reduces size of DB audit log when inserting high volumes of records
- Cancel
- Up 0 Down
- Reply
- More
- Cancel
Vernon Pinawin over 4 years ago in reply to Appian AppMarket

My initial test failed. It only worked after I checked the json Master and put {} in the Delete Settings column. Is there an instruction on how to use these fields? Thanks.
- Cancel
- Up +1 Down
- Reply
- More
- Cancel
matthewarndt over 3 years ago in reply to Michael Chirlin

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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

matthewarndt over 3 years ago in reply to Michael Chirlin

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.
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

No Data