Database Software Requirements

<< Click to Display Table of Contents >>

EQuIS 7  >>  Professional > Databases > Install >

Database Software Requirements

EQuIS requires a Microsoft SQL Server relational database management system installed and licensed separately. As of EQuIS Version 7, Oracle database servers are no longer supported.

 

SQL Server Edition

 

EQuIS can be used within any of the following versions or editions of Microsoft SQL Server.

 

Microsoft SQL Server 2016

Microsoft SQL Server 2014

Microsoft SQL Server 2012

Azure SQL Database

 

EQuIS Version 7 requires Microsoft SQL Server 2012 or newer.

 

The EQuIS Enterprise application needs to connect directly to SQL Server. The DBA will need to establish a SQL Server login that can be used by EQuIS Enterprise. Typically, this is a SQL login (username and password). However, Windows Authentication can be used, if desired. In order for EQuIS Enterprise to use Windows Authentication to connect to SQL Server, the machine/domain user for the EQuIS Enterprise Workflow Service and the machine/domain user for the EQuIS Enterprise Web application must be given login privileges to SQL Server and the EQuIS Database.

 

Additionally, EQuIS Professional uses database-level security. This means that each user (using EQuIS Professional) will need a login to the database. These can be either SQL logins or managed via Windows Authentication. EQuIS Professional contains some simple screens for user management, but the tools provided with SQL Server provide more flexibility for managing user logins, permissions, etc.

 

EQuIS Database Size

 

For analytical data, the three tables that will grow most rapidly are DT_SAMPLE, DT_TEST, and DT_RESULT. For all three tables, the maximum record size is less than 4000 bytes. However, most of the fields are varchar fields, so only the number of actual bytes will be stored (along with some slight overhead). Each of those tables contains a remark field that is varchar(2000). It is uncommon for every field to be populated, let alone every field populated with the maximum number of bytes. A fair estimate might be 2000 bytes per record.

 

The next step is to determine the number of records for each table. As an example, assume an estimate of 225000 samples per year. The number of tests is at least one per sample, but often more. The number of results can vary, but for calculation purposes, assume approximately 10-13 results per sample. These calculations may be refined to determine a more accurate approximation based on the typical analysis done for the samples.

 

clip0015b

 

Or a total of (3675000 records) * (2000 bytes per record) = ~ 7 GB of storage for just analytic data per year (not including other data types, indexes, etc).

 

Note: These numbers represent an approximation. Actual size will vary.

 

Each EQuIS Professional user will need Application Level Security where users access the database through an underlying database account, but do not have individual database-level access. This account must have permissions and synonyms to the objects owned by the schema owner account. A script is provided that will assist in creating user accounts, granting permissions, and creating synonyms.