sqlserver2022
Skill1 starsChanged 12 days agoMITView on GitHub
Select and run SQL Server 2022 feature demos: IQP, Azure Arc, Entra authentication, contained AGs, MI link, Fabric/Synapse integration, ledger, S3, Parquet/Delta, containers, Kubernetes, tempdb, and T-SQL. Use for examples/sqlserver2022.
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
- 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 catalog and select one area.
- Distinctive: line 13
Verify SQL Server 2022 edition/build, compatibility level, sample database, permissions, and client tools.
- Distinctive: line 22
Run the selected walkthrough in its numeric/session order.
- Distinctive: line 26
Follow the area's teardown and verify its scope before deleting cloud resources, databases, containers, volumes, or persistent storage.
≈ “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 2022 demonstration collection
Procedure
- Read the collection catalog and select one area. Use its local README and actual files, not a guessed script order or an obsolete folder name.
- Verify SQL Server 2022 edition/build, compatibility level, sample database, permissions, and client tools. For integrations, independently verify current Azure/service support, accounts, storage, and network prerequisites.
- Inspect scripts/manifests for endpoints, paths, and private configuration. Supply runtime credentials following secret setup, including SQLCMD mode where script headers require it. Never suppress findings.
- Present the target and operational impact. Require approval before creating Azure resources, exposing services, changing identity/HA configuration, restoring data, applying Kubernetes manifests, or generating heavy load.
- Run the selected walkthrough in its numeric/session order. Validate actual plans, feedback, data access, container/pod state, or integration evidence relevant to that demo. Treat captured examples as illustrative, not expected measurements.
- Follow the area's teardown and verify its scope before deleting cloud resources, databases, containers, volumes, or persistent storage.
Boundaries
This collection has no universal build. Kubernetes restart labs do not establish an availability-group guarantee. Parquet/Delta files are supporting data, not code; preserve metadata and inspect publication suitability separately. Follow secret checks.
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.

