inside-transaction-log
Skill1 starsChanged 12 days agoMITView on GitHub
Explore SQL Server transaction log files, VLFs, log records, log IO, minimal logging, recovery, truncation, and log management. Use when working with examples/insidetlog or selecting its five transaction-log labs and VLF tests.
In this repository20 other files it gives its agents.
- nvidianimSkill
- zavahospitalSkill
- shift-handoffSkill
- adventureworksSkill
- auto-index-compactionSkill
- azure-sql-aiSkill
- debugging-sqlSkill
- polybaseSkill
- powerapps-sqlSkill
- secure-scalable-db-appSkill
- sql-by-exampleSkill
- sql-linuxSkill
- sqlserver2022Skill
- sqlserver2025Skill
- sql-versioning-appsSkill
- sql-versioningSkill
- tempdb-growthSkill
- waits-latches-spinlocksSkill
- waits-latches-spinlocks-workshopSkill
- wardgeneralSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the collection map. Choose physical layout, records, IO, recovery, management, or VLF growth.
- Distinctive: line 12
Read the selected walkthrough and scripts before deciding execution order.
- Distinctive: line 21
Treat internal DBCC/log-format details as version-sensitive educational evidence.
- Distinctive: line 27
Use secret checks before publishing scripts, backups, or log captures.
≈ “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
Inside the transaction log
Procedure
- Read the collection map. Choose physical layout, records, IO, recovery, management, or VLF growth.
- Read the selected walkthrough and scripts before deciding execution order. Confirm SQL build, SQL tools, permissions, filesystem/backup paths, and any extra inspection utilities.
- Require an isolated lab and explicit approval for shutdown, restore, file manipulation, log rebuilding, large growth, or destructive cleanup. Preserve restorable lab backups before recovery experiments.
- Establish the documented starting database state. Run the selected blocks and separate sessions in order, recording actual VLF, log-space, record, IO, transaction, or recovery observations at the requested checkpoints.
- Treat internal DBCC/log-format details as version-sensitive educational evidence. Do not turn a lab's file/log-rebuild technique into production recovery advice or infer results from historical screenshots.
- Close transactions, stop drivers, restore the intended lab state, and report remaining files/databases rather than deleting them automatically.
Use secret checks before publishing scripts, backups, or log captures; binary artifacts need independent review.
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.

