6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
2.6 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/d9eaf831-9348-4330-a83e-b7c099cdc8f6 | Teradata Database | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
Teradata Database — Database Administrator
As a Teradata DBA, 'Teradata Database' competence isn’t just knowing it exists; it's being able to keep the entire system humming. Daily tasks revolve around performance monitoring using tools like Query Banding and Explain plans to identify slow-running queries or resource bottlenecks. You'll spend significant time managing space – tablespaces, AMPs (Access Module Processors), and data distribution skew – ensuring optimal storage utilization and preventing outages. Expect frequent work with Teradata Studio for query execution/analysis, BTEQ scripting for automation, and potentially tools like Viewpoint for monitoring dashboards.
A core part of the role is proactive maintenance: applying PTFs (Program Temporary Fixes) to address bugs or security vulnerabilities, managing user permissions via roles and grants, and performing regular backups/restores using Teradata’s utilities. Troubleshooting often involves digging into error logs, analyzing system statistics (using tools like DBAONTAP), and understanding how Teradata's parallel processing architecture impacts query execution. Pitfalls include improper data distribution leading to performance issues, failing to monitor space effectively causing table overflows, or incorrectly applying PTFs which can destabilize the environment.
Good looks like consistently high system availability, predictable performance even under peak loads, and a well-documented environment. It means being able to quickly diagnose and resolve issues before they impact users, automating routine tasks with scripting, and proactively identifying potential problems through monitoring and capacity planning. A strong Teradata DBA understands the nuances of Teradata’s architecture – how data is partitioned, how queries are optimized, and how different features interact.
Finally, this competence extends to understanding Teradata-specific extensions to SQL (like volatile tables or join indexes) and being able to advise developers on writing efficient Teradata SQL. It's not enough to just make things work; you need to make them work well within the Teradata ecosystem.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).