Import each table data in a SQL file to a separate HiperSix table

by

Want to import data from each table in a SQL file to a separate HiperSix table?

Try Withdata FileToDB, a SQL to HiperSix converter, Import each table data in a SQL file to a separate HiperSix table, Easy and Fast.

Download Withdata FileToDB Download FileToDB

Import data from each table in a SQL file to a separate HiperSix table

Select tables in SQL file -> Set HiperSix tables -> Import SQL data to HiperSix

Choose HiperSix and logon.

convert data from each table in a SQL file to a separate HiperSix table - Choose HiperSix and logon

Click “Wizard – 1 File To N Tables” at task dialog.

Import data from each table in a SQL file to a separate HiperSix table - task window

Select the “SQL” file type.

Import data from each table in a SQL file to a separate HiperSix table - select file type

then show the wizard.

1. Open a SQL file, select tables.

Import data from each table in a SQL file to a separate HiperSix table - open SQL file

2. Show existing HiperSix tables, choose “Import Type”.

Import data from each table in a SQL file to a separate HiperSix table - choose import type

3. Set HiperSix tables.

Import data from each table in a SQL file to a separate HiperSix table - set tables

4. Show summary, set “Convert Rows”.

Transfer data from each table in a SQL file to a separate HiperSix table - preview

5. Import data from each table in a SQL file to a separate HiperSix table.

Copy data from each table in a SQL file to a separate HiperSix table - import data

View imported data in HiperSix table

SQL tables to HiperSix converter - view data


More about SQL file to HiperSix converter

SQL → HiperSix reference

Type mapping

Value kindin SQLin HiperSix
IntINTNumeric(10,0)
BigintBIGINTNumeric(19,0)
DecimalDECIMAL(p,s)Numeric(p,s)
FloatDOUBLE PRECISIONFloat
TextVARCHAR(n)Character(n)
Long textTEXT / CLOBMemo
DateDATEDate
DatetimeTIMESTAMP(none)
BinaryBLOB / BYTEA(none)
BooleanBOOLEAN / SMALLINTLogical
JSONJSON / TEXT(none)

Dialect differences

SQL is a file format and HiperSix is a database server, so the target has to be told the types the file never carried - the rows below are where the two sides diverge.

Propertyin SQLin HiperSix
port—(file-based)
identifiersTwo competing conventions: single-quoted literals and diale...—
row limit—(driver dependent)
datesDepends on the dialect: DATE literals, TO_DATE(), or plain ...Date (D)
long text—Memo (M)
binaryDialect-specific: X-quoted literal, 0x hex, or decode()—
separatorStatement terminators (;)—
encodingNo declaration—
typingTypes belong to the target database, and they differ betwee...—
shapeStatements; a dump usually means CREATE TABLE plus INSERT rowsTables of rows and columns
ceilingNo formal limit, but a single INSERT statement has to fit i...—

No counterpart

  • SQL values of kind Date and time have nowhere to go in HiperSix.
  • SQL values of kind Binary have nowhere to go in HiperSix.
  • SQL values of kind JSON have nowhere to go in HiperSix.

Convert your data online, free

Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.