Set up the database for your CollabNet TeamForge site on a separate server

If you expect your site to have a high rate of user traffic, you may want to run the site's database on its own server.

The database is where users' project pages, documents, tracker artifacts, tasks, discussions and other work products are stored and accessed.

To run your TeamForge site's database on its own server, you must install the database and configure TeamForge to work with it.

The advantage of hosting a service on a separate server is that it does not share CPU, RAM or I/O bandwidth with the server that is hosting the main TeamForge application.

Note: Each TeamForge site can have only one database server.