Request
Field Repair needs January removed from its live event parent while retaining the January table for an audit. Build date partitions, load boundary records from existing orders, detach the old period and reconcile both the live and retained populations. Detach and drop have different data-retention effects.
Data
Use the fictional customers, orders, items, event documents and account records supplied in the workspace. No production data is connected.
Final output
Complete all six checked stages and leave the final SQL and result available for review. Each stage names its required object or output.
Field Repair needs January removed from its live event parent while retaining the January table for an audit. Build date partitions, load boundary records from existing orders, detach the old period and reconcile both the live and retained populations. Detach and drop have different data-retention effects.
Build the requested result in six checked stages. Each stage keeps the earlier SQL in the editor so you can extend the same work. The next stage begins with your own submitted script; Start over restores the reference starting point for that stage. Read the output contract before adding a column or changing a filter.
Keep source rows intact unless the task explicitly asks for a write. Missing values and period boundaries are included deliberately. The checker reruns the work against changed source records, so a fixed visible total isn't a valid substitute for the query or database object.
Partition on the retention date rather than the event identifier.