Data Bound Generator vs. Sequential Data Bound Generator

The Power Tools v1.0 release adds a new data generator, named the "Sequential Data Bound Generator". Since there already exists a data generator named the "Data Bound Generator" this yields the question what the difference is between the two is and when to use either one of them.

Data Bound Generator

The Data Bound Generator, takes the query you specified and uses it to fill a local dictionary. After query is execute, the results are used to fill a dictionary, the generator disconnects from the data source specified and randomly selects values from the dictionary and contributes the values to the column you bound the generator to.

This implies a couple of things:

  1. The complete result set from the query has to fit in memory and is held in memory for the duration of the generation. (If this is not the case the data generator will fail with an out of memory error.)
  2. The connection is only used to execute the query and fetch the results in to the dictionary, after that the connection is no longer used.
  3. You cannot assign a distribution to the Data Bound Generator; the only pattern used to select from the dictionary is random. (This will get addressed in a later release, so you can specify a distribution to select from the dictionary using a statistical distribution pattern.)

Sequential Data Bound Generator

The Sequential Data Bound Generator, takes the query you specified, executes the query and fetches one row at the time and returns the value to the column bound to the generator.

This implies that:

  1. Only a single row of the query is in memory at all times.
  2. The connections used to execute the query and fetch the results is in use for the duration of the generation plan execution
  3. The order in which values are returned are determined by the query statement, assuming you provides an ORDER BY clause in the query.

Both providers can connect to the same providers and are based on the same query execution code, only the way results are handled is different between the two.

I hope this explains the differences between the two providers and makes it easier to determine when to use which data generator.


Comments (3)

  1. jstangroome says:

    The sequential generator is better than the old because it now means I can fill a three column table with a set of predefined rows from another datasource. The old generator would grab each of the column values from different rows in the source and produce a "mutation" of the predefined set.

    The only problem now is that I need to copy and paste the SQL query to create the sequential generator for each and every column in the destination table. Is there some way to define a shared sequential generator once and tell each destination column to choose a different column from the one generator?


  2. There is no way to prevent that using the Sequential Data Bound Generator, you could builld your own that uses instance sharing to enable this, but we have not implemented that yet.

  3. MickeyHeadShot Mickey Gousset says:

    Brian Harry on Updated documentation on creating custom reports. GertD on Data Bound Generator Vs. Sequential…

Skip to main content