Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Data generation fails due to invalid records in ColdRoomTemperatures

Open
#1,275 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
sql
Domain
databases

Research direction

Start with the DataLoadSimulation.PopulateDataToCurrentDate procedure and the Warehouse.ColdRoomTemperatures_Archive history table described in the report. Reproduce the scheduled call, inspect how invalid period records are generated, and verify that the call completes without requiring manual deletion of rows or resetting temporal tables.

Written by the indexing model from the issue text.

Description

I have schedule the data generator to run daily so I can have good demo data for our developers. It occasionally fails with the following error message which requires me to manually delete the invalid rows and reset all the temporal tables.

[SQLSTATE 01000] (Message 0) Setting SYSTEM_VERSIONING to ON failed because history table 'WideWorldImporters.Warehouse.ColdRoomTemperatures_Archive' contains invalid records with end of period set before start.

Here is the stored procedure call that I am using:

EXECUTE DataLoadSimulation.PopulateDataToCurrentDate @AverageNumberOfCustomerOrdersPerDay = 60,
                                                     @SaturdayPercentageOfNormalWorkDay = 50,
                                                     @SundayPercentageOfNormalWorkDay = 0,
                                                     @IsSilentMode = 1,
                                                     @AreDatesPrinted = 1;

I'll dig into the generation code and see if I can fix it since no one appears to be maintaining this project.

Dominant language
PowerShell
Stars
11.2k
Forks
9.1k
Avg merge
2d 7h
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/sql-server-samples

All issues in microsoft/sql-server-samples

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.