Preparing a Microsoft SQL Server Installation

Prior to creating a Laserfiche repository whose underlying structure depends on Microsoft SQL Server, we recommend that you create an empty database. By manually creating your SQL database, you can immediately optimize it to best suit the needs of your installation, including determining where the database will be stored, how the database will grow, where logs and other supplemental information will be stored, security, and a backup strategy.

We strongly recommend installing your SQL server on a different computer than your Laserfiche server for best performance. In addition, note that the tempdb database on the SQL server that is used by Laserfiche can grow very large. It is important that you leave enough free disc space on the SQL server computer to allow tempdb to grow. For most installations, 10 GB of space is sufficient, but large or high-load repositories may result in much larger tempdb files. We recommend monitoring the size of tempdb once your installation has been running for some time, and allocating space for it accordingly.

Note: It is not necessary to pre-create your Microsoft SQL Server database. The Laserfiche Repository Creation Wizard can create this database for you when you create your repository.

Note: All SQL tables for the database associated with the Laserfiche repository must be owned by "dbo." If a SQL table is not owned by dbo, you will need to change the owner of that table to dbo.

To prepare a Microsoft SQL Server installation

  1. Create an empty SQL database.
  2. Configure a backup procedure for the newly created database. A SQL database backup routine can be created from the SQL Server Maintenance Plan Wizard (SQL Server Management Studio) or the Database Maintenance Plan Wizard (Enterprise Manager). It is strongly recommended that you set up automated nightly backups for all of your databases.
  3. During the creation of a Laserfiche repository, you will be prompted to choose how Laserfiche will authenticate to SQL Server. You will need to make sure that the specified Windows or SQL Server login account can access SQL Server and is the owner of any SQL databases associated with your Laserfiche repositories. An additional requirement of a SQL Server login account is that you will have to configure SQL Server to use mixed mode authentication.

Important:  If you plan on using Windows authentication when creating or registering a Laserfiche repository, you will need to make sure that the Windows account assigned to the Laserfiche Server can access SQL Server and has been granted the dbcreator fixed server role.

Note: By default, domain administrators and local administrators on the computer hosting SQL Server can access SQL Server and are granted the sysadmin server role.

Warning: Laserfiche Server does not support databases where the XACT_ABORT option is turned on.

Microsoft SQL Server required privileges

The Laserfiche Server service requires certain minimum privileges to create a repository: the user must be allowed to log in to SQL Server and create a database.

First, you will need to create or specify a Windows user account that the Laserfiche server service will log in as. (Alternately, you can enable SQL Server Login, and create a user in SQL Server.) The user must be able to log in to the SQL Server and create databases, but does not need to be a domain administrator. You can grant the user the ability to create databases in one of two ways: by granting the dbcreator fixed server role or by adding the user to the Local Administrators group on the server computer. While adding the user to Local Administrators is simple, it may not be desirable if you want to minimize the number of users with administrator privileges.

If you do not want to add the server service user to any fixed server roles, you can create the database manually and grant the user account full access to the database by making that user the database owner. This will grant the server service user access to the Laserfiche database without granting the ability to create other databases. 

For more information on a specific repository administration topic, return to the repository administration home page.