InterBase 2017 Update 2 Readme

From InterBase

Go Up to Main Page

This release introduces bug fixes. See Resolved Defects for a complete list of bug fixes. This release introduces new features see New Features for details.

This Readme covers the following sections:

Note: Click Previous Releases for all releases prior to InterBase 15.
Note: Click here to view the resolved issues and the new features of the 2017 release.


New Features

There are no new features on this release.

Other

Order of prepared parameters

In a parameterized query, the order of parameters received for an Input SQLDA has been fixed. The fixed order is now both intuitive and in "visible order" as per ANSI/SQL standard requirements. This is useful especially when parameters are used in the main query's conjuncts (WHERE conditions), and in the query's column-list which have one or more sub-query(s) themselves with parameters in them. The client API, isc_dsql_describe_bind(), now correctly returns the visual order sequence number for each parameter in the input SQLDA and uses it internally to transform the user provided SQLVARs to InterBase engine expected order. The changes are only available for SQLDA version >= 2.

A new example, api17.c, has been provided to showcase how this works. The sample below showcases how named parameters are used in IBX and FireDAC components. The named parameters should work for both :TEST and :NO in that parameter order. The client component is expected to provide values in the SQLVAR array in the visible order of :TEST followed by :NO parameters. 

select P.emp_no, P.first_name, P.last_name, (select 1 from RDB$DATABASE where 1 <> :TEST) 
from employee P 
where P.emp_no = :NO

New IBConfig parameter PREDICTIVE_IO_PAGES

This parameter allows you to manipulate the number of pages to be prefetched. This parameter should be left on its default status and changed only for testing purposes when it is suspected to produce performance issues. You can find more information Here.


New IBConfig parameter ENABLE_PARTIAL_INDEX_SELECTIVITY

This parameter allows you to enable/disable the use of partial index selectivity data for SQL query optimization. This parameter should be left on its default status and changed only for testing purposes when it is suspected to produce performance issues. You can find more information Here.


Change View Performance

In InterBase 15 Change View retrieval performance has been enhanced.

Note: This performance enhancement only works on ODS 17 databases.


First Sweep of a Restored Database is now a Fast Sweep

With InterBase 15, any database that you restore is immediately marked as swept, therefore the first sweep of that database is a fast sweep. In order to take advantage of this feature, you need to perform a database restore with InterBase 15 and use either ODS 15 or ODS 16. See Sweep Interval and Automated Housekeeping for more information about sweeping.


Bug Fixes

See Resolved Defects for a list of bug fixes in InterBase 2017 Update 2.


System Requirements/Prerequisites

For system requirements to install and run InterBase, see System Requirements/Prerequisites.


Migration Issues for InterBase 15

  • ODS 17/18 to ODS 19
  • admin.ib and EUA databases: ODS 19 will support SHA-256 password digest for user accounts. SHA-1 and DES-CRYPT will continue to be supported in non-FIPS environments.
    • Migration: To use SHA-256 password digest for user accounts (mandatory for FIPS environments), recreate InterBase user accounts on admin.ib with ODS 19 (with default SHA-256 password digest). If you just restore/copy an admin.ib, from IB2020 or prior, it will only allow the weaker digest algorithms DES-CRYPT and SHA-1 digest accounts.
  • Old clients (IB2020 and prior) will not be able to connect to new server accounts with SHA-256 password digests. Use new InterBase clients to connect.
  • ODS 19 EUA databases, cannot be restored back to ODS 18, if embedded user accounts have SHA-256 password digests.
  • InterBase 15 will not have any support for DES encryption.
    • All server-based Editions, and ToGo Edition, will support AES encryption strengths 128/192/256.
    • AES encryption default strength will be 256 bits, the strongest available in InterBase; versions 2020 and prior had a default of 128 bits.
  • If migrating EUA/Encrypted databases from (version 2020 and prior) to InterBase 15, execute following steps:
    • Using InterBase 2020, convert your database to use AES encryption instead of DES. Then, backup the database and restore into InterBase 15 instance


Known Issues

  • On macOS, InterBase Server Edition, Japanese Language installer brings up the English UI. Current diagnosis indicates this is a problem with the InstallAnywhere version used by us and there is no workaround.
  • Issue:Server-side Performance Monitoring via admin.ib works using ISQL command-line tool, but throws a "Key violation" exception when used via IBConsole Performance Monitoring UI

Resolved Defects

Click here for list of resolved defects in InterBase XE7

Additional Resources

Embarcadero Technologies Technical Support

If you have a valid maintenance contract with Embarcadero Technologies, the Embarcadero Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation. We encourage you to visit the Support section of our Web site.

Embarcadero Technologies on the Web

Evaluators receive free technical support for the term of their evaluation. To download evaluations of Embarcadero Technologies products or to learn more about our company and our products, visit us at http://www.embarcadero.com/.
Retrieved from "https://docwiki.embarcadero.com/InterBase/15/e/index.php?title=InterBase_2017_Update_2_Readme&oldid=31795"