Scope
Name the databases, tables, views, routines, structure, and rows included—and explicitly excluded.
Data movement needs a runbook
Make HeidiSQL imports and exports deliberate, verifiable, and recoverable.
Northstar designs operator procedures around source format, target selection, encoding, permissions, output destination, evidence, and restore testing.
HeidiSQL has flexible paths
Flexibility increases the need for context.
Official documentation describes SQL exports to a file, ZIP-compressed file, clipboard, another database, or a configured remote session. It also documents SQL, CSV, and BLOB-oriented imports.
A runbook should therefore answer more than which button to click: what is the source of truth, which target is active, what may be dropped or created, how is encoding selected, and how will completion be verified?
Export control points
Know the destination before generating output.
Action
Review DROP, CREATE, and data output options for their effect on the target, not just the source.
Format
Choose SQL, compressed SQL, CSV, HTML, XML, or another supported result based on the receiving workflow.
Destination
Control file path, clipboard use, same-server database, or configured remote session and its access role.
Import control points
The target and encoding are first-class decisions.
Inspect
Confirm provenance, format, size, delimiter, encoding, schema expectations, and whether the file contains destructive statements.
Stage
Select a non-production or isolated target, verify backups, and test permissions and constraints.
Execute
Set the intended database and explicit encoding; monitor progress and capture errors without repeatedly retrying blindly.
Verify
Compare counts, samples, constraints, application behavior, and logs; preserve evidence and dispose of temporary files securely.
Risk patterns
Failures a short checklist can prevent.
Wrong active database
The operator opens the correct file but executes it against a different selected database or connection.
Encoding by guess
Auto-detection or an assumed default changes characters; an explicit source encoding was available but not recorded.
Oversized statements
Extended inserts exceed server limits such as packet-size constraints and fail partway through a transfer.
Unreviewed DDL options
DROP or CREATE behavior is enabled for a target where the objective was data-only movement.
Uncontrolled clipboard output
Exported records enter a workstation clipboard without an approved need, retention rule, or disposal step.
No restore rehearsal
A file exists, but no one has shown that it can be read, applied, and verified under realistic conditions.
A usable runbook
Put confirmations at the point of consequence.
- Source and target shown together
- Operator and approver roles named
- Backup checkpoint before destructive options
- Encoding and delimiter written explicitly
- Expected counts and sample checks defined
- Temporary file retention and secure disposal covered
- Abort and escalation conditions visible
Data workflow FAQ
Before moving rows.
Is an export automatically a backup?
No. Treat backup suitability as a separate requirement involving completeness, consistency, retention, access, restore testing, and recovery objectives.
Should we use auto-detect encoding?
If the source encoding is known, record and select it explicitly. The official help notes that automatic detection can produce broken data.
Can we export directly to another server?
HeidiSQL documents output to another configured session. Use that only with explicit source-target confirmation, role controls, network approval, backup, and verification.
What belongs in an evidence record?
Capture operator, time, source, target, approved scope, file identity, selected options, completion status, exceptions, counts, and verification result without exposing secrets.
Make the next data move repeatable
Turn a successful one-off into a controlled workflow.
Northstar can map, test, and document one critical import or export path with your operators.
Scope a data workflow sprint