Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Database connection can be configured in Verba on profile or on per server level.

  • In order to configure the database connection settings on the profile level, go to the Administration / Configuration Profiles menu and select the profile. The configuration can be found at the Change Configuration Settings tab.
  • In order to configure the database connection settings on the server level, go to the Administration / Verba Servers menu then select the server that needs to be configured. The configuration can be found at the Change Configuration Settings tab.

The database connection settings can be found under the Database Connection node.

Settings NameDescription
Database Hostname

The hostname or IP address where the database server hosted. If the database is a named instance then provide the instance also. In case of Always-on database, the connector name. If custom port used then use the hostname:port format or turn on the SQL Server Browser service at the database side. Examples:

  • (local) - (SQL Server running co-hosted on the Verba server using the default 1433 port)
  • verba-db-server.acme.com - (SQL Server using the default 1433 port)
  • verba-db-server.acme.com:15001 - (SQL Server using the 15001 port)
  • verba-db-server.acme.com\InstanceName - (SQL Server named instance using the default 1433 port)
Database NameThe name of the Verba database.
Database Windows AuthenticationSet to Yes if Windows authentication used.
Database LoginThe SQL username or the Windows username with the domain for the database access. In case of Windows authentication, a Windows service user has to be used for the Verba services.
Database PasswordThe password for the SQL/Windows user.
Database Failover PartnerThe hostname or IP address where the failover partner database server hosted. If the database is a named instance then provide the instance also. If custom port used then turn on the SQL Server Browser service at the database side. Please note that if mirroring is configured then the ODBC 13.1 have to be used as Database Driver.
Database Multi-Subnet FailoverSet to Yes if Always-on database used with Multi-Subnet Failover configuration. Please note that in this case the ODBC 13.1 have to be used as Database Driver.
Database Driver

The driver used for database connection. This driver configuration is only used by specific services in the system, other services use different SQL Server drivers bundled with the product (JDBC driver) or provided by other prerequisites (.NET framework). The following options available:

  • SQL Server (default driver)
  • Microsoft ODBC Driver 13.1, certain advanced features requires this driver instead of the default:
    • Mirroring
    • Always-on with multi-subnet failover
    • SSL based connection encryption and when TLS 1.0 is disabled on the OS level

Microsoft ODBC Driver 13.1 download 

Enable SSL EncryptionSet to Yes if you want to set up SSL encryption. For more information see: Configuring SSL encryption for database connections
Java Trust Store PathJava Trust Store path used for SSL encryption. For more information see: Configuring SSL encryption for database connections
Java Trust Store PasswordThe password for the Java Trust Store. For more information see: Configuring SSL encryption for database connections

Check the firewall configuration on the SQL Server to ensure connectivity with the Verba servers, see https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-2016

 

  • No labels