Abstract: A computer-implemented method for determining a coordinator node in a database as a service (DBaaS) infrastructure includes receiving, via a processor on a receiving node, an application connect request having data request information, where the data request information refers to data stored in the DBaaS infrastructure and includes a predefined priority metric, selecting, via the processor, a candidate node in the DBaaS infrastructure, determining, via the processor, whether the candidate node is overloaded, comparing, via the processor, responsive to determining that the candidate node is not overloaded, the predefined priority metric to at least one predefined node priority, writing, to a memory, a comparison record indicative of a comparison of the predefined priority metric with the at least one predefined node priority in the candidate node, where comparison record is stored in a catalog table, and selecting, via the processor, the candidate node as the coordinator node.

Abstract: A computer-implemented method for determining a coordinator node in a database as a service (DBaaS) infrastructure includes receiving, via a processor on a receiving node, an application connect request having data request information, where the data request information refers to data stored in the DBaaS infrastructure and includes a predefined priority metric, selecting, via the processor, a candidate node in the DBaaS infrastructure, determining, via the processor, whether the candidate node is overloaded, comparing, via the processor, responsive to determining that the candidate node is not overloaded, the predefined priority metric to at least one predefined node priority, writing, to a memory, a comparison record indicative of a comparison of the predefined priority metric with the at least one predefined node priority in the candidate node, where comparison record is stored in a catalog table, and selecting, via the processor, the candidate node as the coordinator node.

Abstract: Methods and apparatus, including computer program products, implementing and using techniques for optimizing query performance in a relational database management system. A query is received at the relational database management system. It is determined whether the query is expected to be a long-running query. In response to determining that the query is expected to be a long-running query, a full table scan is started in order to fetch records needed to satisfy the query from the relational database management system. In parallel with conducting the full table scan, a performance object is built, which is capable of satisfying the query in the relational database management system. In response to completing the construction of the performance object prior to completing the full table scan, the full table scan is stopped and the newly built performance object is used instead to satisfy the query.

Abstract: Methods for optimizing query performance in a relational database management system. A query is received at the relational database management system. It is determined whether the query is expected to be a long-running query. In response to determining that the query is expected to be a long-running query, a full table scan is started in order to fetch records needed to satisfy the query from the relational database management system. In parallel with conducting the full table scan, a performance object is built, which is capable of satisfying the query in the relational database management system. In response to completing the construction of the performance object prior to completing the full table scan, the full table scan is stopped and the newly built performance object is used instead to satisfy the query.

Abstract: Methods for optimizing query performance in a relational database management system. A query is received at the relational database management system. It is determined whether the query is expected to be a long-running query. In response to determining that the query is expected to be a long-running query, a full table scan is started in order to fetch records needed to satisfy the query from the relational database management system. In parallel with conducting the full table scan, a performance object is built, which is capable of satisfying the query in the relational database management system. In response to completing the construction of the performance object prior to completing the full table scan, the full table scan is stopped and the newly built performance object is used instead to satisfy the query.

Abstract: Methods and apparatus, including computer program products, implementing and using techniques for optimizing query performance in a relational database management system. A query is received at the relational database management system. It is determined whether the query is expected to be a long-running query. In response to determining that the query is expected to be a long-running query, a full table scan is started in order to fetch records needed to satisfy the query from the relational database management system. In parallel with conducting the full table scan, a performance object is built, which is capable of satisfying the query in the relational database management system. In response to completing the construction of the performance object prior to completing the full table scan, the full table scan is stopped and the newly built performance object is used instead to satisfy the query.