[ANSWERED] SQL advantages over the h2 file

[lucas.lima]

Hi there, guys!
From the docs:

Note that in the default configuration Metabase will use a local H2 database for storing all its own application data. This is meant for simple evaluations or personal use, so if you want to run Metabase for a team we recommend you upgrade to a more robust SQL server such as Postgres.

I'm currently running metabase on an EC2 servers, and I'm having some troubles regarding silent crashes, as I reported in this post:

Crashes / Can't save questions

Guys, this is driving me nuts. I simply, quite often, find myself unable to save a native question, for a unkown reason. It will simply stay like this: [image] It may stay like that for 10, 20 minutes, and do nothing. The most annoying thing is that I'm trying to correct a mistyped SQL in the question, at least in this example, and I'm not being able to. And then, the most critical one, metabase simply stops. I run my instance from the jar file (currently on 0.29.3, still looking for agood …

Here is my doubt: why do the docs recommend that? What are the advantages? May this be related to my issues, somehow? What is the advantage of having metabase metadata on SQL rather than h2 file?

[jornh]

See some reasons in:

Issue: Warn users when running H2 as the application database