1. Home
  2. KBAs
  3. Goverlan SQL Server Configuration

Goverlan SQL Server Configuration

Goverlan SQL Server Configuration

Goverlan Reach requires 2 databases:

  1. Server Database – This is for server specific operations.
  2. Console Database – This is for the consoles themselves.

 

IMPORTANT NOTE: Do not pre-create the databases. They will be created when the Reach Server or Console is run for the first time.

Minimum Supported SQL Server is Microsoft SQL Express or SQL Server 2008.

Network Configuration

For new SQL Server or SQL Express installations, you may need to follow these steps before SQL is ready for use.

  1. Go to Start –> All Programs –> SQL Server
  2. Run SQL Server Configuration Manager.
  3. Go to SQL Server Services.

OPTION 1 – SQL Browser Service Enable for DYNAMIC PORTS:

NOTE: This is for configuring SQL with DYNAMIC PORTS. This is the default configuration on new SQL Express Instances.

  1. Right click SQL Server Browser > Properties > Service tab > Start Mode. Change this to Automatic. Then click Ok.
  2. Right click SQL Server Browser > Start.

SQL Network Configuration:

 

  1. Go to SQL Server Network Configuration > Protocols for SQLEXPRESS.
  2. Make sure TCP/IP is enabled.
  3. Right-click on TCP/IP and select Properties.
  4. Scroll down to IPAll.
  5. Verify that Dynamic Ports has some random port. (This should be the default)
  6. Make sure that TCP Port is set to blank. (This should be the default)

 

OPTION 2 – SQL Server Service with a specified port:

  1. Go to SQL Server Network Configuration > Protocols for SQLEXPRESS.
  2. Make sure TCP/IP is enabled.
  3. Right-click on TCP/IP and select Properties.
  4. Scroll down to IPAll.
  5. Verify that Dynamic Ports is blank.
  6. Make sure that TCP Port is set to the port you would like to specify (Typically 1433)

 

If you use this configuration, you must specify the TCP port in the Goverlan Database configuration:

Add (comma) and the port number to the SQL Server Name \ Instance field.

This applies to both server and console configurations.

 

SQL DB Creation

The Goverlan Reach Products will create the DB on initial connection. This requires the following:

  • The Reach Server Service account must have the DBCREATOR role on the SQL Server.
  • The user running the Goverlan Reach Console must have the DBCREATOR Role on the SQL Server.

If the Reach Console user does not have the rights, you may RIGHT CLICK –> RUN AS DIFFERENT USER on the Goverlan Reach Console Icon.

SQL DB Rights Configuration
Goverlan Reach Console DB requires that each Goverlan Reach user has at least DataReader and DataWriter permission to the database after it is created.

Configure the following security settings to allow Goverlan Reach users to read and modify the database.

  1. Open the SQL Management Studio
  2. Expand Security –> Logins
  3. Right Click Logins
  4. Select New Login


It is recommended that you add a Security Group here and have your Goverlan Reach users as members of that security group.

OPTION 1 – Windows Authentication

  1. Click the Search button
  2. If you are in an Active Directory Domain, select “Location”
  3. Choose your AD Domain
  4. If you are using an AD Security group to assign permission, click Object Types
  5. Select Groups
  6. Enter your AD Group or account name and click OK.

OPTION 2 – SQL Authentication

Use SQL Authentication to use a non Windows or AD based credential to access the database.

  1. Select SQL Server Authentication
  2. Enter a password and confirm it
  3. Uncheck “Enforce password policy” (optional: consult your organizations security policy)

The use name and password specified here must be specified in the Goverlan Database settings.

Mapping the account to the Goverlan Reach Console DB

Mapping the account to the SUREDATA database will allow you to assign permissions.

  1. Select the Default Database as the Goverlan SUREDATA DB. By default the name is GoverlanV9_DB.
  2. Select User Mappings
  3. Check the GoverlanV9_DB
  4. The minimum permissions to give are db_datareader and db_datawriter. db_owner is also acceptable.

Was this article helpful?

Related Articles