X-ERP Help

SQL or CSV?

Choose the transport method based on data volume, relationships, repeatability, control and team competence - not personal habit.

The file format is vehicle only. What matters is whether you can always explain which data set came from where, which rule changed it and how an error is reprocessed.

The truth is in the mapping

CSV is transparent, portable and good for clearly defined master data. SQL is suitable for large, relational or repetitive transformations, but requires database expertise, staging and strict boundaries with X-ERP business logic.

From raw stock to controlled import

Assess volume, table relationships, rate of change, error handling, and need for retry.
Use CSV for manageable, flat, easily auditable handoffs.
Leverage SQL staging for large or highly relational assets and repeatable transformation.
In both cases, define key, character set, null values, date/number format and protocol.
Run the same test set reproducibly at least twice.

Evidence instead of gut feeling

The process preserves keys and references.
Error lines can be explained individually and reprocessed.
Character set and locale do not change any values.
A second run does not produce unwanted duplicates.

The typical breaking points

CSV opens in Excel and reformats unnoticed.
SQL scripts write directly to internal tables and bypass business rules.
The choice only takes speed into account, not decrease and repetition.

This is what you take with you

You choose a transport method that facilitates the technical evidence rather than obscuring it.

In this chapter

Further information / source

Frequently asked questions

**Is SQL always faster?**

Often with large amounts of data, but total time includes mapping, error explanation, checking and repeating. A transparent CSV can be more efficient in a small scope.

**Can I fill X-ERP tables directly?**

Only via explicitly approved import procedures. Direct writes can bypass business logic and references.