The Surround SCM Server database and mainline branches are stored in an RDBMS database, such as PostgreSQL. You can modify the internal Surround SCM database format and data from the RDBMS database, but we do not recommend it. Your Surround SCM maintenance contract does not include support for recovering from these types of database changes.
Configuration changes
We recommend making configuration changes using the Surround SCM Client instead of at the database level. Making changes directly in the database requires a full understanding of the Surround SCM database format and the rules enforced at the software level.
Database table changes
Do not reconfigure the Surround SCM database format. Do not change database tables/column names, modify column size/attributes, or make any other structural database changes as it will result in errors running Surround SCM.
Live updates
Surround SCM caches data to improve performance. Do not perform live updates of Surround SCM at the database level unless the Surround SCM Server has been shut down. Adding, editing, or deleting Surround SCM data while the server is running results in errors and potential data loss. Your changes may be overwritten next time the record is modified because database changes are not immediately read into the Surround SCM cache.
Surround SCM does not prevent users from opening the database in read/write mode while the Surround SCM Server is running. To perform live Surround SCM data updates, use methods available in the Surround SCM Client or CLI Client.
Note: You can lock Surround SCM databases to prevent users from performing actions that write to the database, such as checking out files. See Locking databases for backups.