Skip to content

Latest commit

 

History

History
39 lines (34 loc) · 2.67 KB

readme.md

File metadata and controls

39 lines (34 loc) · 2.67 KB

Example collections

Choose a collection below before installing dependencies or running scripts. There is no shared application or universal setup command.

Collection Start here for
adventureworks AdventureWorksLT sample database import
auto_index_compaction Azure SQL Hyperscale index compaction and measurement
azuresqlai Azure SQL embeddings, approximate vector search, and RAG
debugging_sql SQL Server process and query debugging with WinDbg
insidetlog Transaction log internals and recovery labs
insidewaitslatchesspinlocks Wait, latch, spinlock, and log-rate investigations
insidewaitslatchesspinlocks_workshop Numbered debugging and synchronization workshop
polybase SQL Server 2019 PolyBase fundamentals and external-source examples
powerappssql A Power Apps orders interface over Azure SQL
securescaleabledbapp Azure SQL application security, performance, and availability
sqlbyexample SQL Server 2019 capability walkthroughs
sqllinux SQL Server on Linux deployment, tuning, AG, and Docker demos
sqlserver2022 SQL Server 2022 features and deployment scenarios
sqlserver2025 SQL Server 2025 engine, developer, and AI capabilities
sqlversioning SQLBits 2026 row-versioning and ADR demonstrations
wardgeneral The cumulative Ward General Hyperscale application

Running safely

  • Read the collection and subfolder README first. Match the SQL version and prerequisites rather than assuming every script runs on the same instance.
  • Use isolated lab resources. Debugging and recovery demos can stop SQL Server; performance and contention demos can exhaust CPU, storage, or connections.
  • Review placeholders, paths, credentials, resource names, and cleanup. Supply secrets privately and obtain approval before billable or destructive work.
  • Captured results are illustrative evidence from previous runs, not performance guarantees. Source folders have Markdown READMEs; generated build output is not part of this documentation coverage.

Each collection has a matching workspace skill listed in the repository overview. Before publishing changes, follow Secret scanning.