Ingres® 2006 - Release Summary

Peter Kitson

ISBN : -

Order a printed copy of this book from Amazon --UNAVAILABLE--


Cover Design - Ingres® 2006 - Release Summary
  

For your free electronic copy of this book please verify the numbers below. 

(We need to do this to make sure you're a person and not a malicious script)

Numbers

 



Sample Chapter From Ingres® 2006 - Release Summary
     Copyright © Ingres Corporation



What Is Ingres 2006?

Ingres 2006 is an enterprise-class open source database. It is a reliable, highperformance database solution that offers scalability, integration, and flexibility. Ingres scales from the laptop to the cluster in a single version and has the lowest total cost of ownership in the industry. Its enterprise-class features are available under an Open Source license. Designed for “set-and-forget” operations on a compact footprint, Ingres is the ideal unattended database for both enterprise and embedded deployment. Ingres 2006 was previously released by Computer Associates as Ingres r3.

The open source model provides many business and technical advantages, such as:

  •   Ability to receive features more quickly
  •   Ability to extend Ingres to meet specific requirements
  •   Collaboration on projects
  •   Building relationships with leading open source application vendors
  •   More easily extending support to non-traditional or emerging platforms
  •   Enhancing security by providing code that is less vulnerable to attack

Features Included in Open Source

The following Ingres components are contributed to the open source community:

  •   Ingres DBMS and associated database administration tools
  •   Embedded SQL precompilers
  •   Character-based querying, reporting, and application development tools
  •   Connectivity components, including ODBC, JDBC, and the .Net Data Provider
  •   Ingres Distributed Option
  •   Ingres Replicator Option
  •   Ingres Web Deployment Option
  •   TP monitors, including CICS, Tuxedo, and Encina

Features Not Included in Open Source

Features not included in the open source edition are as follows:
  •   Support for spatial objects
  •   B1 security
The spatial object library is available for download from www.ingres.com if you have a valid technical support contract with Ingres Corporation.

While the source for the Visual DBA suite is not contributed to the open source community, the suite is included in the Ingres for Windows download.

The following members of the Ingres product family are not contributed to open source and continue to be available for purchase from Ingres Corporation:

  •   OpenROAD
  •   Enterprise Access
  •   EDBC products

Ingres High Availability Option

Ingres 2006 provides automatic failover support for Ingres clusters on Sun Solaris and Windows. For more information, see the System Administrator Guide.

Unextenddb Utility

Ingres 2006 introduces an unextenddb utility, which provides the ability to unextend a database location. For more information, see the Database Administrator Guide and Command Reference Guide.

Killing Queries

Ingres 2006 provides the ability to kill a query in another session while leaving the session in place. For more information, see the Command Reference Guide.

Numeric Overflow Support in Report-Writer

Ingres 2006 provides support for numeric overflow in Report-Writer. For more information, see the Command Reference Guide.

Collation Specification at the Column Level

This feature allows the specification of a collation sequence at the column level that differs from the database default collation sequence. A new optional “collate” clause is added to the column specification on the create table statement. The collate clause lets you specify a case-insensitive collation for columns that contain Unicode data.

In previous releases of Ingres, the DBA had the option when creating a database of defining a collation sequence to be used for non-Unicode text columns. The Unicode standard default collation sequence was provided for Unicode text columns. These collation sequences were in effect for all columns in the database and could not be changed without recreating the database.
 
Note: As part of this feature, the data descriptor used throughout the Ingres system changed. This data descriptor is also compiled into imaged ABF applications. After upgrading to Ingres 2006, all ABF applications should be reimaged. Delete the contents of the ABF object directory, /database-name/app-name, and then re-image.