Who we are

We are the developers of Plastic SCM, a full version control stack (not a Git variant). We work on the strongest branching and merging you can find, and a core that doesn't cringe with huge binaries and repos. We also develop the GUIs, mergetools and everything needed to give you the full version control stack.

If you want to give it a try, download it from here.

We also code SemanticMerge, and the gmaster Git client.

Migrate database backend

Thursday, November 22, 2012 Ma Nu 0 Comments

As you may know Plastic SCM is deployed with a nice SqlServer CE backend. Although it performs great, it has a database size limitation, you can't have a database file bigger than 4GB.

So, what can you do when you reach the size limit or you simply want to go into production with a faster backend? Easy, migrate the repositories to a different database engine.

Plastic SCM is flexible and it supports a great number of database engines.
Some of them are embedded systems which means that you don't need anything external to start working with them. Firebird, SQLite and MS SQL Server CE belong to this group.

On the other hand, you will need to install external software to use PostgreSQL, MS SQL Server, MySQL or Oracle. This group performs better in a high demand environment.

Admin tool

You will be able to find the Admin tool inside the Plastic SCM server components .

Admin tool
This tool will allow us to migrate all the repositories from one database system to a new one in a few clicks. In this example we will migrate "Microsoft SQL Server CE" repositories into a MySQL instance, which is also free.

We'll open the Admin tool and we'll click in the "Database" section, as you might see there're two options, click in "Migrate database backend" button to start the process.

Database section
As you can see in the figure below all the supported backends are available except the one you are already using, as I said before, we will choose MySQL.

MySQL as the new backend
MySQL needs some extra parameters, like the server address, the DB user name and finally the password. The "Start migration" button will remain disabled until the information provided is verified by the "Test connection" check. Optionally you can specify a database suffix, prefix and a custom database path in order to store the database files.

MySQL custom information
Note: If the target database system already contains Plastic SCM databases you will need to specify a prefix or suffix. Otherwise the process will not continue.

Now, all we have to do is wait until the process ends. The repositories are going to be migrated into the new database backend one by one.
Repositories conversion
Once the process is finished you will notice that you have a brand new db.conf , automatically created and working with the destination database engine, if you start the Plastic SCM server service everything will be working with your new backend.

New db.conf working with MySQL


Migrating repositories is a hard task made easy by the Admin tool.


Manuel Lucio
I'm in charge of the Customer Support area.
I deal with complex setups, policies and working methodologies on a daily basis.
Prior to taking full responsibility of support, I worked as software engineer. I have been in charge of load testing for quite some time, so if you want to know how well Plastic compares to SVN or P4 under a really heavy load, I'm your guy.
I like to play with Arduino GPS devices, mountain biking and playing tennis.
You can find me hooked to my iPhone, skate-boarding or learning Korean... and also here @mrcatacroquer.

Ma Nu

0 comentarios:

Subscribe to: Post Comments (Atom)