Determine whether Microsoft SQL Server database
components are dedicated to individual FileNet® P8 components or shared components
after you review the requirements
In a shared configuration, multiple
FileNet P8 components can store their
data in a single database. Most components allow for data to be collocated.
However, it is recommended to keep some in dedicated databases:
- The global configuration database: it is recommended not share
this database.
- Object stores and their workflow system data, which is part of
a single application family can be collocated given the factors that
are listed in the following paragraph.
- Rendition Engine data
- IBM® Content Navigator configuration
data: sharing the IBM Content Navigator database
with the global configuration database is not supported.
When you decide about whether to share a database for multiple
components, consider the following factors:
- Database backup/recovery requirements allow for the data in a
single database to be backed up and recovered together.
- Database security allows for collocation of data.
- Sharing of a database might allow for more efficient usage of
database resources like database connections.
Important: 
READ_COMMITTED_SNAPSHOT is
required for the database where the
Content Platform Engine schema is installed.
To enable READ_COMMITTED_SNAPSHOT for the object store, see the instructions
in
Creating a Microsoft SQL Server database for an object store.

The file groups in the database can optionally be
shared.
For SQL Server database
requirements for Rendition Engine,
see the IBM
FileNet Rendition Engine Installation and Upgrade
Guide.