SQL Server

Prerequisites

Dedicated server running Windows Server 2012 R2 or higher with at least 4 GB RAM and dual cores.

Please note that all installations must be run as an administrator with elevated privileges.

Installing

Download the SQL Server 2017 Express installer (SQLEXPR_x64_ENU.exe) from this page microsoft.com and place the file in the same location as the nodeprotect binaries.
Start the installation file (SQLEXPR_x64_ENU.exe).
When presented with the following dialog choose ‘New SQL Server stand-alone installation or add features to an existing installation’.
On the next screen confirm the license agreement.
On the next screen confirm that the global rules report does not return any issues.
On the next screen choose whether to use the Microsoft Update to check for updates.
On the next screen verify that the rules can be applied.
On the feature selection screen choose to install the Database Engine Services feature.
On the instance configuration screen choose to install a new named instance.
On the server configuration screen verify the following configuration.
On the database engine screen verify the following configuration.
On the summary screen verify that the installation was successfull.
Important: Install Microsoft SQL Server Management Studio.
Start Microsoft SQL Server Management Studio and click “Connect”.
Right-click and choose “New Database…”.
Enter database name “nodeProtect.Idp” and click OK.
Create a new database for nodeProtect Admin Web with the name “nodeProtect” and click OK.
Right-click on Login and select “New Login…”. (We will create a total of three “Logins” so this should be repeated three times).
The first Login is for IDP and Login name is like the image below “nodeProtectIdp”. Enter a password. Uncheck Enforce password policy. User “nodeProtectIdp” should have default database “nodeProtect.Idp” (see image below).
Under the User Mapping tab -> check “nodeProtect.Idp” and check role “db_owner”. Click OK.
The second Login is for Web and Login name is like the image below “nodeProtectWeb”. Enter a password and uncheck Enforce password policy. User “nodeProtectWeb” should have the default database “nodeProtect” (see image below).
Under the User Mapping tab -> check “nodeProtect” and check role “db_owner”. Click OK.
The third Login is for AgentAPI and Login name is like the image below “nodeProtectAgentAPI”. Enter a password and uncheck Enforce password policy. User “nodeProtectAgentAPI” should have the default database “nodeProtect” (see image below).
Under the User Mapping tab -> check “nodeProtect” and check role “db_owner”. Click OK.
SQL Server installation completed. Continue to Internet Information Services (IIS).