eCG Cloud: data and actions

Back up your data

Download a copy of your app's tables and rows as one SQL file. Learn what the backup holds, the 10,000-row limit per table, and what it does not include.

A backup is a file you download that holds a copy of your app's data. Keep one before you make a big change, before you delete anything, and from time to time while your app collects real orders or sign-ups.

The backup is one file with the ending .sql. It holds your tables and the rows inside them.

Download a backup

  1. Open the console for your app. From the Cloud page, open the eCG Data tab and select the app. Or, in the editor, open More actions, then Project settings, then eCG Data.
  2. Select Backup at the top right of the console. The button reads Dumping… while the file is prepared.
  3. Your browser downloads the file. A message says Database dump downloaded.

The file is named after your database and the time of the download, for example tenant_ab12-dump-1760000000000.sql. Each download has a different name, so a new backup never replaces an old one.

The Backup button is unavailable until eCG Data is active. See eCG Data: your app's database for statuses.

What is in the file

Included Not included
Every table Indexes, which make searches fast
The type of each column Links between tables (foreign keys)
The main identifier of each table (the primary key) Counters that number new rows (sequences)
The rows of each table Access rules for visitors (row protection policies)
Functions, views and custom types
Your eCG Actions and your Secrets
Your app's pages and files

The file starts with a short comment that lists these limits, so a person who opens it later knows what it is.

In short, the backup is a copy of the data, with the basic shape of the tables. It is not a copy of the whole app.

The 10,000-row limit

A backup holds at most 10,000 rows per table. If a table has more, the file keeps 10,000 of its rows and leaves out the rest. This limit applies to each table on its own: three tables of 9,000 rows are all complete.

When this happens, you see this message after the download:

Dump downloaded, but some tables were cut at 10,000 rows. Export those tables another way if you need every row.

Inside the file, the cut table carries a warning line, "table orders truncated to 10000 rows", so you can tell which one.

If a table is larger than 10,000 rows

You have two choices:

  1. Ask the agent to add an export. For example: "Add an Export button to my admin page that downloads all orders as a spreadsheet." The agent builds it with an action that reads your table. See eCG Actions.
  2. Copy the rows in parts. In the SQL tab, run a query with LIMIT 5000 OFFSET 0, then OFFSET 5000, and so on, and copy each result. This is slow, so use it only for a few thousand extra rows. See Browse tables and run queries.

Keep the file safe

  • Store the file in a private place that only people you trust can open.
  • Name your copies by date so you can tell them apart.
  • Do not attach a backup to a chat with the agent or to a support request unless you were asked to, and then remove personal details first.

Restoring from a backup

eComGear does not have a Restore button. The file is a standard SQL file. A developer can run it against a database to recreate the tables and fill them with the rows.

If you need help bringing data back, contact support and tell them what was lost and when. Attach the file only when support asks for it. See Get help.

When to take a backup

Before you Why
Delete eCG Data Deleting is permanent. See eCG Data.
Run SQL with service (full access) A wrong DELETE or DROP cannot be undone
Ask the agent for a big change to your tables It is cheap insurance
Import or edit many rows at once A mistake spreads over many rows