Sample And Data Sources
No dataset on this page is bundled with Azure Data Lab Toolkit. These are possible future catalog entries, and each remains owned and licensed by its upstream publisher and, where applicable, the creators of the underlying data.
Microsoft samples
Section titled “Microsoft samples”| Candidate | Steward and attribution | License or review note |
|---|---|---|
| Microsoft SQL Server samples | Microsoft and repository contributors | Repository code and samples use the repository’s MIT license; individual folders may add terms that must also be reviewed |
| AdventureWorks | Microsoft | Review the repository license and the selected package before download or redistribution |
| WideWorldImporters | The authoritative README credits Greg Low, Denzil Ribeiro, Jos de Bruijn, and Robert Cain as authors | Review the repository MIT license and package-specific notices |
| Northwind and pubs | Microsoft | Legacy samples; review repository and folder terms before use |
| Microsoft Fabric samples | Microsoft and repository contributors | Review the repository license and the selected sample’s own README and dependencies |
Community SQL Server and analytics sources
Section titled “Community SQL Server and analytics sources”| Candidate | Steward and attribution | License or review note |
|---|---|---|
| SQL Sunday downloads | Daniel Hutmacher prepares the database packages and identifies underlying public-data sources | Review every database separately. The source data, prepared database, and download method can have different terms; the downloads index alone is not a blanket license |
| Stack Overflow database for SQL Server | Brent Ozar provides the SQL Server distribution; the posts remain the work of Stack Overflow contributors | The underlying content is governed by the Stack Overflow content license. Distribution terms and attribution must be preserved |
| Contoso Data Generator | SQLBI, founded by Alberto Ferrari and Marco Russo | Redistribution rights and the provenance and terms of generated archives require verification before a catalog entry can automate acquisition |
PostgreSQL sources
Section titled “PostgreSQL sources”The PostgreSQL community sample database index is a useful directory, not a guarantee that each linked database has the same owner or license.
| Candidate | Steward and origin | License or review note |
|---|---|---|
| Pagila | Maintained by Devrim Gündüz and contributors; it began as a PostgreSQL port of the Sakila example created by Mike Hillyer and the MySQL documentation team | PostgreSQL License |
| Chinook | Created by Luis Rocha and maintained with contributors | MIT |
| Northwind for PostgreSQL | A PostgreSQL adaptation by Pascal Thomet and contributors of Microsoft’s Northwind sample | Review the project’s license and preserve both adaptation and original-sample attribution |
User-provided data
Section titled “User-provided data”Planned sources include local files and directories, approved HTTPS URLs, Azure Blob Storage, ADLS Gen2, Azure Files, existing databases or backups, and generated data. Public catalog entries remain optional: a company or developer may choose private data or software instead.
Private data needs the same provenance record as public data, plus stricter access handling:
- credentials must be supplied through Key Vault or another approved secret reference, never inside YAML or a URL;
- an explicit acknowledgement is required when provenance cannot be independently verified;
- a user-provided checksum is optional, but an absent checksum must be warned about and recorded;
- sensitive data requires explicit classification, policy validation, least-privilege access, and redacted reports;
- acquisition, restore or import, validation, retention, and removal must be part of the plan.
The catalog must preserve the resolved source, immutable version when available, checksum or signature evidence, upstream terms, and restore metadata. The plan must show what will be loaded and what code or database commands will run before anything changes.