Microsoft SQL Server
When using MS SQL Server, the following initial database configuration is recommended. However, some of the options below may need to change over time as the work carried out by PhixFlow increases.
Minimum requirements
The following the minimum requirements for a SQL Server database installation to support PhixFlow.
Server settings
Option | Setting |
SQL Server Edition | Standard or Enterprise |
Version | |
Service Name | (Please provide to PhixFlow installation consultant) |
Collation Character set | |
Collation Character set | Latin1_General_CI_AS The database that PhixFlow runs against must be created with the collation set to this character set (see Install the PhixFlow Database Schema), otherwise the performance of PhixFlow can be severely impacted. However, PhixFlow uses TEMP tables for efficient processing of ‘is in’ filter clauses with large numbers of parameters, and this uses the collation setting of the server itself. Therefore, it is strongly recommended that the server is set to use this collation. |
Database settings
Parameter | Setting |
Collation | Latin1_General_CI_AS |
Max Server Memory
Server Authentication
READ_COMMITTED_SNAPSHOT | ON |
Login and user
A command to create the database, along with a local (SQL Server) login, and associated user and user mapping, are provided in Install the PhixFlow Database Schema. If you do not wish to use this command, please consult PhixFlow Support.
Suggested configuration
The following configuration is suggested as a guide. The provision of database files fits in with the scheme presented in MS SQL Server planning for disk partitions on the database server.
Logins
Create a new login as follows:
...
Parameter
...
Setting
...
Login Name
...
phixflow
...
Authentication
...
SQL Server
...
Password
...
Please provide to the PhixFlow installation consultant
...
Enforce password policy
...
No
...
Default database
...
Set to phixflow once the phixflow database has been created (below)
...
Default language
...
As appropriate
Database
Create a new database as follows:
...
Parameter
...
Setting
...
Name
...
phixflow
...
Owner
...
phixflow
...
Collation
...
Latin1_General_CI_AS
...
READ_COMMITTED_SNAPSHOT
...
Server settings
Option | Setting |
SQL Server Edition | Standard or Enterprise |
Version | |
Collation Character set | Latin1_General_CI_AS |
Max Server Memory | Do not set a fixed maximum memory; see MS SQL Server planning |
Server Authentication | SQL Server and Windows Authentication Mode |
Database, login and user settings
Note that it is possible to use MS SQL Server Integrated Authentication to authenticate PhixFlow against the database. This is especially useful on production servers where the number of people who can have access to key passwords is strongly controlled. However, for most instances, a local SQL Server login as below can be used.
The command given in Install the PhixFlow Database Schema will create a database, login and user with the suggested settings.
Filegroups
Name | Default |
PRIMARY | Yes |
ANALYSIS_DATA |
Database Files
Logical Name | Setting |
phixflow | Type: Rows Data Filegroup: PRIMARY Initial Size: 2000 MB Autogrowth: 10% Unrestricted (or as per management policy) Path: (As per management policy) |
phixflow_data_01 | Type: Rows Data Filegroup: ANALYSIS_DATA Initial Size: 100,000 MB Autogrowth: 10% Unrestricted (or as per management policy) Path: (As per management policy) |
phixflow_log | Type: Log Initial Size: 1000 MB Autogrowth: 10% Unrestricted (or as per management policy) Path: (As per management policy) |