The Plastic SCM server transparently handles versioning. It manages both revision's data and metadata in a safe and efficient way. But, where is the data actually stored?

Many version control systems rely on their in-house data management implementation. Plastic SCM uses relational database management systems for that purpose. Relying on those systems has many benefits like having fully transacted operations (ensuring data integrity), performance or well defined backup and restore mechanism.

Plastic SCM can be configured to work with Firebird, Postgresql or SQL Server database back ends, each of them having different features and benefits.

Being able to work with different database back ends is not only good as added value for clients, it is good for software design. Our datalayer is currently ready to support other database systems like Oracle or MySQL.