Pain point · Self-hosting & upgrades · Blocks work
Nightly MSSQL backup not created when database name is not the default
1 source thread · first seen 2022-01
Summary
With a custom database name no backups are created for days because the backup script still hardcodes the default database name.
- Affects
- Self-hoster
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“The problem seems to be that the database name is still hardcode”