Previous Topic

Next Topic

New Features for Database Administrators

The new features for database administrators make it easier to administer an Ingres database and allow database administrators to deploy Ingres in a more scalable environment.

Previous Topic

Next Topic

Parallel Query

As a multi-threaded server, Ingres has long supported symmetric multi-processing (SMP) systems by creating individual threads to handle user queries, and executing these queries in parallel across all available CPUs. Ingres 2006 introduces the ability to execute individual queries in parallel across all available CPUs in the system, which greatly improves performance. For more information, see the SQL Reference Guide.

Previous Topic

Next Topic

Key Range Table Partitioning

With the functionality of key range table partitioning, the data in a database can be partitioned based upon the value of a given key, which significantly improves the performance of queries that require a full table scan. For more information, see the SQL Reference Guide.

Previous Topic

Next Topic

Online Modify

The online modify functionality enables users to modify tables while working online. The DBMS performs the modify processing while allowing concurrent updates to the table. For more information, see the SQL Reference Guide.

Previous Topic

Next Topic

Ingres Cluster Solution for Linux

Ingres Cluster Solution is an extension to the base Ingres product that allows it to operate on a cluster as a distributed application, providing transparent access to databases residing on shared storage devices. If there is an Ingres or hardware failure on one of the nodes, only those transactions that are in process on the failing node are aborted and ACID properties are maintained.

Previous Topic

Next Topic

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.

Previous Topic

Next Topic

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.

Previous Topic

Next Topic

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.

Previous Topic

Next Topic

Numeric Overflow Support in Report-Writer

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

Previous Topic

Next Topic

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 re-imaged. Delete the contents of the ABF object directory, $ING_ABFDIR/database-name/app-name, and then re-image.

For details on this new feature, see the SQL Reference Guide.

Previous Topic

Next Topic

System-wide Setting for Default Lock Level

This feature adds a system configuration parameter that allows the Ingres administrator to define the default lock level for the entire Ingres instance.

In previous releases of Ingres, to alter the default lock level the application programmer had to use the SET LOCKMODE statement in the application, which affected only the current session.

The new parameter, system_lock_level, is available to the administrator through Configuration-By-Forms. Valid values are DEFAULT, ROW, PAGE, and TABLE. The DEFAULT value is the default and allows the system to decide the lock level. DEFAULT is the assumed value if the parameter is not present.

Note: Each of the default lock levels is subject to escalation, as in previous releases.

For more information on the default locking level, see the Database Administrator Guide.


© 2007 Ingres Corporation. All rights reserved.