Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Database Administrator (DBA) source-backed Guide
Defines source-backed database administration and reliability, evidence handling, and action boundaries.
Read the fileOverview
Database Administrator (DBA) overview
Use this bundle to prepare source-backed database administration and reliability analysis and a review-ready database change brief.
Read the fileWorkflow
Database Administrator (DBA) source-backed triage
1. State the requested decision or artifact. 2. Inventory evidence: database purpose, owners, environments, engine, version, topology, and dependencies; schemas, data classification, volume.
Read the fileTemplate
database change brief
Review-ready artifact for database administration and reliability, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Database Administrator (DBA) work, plus teams reviewing its decisions and outputs
- Teams working in Data and analytics, Technology operations
When to use it
- A Database Administrator (DBA) task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare a database change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- database change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Database Administrator (DBA) work by producing database change brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1242.00, then confirm that the reference is current and applicable. Inspect Database Administrator (DBA) source-backed Guide before drafting.
Context path: bundles/roles/database-administrator-dba
What the bundle includes
Frameworks
- source-evidence matrix
- database administration and reliability review matrix
- qualified-review gate
Evaluations
- Database Administrator (DBA) source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the cited official, originator, standards, or professional sources for general database administration and reliability context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for database purpose, owners, environments, engine, version, topology, and dependencies; schemas, data classification, volume, workload, queries, indexes, and statistics; identities, roles, privileges, encryption, keys, audit, and network controls; backups, retention, restore tests, replication, recovery objectives, and incidents; change plan, migration, capacity, monitoring, maintenance, rollback, and approvals.
- Do not infer schema meaning, privilege, backup validity, recoverability, performance cause, replication state, capacity, or production health.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
- Require explicit confirmation before querying or exporting sensitive data, changing schemas or privileges, restoring backups, failing over, or modifying production.
- Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.