Data Migration Pipeline
Design a safe, reversible data migration pipeline for this schema change or data movement. Migration: {{migration_description}} (e.g. split a table, merge schemas, move to new d...
4 Database Engineer prompts in Migration and Upgrades. Copy ready-to-use templates and run them in your AI workflow. Covers intermediate → advanced levels and 3 single prompts · 1 chain.
Design a safe, reversible data migration pipeline for this schema change or data movement. Migration: {{migration_description}} (e.g. split a table, merge schemas, move to new d...
Plan a major PostgreSQL version upgrade for this production system. Current version: {{current_version}} Target version: {{target_version}} Database size: {{size}} RPO: {{rpo}}...
Step 1: Schema design - design the normalized relational schema for the domain. Define primary keys, foreign keys, and data types. Create an ERD. Identify tables requiring parti...
Design a zero-downtime schema migration strategy for this production database. Change type: {{change}} (add column, rename column, change type, add index, split table) Table siz...
Start with a focused prompt in Migration and Upgrades so you establish the first reliable signal before doing broader work.
Jump to this promptReview the output and identify what needs follow-up, cleanup, explanation, or deeper analysis.
Jump to this promptContinue with the next prompt in the category to turn the result into a more complete workflow.
Jump to this promptWhen the category has done its job, move into the next adjacent category or role-specific workflow.
Jump to this promptMigration and Upgrades is a practical workflow area inside the Database Engineer prompt library. It groups prompts that solve closely related tasks instead of leaving users to search through one flat list.
Start with the most general prompt in the list, then move toward the more specific or advanced prompts once you have initial output.
A single prompt gives you one instruction and one output. A chain is a multi-step sequence designed to build on earlier results and produce a more complete workflow.
Yes. They work in other AI tools too. MLJAR Studio is still the best fit when you want local execution, visible code, and notebook-based reproducibility.
Good next stops are Schema Design, Performance Tuning, Query Optimization depending on what the current output reveals.