Skip to main content

Installing database client software

Bravura Security Fabric requires a database client in order to connect to the Microsoft SQL Server. At a minimum, both of the following drivers must be installed before installing Bravura Security Fabric :

  • Either Microsoft SQL Server 2008 Native Client or Microsoft SQL Server 2012 Native Client

    AND

  • Microsoft OLE DB Driver 19 for SQL Server

    You must install Microsoft Visual C++ 2015 Redistributable (x64 and x86 versions) as a pre-requisite

Depending on the version of Microsoft SQL Server, these drivers may already be installed provided that "Client Tools Connectivity" was selected during setup. Otherwise, obtain and install these drivers from the official Microsoft website.

Note

To verify if your system has the correct OLE DB Driver installed, click the Windows Start icon and open the system settings "Apps and Features" category. Scroll down the list to find the "Microsoft OLE DB Driver 19 for SQL Server" program. If it does not appear in your list, it must be downloaded and installed.

If you decide to install Bravura Security Fabric on a system different from the database, you do not need to install Microsoft SQL Server, however, you will still need to install the required database client drivers.

Connection settings

The OLE DB driver connection settings are managed by Microsoft, version-specific:

https://learn.microsoft.com/en-us/sql/connect/oledb/applications/using-connection-string-keywords-with-oledb-driver-for-sql-server?view=sql-server-ver16

For example, for connection encryption, in case a test database server uses self-signed certificates: https://learn.microsoft.com/en-us/sql/connect/oledb/features/encryption-and-certificate-validation?view=sql-server-ver16

The settings are placed in iddb's registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Bravura Security\Bravura Security Fabric\instance-name\MSSQL

There are two String values to use: CustomOptions and CustomOptionsPooled.

If only one setting is needed, no quotes are required but both the connection setting and its value are provided.

In the example above, to bypass the certificate validation if trust cannot be established the normal way (and not for production instances), the values of both strings would be either TrustServerCertificate=True or for more security "HostNameInCertificate=hostname" "TrustServerCertificate=True". where hostname is the value used in the certificate used on the SQL database.

In this section: