polybase
Skill1 starsChanged 12 days agoMITView on GitHub
Guide the dedicated SQL Server 2019 PolyBase fundamentals and WideWorldImporters data-hub demos. Use when working with examples/polybase, head/compute-node diagnostics, external-table execution, or its SQL Server, Azure SQL, HDFS, Oracle, Cosmos DB, and SAP HANA connectors.
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
- 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
5 rules. About 0 are common, 4 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the collection README, then the fundamentals or chosen data-hub connector walkthrough.
- Distinctive: line 12
Verify the actual SQL Server version/build, PolyBase installation/services, supported connector/driver, remote source, and …
- Distinctive: line 21
Keep the target source and SQL lab isolated.
- Distinctive: line 22
Run the selected setup and external-table queries, then verify the remote data and local joins.
- Very specific: line 29
Follow secret checks before publication.
≈ “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
PolyBase fundamentals and data hub
Procedure
- Read the collection README, then the fundamentals or chosen data-hub connector walkthrough.
- Verify the actual SQL Server version/build, PolyBase installation/services, supported connector/driver, remote source, and WideWorldImporters lab data. These examples reference SQL Server 2019 previews and scale-out/Hadoop features; do not assume they work unchanged on later releases.
- Inspect scripts for node names, endpoints, filesystem paths, credentials, and required permissions. Supply secrets privately and review notebook outputs; do not reuse or allowlist inherited literal credentials.
- Obtain approval before restarts, firewall changes, scale-out setup, external-source configuration, database writes, or billable resources. Keep the target source and SQL lab isolated.
- Run the selected setup and external-table queries, then verify the remote data and local joins. For fundamentals, use the supplied status and execution diagnostics to observe actual node/query behavior.
- Report unsupported prerequisites or connection errors explicitly. Follow the connector's cleanup for lab-owned credentials, data sources, formats, and external tables without deleting remote source data automatically.
Follow secret checks before publication. This
dedicated collection is distinct from the similar sqlbyexample/sqldatahub demos.
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.

