HomeWindows InstallationUsing a SQL Server databaseWhat do I need to set up before installing the PureCM server?

3.3. What do I need to set up before installing the PureCM server?

  1. Using SQL Server requires the Microsoft ‘SQL Native Client' drivers to be installed before starting PureCM server installation. If they're not present you will be prompted to download them before proceeding.
  2. Create a new database that PureCM will use
  3. Consider the following options:

    1. Database ‘autoshrink' option

      The SQL Server default is to set this to ‘false'. Setting this option to ‘True' is a simple zero maintenance way of handling SQL Server Transaction log truncation. With it set to false you need to handle transaction log backup/truncation in your backup procedures. We would typically recommend that you enable this option unless your Database Administrator thinks otherwise.

    2. Authentication Mode

      The simplest way to allow PureCM to authenticate with SQL Server is to use SQL Server Authentication. With this option, you define a username and password within SQL Server that you provide to the PureCM Installer. PureCM will require an account with most available privileges for the database you choose (as well as SELECT,UPDATE and DELETE the server can also issue CREATE TABLE, DROP TABLE and ALTER TABLE requests during startup/repository creation. Note that we do not recommend use of the default ‘sa' account other than for testing/evaluation (this is the administrative account and has all privileges).

      A slightly better authentication mechanism is to use Integrated/Windows authentication. This means that the Windows account that PureCM is running as must be given access to the database. For this to be easy to administer, it's likely that you'll need to create a Domain Account and specify in the PureCM Server Installer that the PureCM Service should run as this user. The privileges required by the user will be the same as per SQL Server authentication.

    3. Snapshot Isolation

      PureCM works well with the new ‘snapshot isolation' support in SQL Server 2005 and later. This is not enabled by default when creating a database. The Transact/SQL script below will typically need to be run to enable this feature (substituting ‘purecm' for the name of your SQL database below). Snapshot isolation results in reduced locking contention and therefore typically greater throughput.

      alter database purecm set allow_snapshot_isolation ON
      alter database purecm set read_committed_snapshot ON

      select is_read_committed_snapshot_on,
      snapshot_isolation_state from sys.databases where name='purecm'


This page was: Helpful | Not Helpful