WideWorldImporters data generation
The released versions of the WideWorldImporters and WideWorldImportersDW databases have data from January 1, 2013, up to the day that the databases were generated.
When you use these sample databases, you might want to include more recent sample data.
Data generation in WideWorldImporters
To generate sample data up to the current date:
If you haven't done so, install a clean version of the WideWorldImporters database. For installation instructions, see Installation and configuration.
Execute the following statement in the database:
EXECUTE DataLoadSimulation.PopulateDataToCurrentDate @AverageNumberOfCustomerOrdersPerDay = 60, @SaturdayPercentageOfNormalWorkDay = 50, @SundayPercentageOfNormalWorkDay = 0, @IsSilentMode = 1, @AreDatesPrinted = 1;
This statement adds sample sales and purchase data to the database, up to the current date. It displays the progress of the data generation by day. Data generation can take about 10 minutes for every year that needs data. Because of a random factor in the data generation, there are some differences in the data that's generated between runs.
To increase or decrease the amount of data generated for orders per day, change the value for the parameter
@AverageNumberOfCustomerOrdersPerDay. Use the parameters
@SundayPercentageOfNormalWorkDayto determine the order volume for weekend days.
Import generated data in WideWorldImportersDW
To import sample data up to the current date in the WideWorldImportersDW OLAP database:
Execute the data generation logic in the WideWorldImporters OLTP database by using the steps in the preceding section.
If you haven't yet done so, install a clean version of the WideWorldImportersDW database. For installation instructions, see Installation and configuration.
Reseed the OLAP database by executing the following statement in the database:
Run the Daily ETL.ispac SQL Server Integration Services package to import the data into the OLAP database. To learn how to run the ETL job, see WideWorldImporters ETL workflow.
Generate data in WideWorldImportersDW for performance testing
WideWorldImportersDW can arbitrarily increase data size for performance testing. For example, it can increase data size to use with clustered columnstore indexing.
One of the challenges is to keep the size of the download small enough to download easily, but large enough to demonstrate SQL Server performance features. For example, significant benefits for columnstore indexes are achieved only when you work with larger numbers of rows.
You can use the
Application.Configuration_PopulateLargeSaleTable procedure to increase the number of rows in the
Fact.Sale table. The rows are inserted in the 2012 calendar year to avoid colliding with existing World Wide Importers data that begins January 1, 2013.
@EstimatedRowsFor2012 bigint (with a default of 12000000)
Approximately the required number of rows are inserted into the
Fact.Sale table in the 2012 year. The procedure artificially limits the number of rows to 50,000 per day. You can change this limitation, but the limitation helps you avoid accidental overinflations of the table.
The procedure also applies clustered columnstore indexing if it hasn't already been applied.