> On Feb 12, 2026, at 07:27, Charles Gagnon via gnucash-user > <[email protected]> wrote: > > I've been running GnuCash for years with a MySQL DB as the backend. I host > the DB in GCP, so the app is a frontend, and I can run it on any computer. > > For performance and offline access reasons, I've been considering using > SQLite3 locally instead. I would back up the .gnucash file regularly. I > already do this for smaller entities with tarball backup in Google > Drive. But I would love to keep a MySQL copy somewhat up to date, maybe > weekly during busy periods or monthly after close. > > Would a simple "Save as..." to the MySQL endpoint, as-needed, work? Would > it automatically overwrite everything that's already there? Or would it > know what changed since the last save? Or would I have to start from a > clean DB for every save? > > I have custom reporting I do directly from the DB, and would like to keep > this option open. Unfortunately, I don't know much about the different > backends or how they open and save.
It should offer to delete the existing database and write the whole thing fresh, and if it works right it will delete with DROP DATABASE so your DB user will need that priv. That will also drop any customizations you’ve made to the DB. I’ve never tried directly saving over an existing remote DB so you should test carefully before trying with production data. The SQL backend is simple and assumes that it has exclusive access to the database. It loads the whole thing into memory at the beginning of the session and writes changes as they happen. The only history it keeps are the rather limited transaction logs. Regards, John Ralls _______________________________________________ gnucash-user mailing list [email protected] To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
