Abstract: Systems, methods and computer program products for testing the stability and efficiency of a database query engine are described herein. In an embodiment, all possible query execution plans considered by a query optimizer are retained in the form of abstract plans (APs). Each AP is then subsequently supplied with a query to test for stack traces and incorrect results that may occur during the execution of the query. An embodiment includes determining an optimizer efficiency index (OEI) by comparing each AP with a query execution plan chosen by the query optimizer and classifying the APs into various performance buckets based on the degree of improvement or degradation in performance with respect to the query execution plan chosen by the query optimizer. In another embodiment to determine the optimizer efficiency index, APs are ranked based on estimated cost and classified into a plurality of categories based on query optimizer estimates and actual execution behavior.

Abstract: Systems, methods and computer program products for inherently integrating mobility with an enterprise are described herein. Enterprise data is accessed from one or more data sources, wherein such data sources may comprise structured and unstructured data sources. The data is transferred from the enterprise to a plurality of mobile devices over a plurality of diverse networks. In an embodiment, such transfer takes into consideration characteristics of the diverse networks. The enterprise receives data generated by mobile devices while performing enterprise-related operations at the wireless edge. The enterprise responds to environmental changes using the received data.

Abstract: Methods, systems, and computer program products for tuning query execution performance in a database management system are described. In an embodiment, query performance issues of chosen database operational logic in a database management system are identified with an external utility provided for use on top of the database management system. The identified query performance issues are resolved selectively in the database management system without modifying the chosen database operational logic.

Abstract: Systems, methods and computer program products for testing the stability and efficiency of a database query engine are described herein. In an embodiment, all possible query execution plans considered by a query optimizer are retained in the form of abstract plans (APs). Each AP is then subsequently supplied with a query to test for stack traces and incorrect results that may occur during the execution of the query. An embodiment includes determining an optimizer efficiency index (OEI) by comparing each AP with a query execution plan chosen by the query optimizer and classifying the APs into various performance buckets based on the degree of improvement or degradation in performance with respect to the query execution plan chosen by the query optimizer. In another embodiment to determine the optimizer efficiency index, APs are ranked based on estimated cost and classified into a plurality of categories based on query optimizer estimates and actual execution behavior.

Abstract: Systems, methods and computer program products for inherently integrating mobility with an enterprise are described herein. Enterprise data is accessed from one or more data sources data sources, wherein such data sources may comprise structured and unstructured data sources. The data is transferred from the enterprise to a plurality of mobile devices over a plurality of diverse networks. In an embodiment, such transfer takes into consideration characteristics of the diverse networks. The enterprise receives data generated by mobile devices while performing enterprise-related operations at the wireless edge. The enterprise responds to environmental changes using the received data.

Abstract: A database system with improved query execution performance is described. In order to achieve as much accuracy as possible by optimizing large block I/O related query plans, the database system implements a methodology employing two new statistical measures for use in a database server. The first statistical measure, called “Data Page Cluster Ratio” (DPCR), indicates the “packing” of data pages by measuring the “clustering” property of the data pages, i.e., how well clustered the consecutive data pages of a given relational table are in the extents. The ratio is measured for data pages accesses either via a scan of an index or via a scan of the table. The second statistical measure, called Index Page Cluster Ratio (IPCR), indicates the “packing” of index leaf pages by measuring the “clustering” property of index pages, i.e., how well clustered the consecutive index leaf pages of a given relational table's index are in the extents.