From 67c3374c9ff1a1e095e87a42e7dfc1385b71ff78 Mon Sep 17 00:00:00 2001 From: Jos de Bruijn Date: Mon, 26 Jun 2017 10:01:04 -0700 Subject: [PATCH] clarified how 2012 data is generates --- samples/databases/wide-world-importers/wwi-ssdt/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/databases/wide-world-importers/wwi-ssdt/README.md b/samples/databases/wide-world-importers/wwi-ssdt/README.md index 44a34aef..92d25740 100644 --- a/samples/databases/wide-world-importers/wwi-ssdt/README.md +++ b/samples/databases/wide-world-importers/wwi-ssdt/README.md @@ -77,7 +77,7 @@ Note that each time the database is created from scratch, the data in many table To customize the period for data generation, leverage the stored procedure `DataLoadSimulation.DailyProcessToCreateHistory`.

The referenced stored procedure removes the temporal nature of the tables, and implements a series of triggers. It then emulates typical activities that would occur during each day. Finally, it removes the triggers and re-establishes the temporal tables. You can see the progress of the simulation in the Messages tab in SSMS as the query executes. (AreDatesPrinted controls whether dates are printed to the messages window as data is generated. IsSilentMode controls whether detailed output is printed. IsSilentMode = 1 produces just date output if AreDatesPrinted = 1.). Note that a different outcome is produced each time it is run as it uses many random values. -StartDate and EndDate cover the period for generation. Other code populates the 2012 period when expanding the columnstore tables so do not populate back into 2012 or earlier with this procedure. The EndDate must also be at or before the current date as temporal tables do not allow future dates. +StartDate and EndDate cover the period for generation. The OLAP database `WideWorldImportersDW` contains the stored procedure `Application.Configuration_PopulateLargeSaleTable` to populate the 2012 period with a large amount of data for columnstore tables testing, so do not populate back into 2012 or earlier using the `DailyProcessToCreateHistory` procedure. The EndDate must also be at or before the current date as temporal tables do not allow future dates. You can configure the amount of data produced by modifying the number of orders per day. The default is 60 orders and produces a reasonable OLTP database size of around 93MB compressed. You are also able to configure how busy Saturday and Sunday are compared to normal Monday to Friday working days, as a percentage. The suggested values are 50% for Saturday and 0% for Sunday. ### Publishing to Azure SQL Database