Contents
Container Manager

Connection Properties

Connection Propeties dialog allows to modify all properties available for Microsoft SQL Servers.

User has two options to modify parameters. First, you can change corresponding parameters in the list. The second way -- you can edit the entire connection string directly which is located in "Data" section. All changes made to the connection properties are reflected in a "Connection String" at the top of the window.

Below is a list of the most commonly used properties:


  • Section "Security":
    • Integrated Security -- Indicates whether the connection is to be a secure connection or not. When integrated security is set to "True", SQL Server leverages Windows NT authentication to validate SQL Server logon accounts. Otherwise SQL Authentication is used.
    • User ID -- User login name which is used for SQL Authentication
    • Password -- User password which is used for SQL Authentication
    • Encrypt -- Turns ON SSL encryption for SQL Server DB Instances. Please see Encryption for more details.
    • TrustServerCertificate -- When the Encrypt property is set to True and the TrustServerCertificate property is set to True, Combine will not validate the SQL Server SSL certificate. This is usually required for allowing connections in test environments, such as where the SQL Server instance has only a self signed certificate.
      Please note that Combine version 6.2 and below always turn ON this property. But for security reasons Combine 6.3 (and above) does not enable this property by default. So if you have self signed certificates you have to manually switch TrustServerCertificate property to True.
      To setup SSL certificates on Amazon please refer to the Amazon documentation
    • Column Encryption Setting -- Enables Always Encrypted feature. To use this feature please make sure that .NET Framework version 4.6 or higher is installed on your development machine. For details, please see .NET Framework 4.6 documentation. Please note that, enabling Always Encrypted is not sufficient for encryption or decryption to succeed. You also need to make sure:
      • The application has the VIEW ANY COLUMN MASTER KEY DEFINITION and VIEW ANY COLUMN ENCRYPTION KEY DEFINITION database permissions, required to access the metadata about Always Encrypted keys in the database. For details, see Permissions section in Always Encrypted.
      • The application can access the column master key that protects the column encryption keys, encrypting the queried database columns. The simplest way to achieve it is to put corresponding master key certificates into a Windows Personal Certificate Store with certmgs.msc utility.

  • Section "Pooling":
    • Pooling -- Enables connection pooling.
      Combine version 6.2 and below does not use pooling. Combine since version 6.3 lefts this property in it's default state -- True. So if you no need pooling you should manually turn this option OFF.

To see detailed explanation of other properties please refer Microsoft SQL Server documentation.


Note. List of Connection Properties contains all available parameters for SQL Server. All of the parameters have default values which are used when the parameter is not specified in a connection string. When parameter is set to such default value it is listed using ordinary font, so user is able to see which value will be used. When user changes any value -- this value is displayed in bold to reflect the fact that it is not a defult. Also this parameter is added to the resulting ConnectionString which will be send to SQL Server.
To restore default value for a parameter user may directly edit the entire connection string in "Data" section and remove the parameter form the string.




Figure 1:  The Connection Properties dialog.





© 2001-2018 JNetDirect, Inc. All Rights Reserved.