Installation - SQL Server
SQL Server setup considerations
Mixed mode
Omfax products require SQL Server Authentication, so SQL Server should be configured as 'mixed mode' to support this and Windows authentication
Language
Ensure language is set to 'British English' for the 'keyfax' login. This is used by all Keyfax database connections. Note: It is likely that connections into Keyfax will fail for a login language set at 'English', as format will be mm/dd/yyyy (esp. after the 12th of the month!).
Collation sequence
This is currently required to be to Latin1_General_CI_AS. We create tables using this collation sequence.
Hosts file
Where SQL Server (or required file servers reside on a different LAN, it may be necessary to add IP addresses and 'friendly' names to this file (located in the WIN32\drivers\etc folder)
Attaching a Keyfax 3.2 SQL Server database
Keyfax 3.2 uses scripts which are stored in a SQL Server 2000 database. The database files (MDF & LDF) must be copied from the supplied CD and attached to an active Microsoft SQL Server (version 2000).
In most cases, the CD will contain customer specific database files.
Omfax Systems Ltd have adopted a naming convention for SQL Server databases, This contains the 'KF_' prefix before the customer name (or abbreviated name), this allows for identification by Omfax personnel to correctly identify databases being sent to/from Omfax customers.
- KF_[CustomerName]_Data.MDF
- KF_[CustomerName]_Data.LDF
[CustomerName] is replaced with the customer's name or in the case of the Model database be named KF_Model_Data.*
The following files from the CD need copying to the SQL Server data and log folders:
- [CD Drive letter]:\Server\SQL\KF_[CustomerName]_Data.MDF
- [CD Drive letter]:\Server\SQL\KF_[CustomerName]_Data.LDF
The Keyfax application uses SQL Authentication so a SQL login needs to be created in SQL Enterprise against the SQL Server which is to host the Keyfax database.
The login must be as follows:
- Login name: 'keyfax' (lowercase)
- Login password: 'omfax' (lowercase)
- Database: master
- Language: British English
See the following screen capture:
The Keyfax database should then be Attached to the SQL Server as 'KF_[CustomerName], setting the owner as 'keyfax'.
See the following screen capture
The database should be backed up according to the customer's company backup policy. Performing regular backups will ensure that the transaction log space used will be freed and reused, thus avoiding continuously autogrowing the log file which can become huge and have a severe impact on performance.
Database maintenance is the responsibility of each customer; please consult your DBA for implementing a suitable SQL maintenance plan.