Hello We use 9 table setup since multiple years. The answer as usually is "it depends" :-)
Without 9 table layout, you have multiple tables per user. That leads to a lot of tables when you have a lot of users.Depending on your database management system (dbms) that can lead to problems in itself. The pro side is, that you can manipulate each users date easier in the database itself, without impacting other users.
Our main issue was dumping sogo for backups.As the dbms has to dump all table create statements and the content, it took considerably longer and produced a lot more output than necessary.
Also caching in the dbms is better when using 9 table layout. So in short: If you have not many users, it doesn't matter at all. If you have many users (>1000) 9 Table is the way to go. As for the script.It should still work, but afterwards you have to run all post Version 3.0.0 scripts too.
Currently those are: sql-update-3.2.10_to_4.0.0.sh or sql-update-3.2.10_to_4.0.0-mysql.sh sql-update-5.5.1_to_5.6.0.shWe switched to 9 table layout by using the sogo-tool backup and sogo-tool restore.
That resulted in our setup in a shorter downtime. Your mileage may vary. Kind regards, Christian Mack Am 01.08.22 um 10:04 schrieb Dirk Schäfer ([email protected]):
Hi,the documentation [1] mentions the possibility of using a database schema with a total of 9 tables. That would require to add the following additional parameters to to /etc/sogo/sogo.conf:- OCSStoreURL - OCSAclURL - OCSCacheFolderUR Would you suggest to use that schema? What are your experience in terms of performance?Is a migration still possible / advisable using `/usr/share/doc/sogo/sql-update-3.0.0-to-combined*.sh`?Kind regards, Dirk Schaefer[1] https://www.sogo.nu/files/docs/SOGoInstallationGuide.html#_database_configuration
-- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre, Infrastruktur 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
