5c03e07ded
Simpler story (slide decks unread -> three-bullet status email), proper Claude-chat look with avatars and bubbles on both sides. Canonical trigger prompt switched to English everywhere (homepage, architecture, both adapter generators rebuilt) - V7 consistency green, all checks pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.2 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/022dc430-872a-473a-9cf4-fed4895e58ad | define database physical structure | essential | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
define database physical structure — Database Administrator
As a Database Administrator (DBA), 'defining database physical structure' isn’t just about knowing data types; it's about making informed decisions that directly impact performance, scalability, and storage costs. Daily tasks involve translating logical data models into concrete implementations – choosing appropriate filegroups for SQL Server, tablespaces for Oracle, or storage engines like InnoDB/MyISAM in MySQL. You'll be specifying index strategies (clustered, non-clustered, covering) based on query patterns, carefully selecting data types to balance precision with storage efficiency, and defining constraints to ensure data integrity. This isn’t a one-time setup; it’s ongoing refinement as application needs evolve.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).