Free forever SQL-Ledger Hosting

tl;dr: Signup here: https://account.ledger123.com/

From today we are offering free forever SQL-Ledger hosting. You can signup and create as many databases as you want to.

Control panel also offers you to upload your own backup, download your backup, upload templates and download templates.

Free support through this forum as well as through forum on this website.

Please consider this offering as beta right now as we work more and more on security, fine tuning and documentation.

But one thing you can be rest assured is that it will be free forever.

Please share your suggestions and concerns.

Remembering Dieter Simader and the Future of SQL-Ledger ERP

I’m writing today with mixed emotions. Last year, in February, the open-source community lost a visionary leader with the passing of Dieter Simader, the creator of SQL-Ledger ERP. News of his death was received in reply to a support request by a user signed by his wife, Wilma Simader (as disclosed in the forum post linked below). Dieter’s dedication and innovation not only brought us a powerful accounting tool but also fostered a vibrant community of users and developers.

As someone deeply invested in the SQL-Ledger community, I felt compelled to continue Dieter’s legacy. With that in mind, I’m excited to announce that I will be taking over the development and support of the final SQL-Ledger release by Dieter. This means:

  • Continued Development: I will actively maintain and improve the current version of SQL-Ledger, ensuring its stability and security.
  • User Support: My forums will continue to be a platform for users to seek help, share knowledge, and connect with each other.
  • Documentation & Resources: I’m committed to providing comprehensive documentation and resources to empower SQL-Ledger users of all levels.
  • Usage & Customization Support: Whether you’re just starting with SQL-Ledger or require advanced customization, I’ll be here to offer guidance and support.

While Dieter’s absence leaves a void, I believe his spirit lives on in the strong community he built. Together, we can ensure that SQL-Ledger continues to thrive as a valuable tool for businesses and individuals worldwide.

In the coming weeks, I’ll be sharing more details about my plans for SQL-Ledger’s future. In the meantime, I encourage you to visit my forums and connect with other users.

Let’s honor Dieter’s legacy by keeping SQL-Ledger a vibrant and thriving open-source project.

News source: https://sql-ledger.com/userforum/index.php?mode=thread&id=1793

Cloning SQL-Ledger dataset

Sometimes you need to create a new dataset with exact same customers, vendors, items, chart etc. from an existing dataset.

There are two ways to do that:

  1. Create a blank data set, export data from existing data and then import it again in the new dataset using Import feature.
  2. Create new dataset using existing dataset as template and make adjustments.

Below I am describing second method step-by-step as gives you more accurate final results avoiding all data import issues. You need to be familiar with Linux command line as well as PostgreSQL’s psql command line too.

  1. First create new dataset using admin.pl so that new admin user is added in users/members file as well as templates folder is created. Selection of chart etc. during creation does not matter as we shall remove this database and will create again making copy of existing one.
  2. Remove the database you created above using “dropdb -U sql-ledger your-new-dbname”
  3. Recreate new database using existing database as template: “createdb -U sql-ledger your-new-dbname -T your-existing-dbname”
  4. Remove transactions from newly clone database using these psql commands: “delete from ar; delete from ap; delete from gl; delete from oe; delete from invoice; delete from inventory; delete from dpt_trans; delete from acc_trans; delete from audittrail; delete from payment;”
  5. Reset document numbers in System–Defaults menu.

As always, backup everything first. If you run into any problem, you can post your issue in our support forum referencing this post to get help.