Connectivity Enhancements

The following connectivity enhancements are included:

A user can connect to a database without having to be defined as an operating system user.

• New default behavior for connecting to a remote instance

A client instance can connect to a remote instance without the need for a local Communications Server and, in some cases, a Name Server.

Note: In some cases, you may need to configure the connection or installation to use a local Communications Server.

For more information, see Using a Local Communications Server for Remote Connections in the Ingres Connectivity Guide.

A new Simple tab in the Ingres ODBC Administrator lets you configure ODBC to connect to a remote database without the use of a local Communications Server or Name Server. For more information, see the Ingres ODBC Administrator help.

The Ingres ODBC Driver allows sets of queries to be defined and executed in an application. In explicit batch execution, a set of create, delete, or update queries are chained together in a single SQLExecDirect() statement.

For more information, see the Ingres Connectivity Guide.

The Ingres JDBC Driver supports new methods in the Java 7 API and JDBC 4.1 Specification.

For more information, see the Ingres Connectivity Guide.

The Ingres JDBC Driver supports output of driver tracing through the Java Logging package (java.util.logging).

For more information, see the Ingres Connectivity Guide.

• Improved .Net Data Provider connection pooling. For details, see the Ingres Connectivity Guide.

• Secure communications encryption between the client and the DBMS Server (see Secure Communications Encryption with AES).

The Communications Server transliterates string connection parameters to and from UTF8 and other character sets.

• Session information added to GCC log messages

Session information, including the user ID, is now logged to the Ingres error log (errlog.log). This helps identify problems in client installations.

Non-GCC errors are no longer logged by default. Such logging can be re-enabled by setting the GCC logging level to 5.

The GCC error_level configuration option is deprecated (ignored).

• Obsolete network protocol drivers are removed (see Obsolete Network Protocol Drivers Removed).