sql-versioning
Skill1 starsChanged 12 days agoMITView on GitHub
Run the SQLBits 2026 SQL Server versioning demos: blocking, RCSI versus Snapshot, update conflicts, version chains, ADR/PVS cleanup, optimized locking, and benchmark comparisons. Use when working with examples/sqlversioning. For the local browser click-through apps, also load sql-versioning-apps.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- adventureworksSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- inside-transaction-logSkill
- polybaseSkill
- powerapps-sqlSkill
- secure-scalable-db-appSkill
- sql-by-exampleSkill
- sql-linuxSkill
- sqlserver2022Skill
- sqlserver2025Skill
- sql-versioning-appsSkill
- tempdb-growthSkill
- waits-latches-spinlocksSkill
- waits-latches-spinlocks-workshopSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read the demo inventory. Work from examples/sqlversioning.
- Very specific: line 18
Verify SQL Server 2025 and permissions.
- Very specific: line 20
Run tools/check-readiness.ps1 with reviewed targets before the session.
- Distinctive: line 27
Verify the intended evidence: blocking versus consistent reads, conflict errors, version-chain structure, PVS cleanup, or lock counts.
- Distinctive: line 37
Follow secret checks; do not publish private connection details in viewer configuration or result files.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SQL Server versioning explained
For browser-based demos 0-4, load the sql-versioning-apps skill. In this repository, "run the app" means verify/start the backend and open a new normal external browser window, not the VS Code integrated browser.
Procedure
- Read the demo inventory.
Work from
examples/sqlversioning; the descriptive demo folders retain their numeric prefixes. Use the inventory's current paths. - Verify SQL Server 2025 and permissions. Inspect
demo0-setup/demo0-setup.sqlfor database names/data creation and get approval before executing. Runtools/check-readiness.ps1with reviewed targets before the session. - Choose the desired concept and open
session1/session2scripts in separate SSMS windows. Follow their handoff cues; do not batch-run both sides or leave snapshot transactions open between demonstrations. - For DBCC PAGE viewers, inspect the viewer source/configuration, confirm Python dependencies, and start only the required local viewer. Preserve autocommit behavior so diagnostic connections do not pin version cleanup.
- Verify the intended evidence: blocking versus consistent reads, conflict errors, version-chain structure, PVS cleanup, or lock counts. Internal page formats and cleanup timing are not stable production contracts.
- For throughput tests, read the
benchmark guide,
verify
sqlsim, approve database creation/load, and preserve comparable configurations. Do not quote captured numbers as new measurements. - Close all transactions, stop viewers/drivers by their specific process IDs, and confirm lab state before any requested cleanup.
Follow secret checks; do not publish private connection details in viewer configuration or result files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

