The DatabaseGenerator.exe is a tool to generate orders for the Contoso data model in order to provide demo data.
Overview and usage
The DatabaseGenerator.exe is a command-line application, running on .NET Core 3.1. It requires a working folder to run on, containing a configuration file and data input files. After executing, the working folder also contains generated output data files and logs.
databasegenerator.exe inputfolder outputfolder configfile [param:OrdersCount=nnnnnnn]
- config.json : main app configuration
- data.xlsx : static data (products, categories, …) and their configuration (distribution, weights, …)
- customer.rpt : customers list
Json Configuration file (config.json)
This file contains the main configuration of the data generator.
OrdersCount: (int) total number of orders to be generated.
StartDT: (datetime) date of the first order.
YearsCount: (int) total number of years generated. Orders are distributed over the years.
CutDateBefore, CutDateAfter: (datetime optional parameters) the 2 parameters allow to create data starting from a day different from January 1st and ending on a date different from December 31st. Data before CutDateBefore and after CutDateAfter is removed
CustomerFakeGenerator: (int) number of fake customers. If > 0, customers.rpt file is ignored and a number of fake customers are generated.
DaysWeightConstant: (bool) if set to true, the configuration about days is ignored.
DaysWeightPoints, DaysWeighValues: (double) points for interpolating the curve of distribution of orders over time. It covers the entire YearsCount period.
DaysWeightAddSpikes: (bool) if set to false, annual spikes are ignored.
WeekDaysFactor: (double – length 7) weight multiplication factor for each day of the week. The first day is Sunday.
DayRandomness: (double) percentage of randomness add to days, to avoid having a too-perfect curve over time.
OrderRowsWeights: (double) distribution of the number of rows per order. Each element is a weight. The first element is the weight of orders with one row, the second is the weight of orders with two rows. and so on
OrderQuantityWeights: (double) distribution of the quantity applied to each order row. Each element is a weight. The first element is the weight of rows with quantity=1, the second element is the weight of rows with quantity=2, and so on.
DiscountWeights: (double) distribution of the discounts applied to order rows. Each element is a weight. The first element is the weight of rows with a discount of 0%, the second element is the weight of rows with a discount of 1%, and so on.
OnlinePerCent: (double) distribution of the percentage of orders sold online, over the orders total.
DeliveryDateLambdaWeights: (double) distribution of the days for delivery. The delivery date is computed by adding one day plus a random number generated using the distribution built from this parameter.
CountryCurrency: table mapping Country to Currency
AnnualSpikes : set of periods where orders show a spike. For each spike, you define the start day, the end day, and the multiplication factor.
OneTimeSpikes: set of spikes with a fixed start and end date. For each spike, you define the start end, the end date, and the multiplication factor.
CustomerActivity : contains the configuration for customer start/end date
StartDateWeightPoints, StartDarteWeightValues: configuration for the spline of customer start date
EndDateWeightPoints, EndDateWeightValues: configuration for the spline of customer end dates
Customers list (customers.rpt)
A file containing customers’ information. Format: text, tab-delimited. Only the first two columns are used by the tool: CustomerID (int) and GeoAreaID (int). The following columns are ignored.
Excel configuration file (data.xlsx)
The Excel configuration file contains both fixed data and parameters to control the distribution of random data. For example, from here you can decide the relative percentage of orders for categories and subcategories.
The file contains several sheets, further described here. Each sheet contains multiple columns. The software reads some of the columns recognizing them by name. Columns with names that do not follow the standard requirements of the software are ignored. Columns have been conveniently colored in yellow if they are used by the software. Any non-yellow color is considered a comment and it is useful only for human purposes.
From here you can configure sales of categories using two curves: W and PPC. “W” define the relative weight of each category in the set of all categories for different periods in the entire timeframe. “PPC” define the variation in the price of items of each category during the whole period (Price percent). Normally the last column is 100%.
From here you can configure sales of subcategories using a weight curve with columns marked with W. The values are used to define the weight of a subcategory inside its category. Therefore, the numbers are summed by category and then used to weight subcategories inside the category.
On this page, you can configure the likelihood that one product in a subcategory triggers the purchase of another product in another subcategory. The values are in percentage: <17, 18, 80%> means that if a product of subcategory 17 is added to an order, there is an 80% chance that a product of subcategory 18 will be added to the same order.
On this page, you configure, for each product, the initial price and the distribution of sales of the product over different periods. The weights identified in the W columns are relative to the subcategory to which the product belongs.
On this page, you define clusters of customers. Each cluster is defined by two columns: OW (OrderWeight) and CW (CustomerWeight). Order Weight defines the percentage of orders assigned to customers belonging to the cluster, whereas CustomerWeight defines the percentage of the total customers used to fill the cluster.
It is possible to define a large cluster of customers that generates a small number of orders. The number of clusters is free.
This page is intended to define geographical areas, each with a set of weights to change the activity of the area over time. Each area is independent of the other and the definition of geographical areas needs to be done at the leaf level: no grouping is provided. For each geographic area, you define the W columns to provide the activity spline.
On this page, you enumerate the stores. For each store, you provide its geographical area and the open and close date. A store is active only between the two dates. You do not provide weight activity for the stores, as the behavior is dictated by the customer clusters. A special store marked -1 as StoreID defines the online store. Each order is assigned to either the online store or to a local store depending on the country of the customer.
- customersClusters.csv : ClusterID, CustomerID
- orders.csv : OrderID, CustomerID, StoreID, DT
- orderRows.csv: OrderID. RowNumber, ProductID, Quantity, Price1, Price2