github/sql-server-samples
1
0
Fork 0
mirror of https://github.com/Microsoft/sql-server-samples.git synced 2025-12-08 14:58:54 +00:00
Code Issues Releases Wiki Activity

clarified how 2012 data is generates

Browse Source
This commit is contained in:
Jos de Bruijn
2017-06-26 10:01:04 -07:00
committed by GitHub
parent 1e3de8607c
commit 67c3374c9f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
samples/databases/wide-world-importers/wwi-ssdt/README.md
+1 -1
View File
@@ -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`.
<br/><br/>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