Convert xBase to SQL Server

Working from an xBase table

xBase is the family name for the record layout dBase defined and Clipper, FoxBase and FoxPro adopted. A file from any of them opens here; the differences live in the header bytes, and those are read rather than assumed.

• →Records deleted but never packed are still physically present, flagged with an asterisk. They are skipped, so the converted table holds the rows the application showed and not the ones it hid.
• →Clipper is the trap in this family: it wrote version byte 0x03 even for tables with memo columns, so a naive reader picks the wrong memo layout and dies with "unpack requires a buffer of 8 bytes". That case is handled here.
• →The header gives each field an 11-byte name slot, so xBase column names are at most 10 characters - a limit that follows the data into the target unless you rename the columns there.

How names and bytes are written

mssql is the short name the drivers use - the ODBC DSN, SQLAlchemy's mssql+pyodbc, the container image. What it produces is ordinary T-SQL text, and the details worth checking before you run it are how it writes names and how it writes raw bytes.

• →Identifiers are wrapped in square brackets rather than double quotes, and a bracket inside a source name is turned into an underscore before the wrapping goes on: a column named Order]Date is created as [Order_Date], so a bracket in your data can never close a name early.
• →The identifier cap is 128 characters, high enough that almost every source name survives untouched - one that Oracle would have to cut at 30 arrives here whole.
• →Binary columns are VARBINARY(MAX) and their values are written as bare 0x hex literals, with no quotes around them and no conversion function wrapped over them.

Reading xBase

• →Numeric fields with decimals are read as exact decimals, not floats, so currency does not drift.
• →Character field widths are read from the header and carried into the target.
• →The code page declared in the file header is used, so Cyrillic, Western European and other legacy DOS encodings decode correctly instead of turning into mojibake. 157 code pages are recognised.
• →Files written by dBase III or Clipper declare no code page at all — the header byte for it did not exist yet. For those, the most plausible encoding is chosen by inspecting the text, and the conversion tells you it had to guess. The API takes a sourceEncoding parameter (e.g. cp866) to force it instead of guessing, though the widget above does not have a control for it yet.
• →Memo columns keep their text in a separate .dbt or .fpt file. If the .dbf declares one and it was not uploaded, the conversion stops and tells you which file to add, rather than handing you a table whose long text is silently blank.

Writing SQL Server

• →String literals carry the N prefix, so non-ASCII text survives whatever collation the database uses.
• →Timestamps become DATETIME2. T-SQL’s TIMESTAMP is a row-version counter, not a point in time.
• →Identity columns are wrapped in SET IDENTITY_INSERT so explicit key values load.
• →Statements are separated with GO in batches.

Convert xBase to something else

• MySQL
• PostgreSQL
• Oracle
• SQLite
• DuckDB
• CSV
• Excel

Convert something else to SQL Server

• CSV
• Excel
• SQLite
• SQL dump
• JSON
• XML
• Parquet
• DuckDB
• MS Access
• PostgreSQL backup