This installation topic describes installation and configuration details of the V-Suite CORE Database Server. The database server provides data services to connected V-Suite CORE clients and to V-Suite CORE Services. Customers who do not have a Microsoft SQL Server Enterprise/Standard Edition license may choose to install Microsoft SQL Server 2012 Express on the same computer as the INOVX Enterprise Server (IES) in which case you do not have to manually install the database server and can proceed with the V-Suite CORE Server installation and configuration.  You must manually install and configure the V-Suite CORE Database Server if you wish to install the database server on a different computer as IES and/or do not want to utilize the Microsoft SQL Server 2012 Express edition for database services. 

In this topic 


System Requirements

  • Windows Server 2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2.
  • Microsoft SQL Server 2012, 2014 or 2016 (Express edition is supported, Standard or Enterprise Editions are recommended).
  • Refer to this Microsoft article for more SQL Server hardware and software requirements.

Network Requirements

There is a substantial amount of network traffic between V-Suite CORE clients and database server and although a connection through VPN is supported it is highly recommended that V-Suite CORE clients connect to the database server over a high bandwidth, low latency network connection.

SQL Server Installation

Although it possible to configure V-Suite CORE services with an existing (shared) Database Engine Instance, it is highly recommended that you install a V-Suite CORE dedicated instance. Refer to this Microsoft article for more details on database engine instances.

It is assumed that you have either downloaded the SQL Server Installer from the Microsoft download center or have purchased Microsoft provided installation media. The following table describes INOVX recommended Microsoft SQL Server Installer command line switches for customers who wish to install an SQL Database Engine Instance for V-Suite CORE.





Specifies that Setup runs and shows progress through the UI, but does not  accept any input or show any error messages. 



Required, to indicate the installation workflow.



Required, to acknowledge acceptance of the license terms. Required only  when the /Q or /QS parameter is specified for unattended installations



Specifies the component to install. V-Suite CORE just needs the SQL Server Database engine.



Specifies an SQL Server instance name 

For example:


Specifies the security mode for SQL Server. If this parameter is not supplied, then Windows-only authentication mode is supported. V-Suite CORE supports both "Mixed mode" and "Windows authentication mode".



Specifies the password for the SQL Server sa account.


For example:



Adds the current user to the SQL Server sysadmin fixed server role. The /ADDCURRENTUSERASSQLADMIN parameter can be used when installing Express editions.Use of /ADDCURRENTUSERASSQLADMIN is optional, but either /ADDCURRENTUSERASSQLADMIN or /SQLSYSADMINACCOUNTS is required.

Default values:

True for editions of SQL Server Express

False for all other editions



Use this parameter to provision logins to be members of the sysadmin role. For SQL Server editions other than SQL Server Express, /SQLSYSADMINACCOUNTS is required. For editions of SQL Server Express, use of /SQLSYSADMINACCOUNTS is optional, but either /SQLSYSADMINACCOUNTS or /ADDCURRENTUSERASSQLADMIN is required.

For example:



Specifies the startup account for the SQL Server service.

"NT Authority\Network Service" 


Specifies the startup mode for the SQL Server service.

Supported values:






Specifies the state of the TCP protocol for the SQL Server service.

Supported values:

0=disable the TCP protocol

1=enable the TCP protocol


Example (SQL Express):


Example (SQL Standard/Enterprise):



These instructions only apply to the installation of a SQL Server instance for V-Suite CORE. For detailed general SQL Server installation instructions, please refer to Microsoft provided reference materials for more details.

Configure SQL Server TCP Port

V-Suite CORE communicates with the Microsoft SQL Server Database Engine via TCP. Each SQL Instance on the database server will use a different port. The default instance of the Database Engine uses port 1433, but that can be changed. Instances of SQL Server Express and named instances of the Database Engine use dynamic ports ('INOVXSQL2012' is a named instanced). That means that every time that the Database Engine starts, it identifies an available port and uses that port number. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433. If other instances of the Database Engine are installed, it will probably use a different TCP port. Because the port selected might change every time that the Database Engine is started, it is difficult to configure the firewall to enable access to the correct port number. Therefore, if a firewall is used, we recommend reconfiguring the Database Engine to use the same port number every time. This is called a fixed port or a static port. Refer to this article to configure an SQL Server instance fixed port. If V-Suite CORE is connecting to a named SQL instance it will also need to communicate with the SQL Browser Service via UDP port 1434. Refer to this article for detailed information about configuring Windows Firewall to allow SQL Server access. 

V-Suite CORE Database Folders

Before you configure IES you must create V-Suite CORE default data folders. Create these folders on the database server where you have installed Microsoft SQL Server. The following is an example of how you could organize these folders:

It is recommended that you create 3 separate folders, one for the Project Databases, one for the IES Administration Database and one for the Project backups and Satellite databases. This is not a requirement but as a minimum you should separate the backup folder from the database folder(s) so that the backup folder can be shared and is accessible by the V-Suite Administrator (in order to be able to load/exchange backup files). The database folders do not have to be shared but you must make sure that the SQL Database Engine service has the appropriate access rights to the database folder and backup folders. Refer to this article for configuring the file system permissions for SQL Server 2012 and up.