Questions? Chat with us.
© Haptic, LLC*30% off applies automatically at checkout for your first month. Ends September 30, 2026.
FiveMGuideDrop .sql files into the sql folder inside server-data and restart. Your server imports them automatically, no database program needed.
You do not need HeidiSQL, phpMyAdmin, or a database login. Your server imports .sql files from one folder automatically, and a file with a mistake in it cannot stop your server from starting.
Every FiveM server on Haptic has its own private database. Frameworks and scripts use it through oxmysql, which is installed on every server. That database is not reachable from the internet, on purpose: it holds your players' characters, money, and inventories. Instead of handing out database logins, your server watches one folder, server-data/sql, and imports whatever SQL files you put there.
Open your server on Haptic and go to the Files tab. Open server-data, then sql. There is a README inside explaining these same steps. If the folder is missing, create it with New folder and name it exactly sql.
Upload the files straight into that folder. They must sit directly in server-data/sql, not inside a subfolder. If order matters, name them 01-tables.sql, 02-data.sql and so on: files run in alphabetical order.
Each file is imported into your server's database while the server starts. Watch the Console on your server page: you will see a line like Importing customer SQL: 01-tables.sql for each file, and the exact database error if a file has a problem.
Each file runs once. After a file imports, it is remembered and skipped on later restarts. A new file, or a file you changed, runs on the next restart. A changed file runs again in full, so plain INSERT statements will insert again.
A broken file cannot take your server down. It is skipped with the exact error in the console, and everything else still imports. Fix the file, upload it again, restart.
You do not need CREATE DATABASE or USE lines. Everything goes into your server's own database automatically. If your dump has those lines, they are ignored on purpose.
One big dump is fine. Exporting from a local tool? Save it as one file, name it 00-import.sql, and drop it in. If a very large dump will not go through, message us and we will import it for you.
Scripts talk to the database live. Tables your resources create at runtime through oxmysql work as usual. The sql folder is for files you would otherwise import by hand.
Leaving a .sql file inside a resource folder, like server-data/resources/my-script/schema.sql. Scripts do not run those by themselves. Copy the file into server-data/sql instead.
Putting files in a subfolder like server-data/sql/my-pack/. Only files directly in the sql folder are imported.
Connecting a database program straight to a public address. Port 3306 is never exposed to the internet on purpose. If you want to browse or edit the database live with HeidiSQL, Navicat, or DBeaver, use the secure SSH tunnel instead: see Connect to your server's database.