Abstract: Described is a system, method, and computer program product is provided that implements high-volume data ingestion in a relational database system. A middle-tier structure is provided that sits between the IoT data producers and the back-end database system. Data records are gathered together and organized at the middle tier, and groups of those records are ingested on a group-basis into the database in a manner which bypasses standard SQL engine processing.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for server-side connection pool multiple tagging. For example, the system can provide a capability to associate multiple connection properties with a particular server-side connection in, e.g., an Oracle Database Resident Connection Pooling (DRCP) environment; look up a connection with one or multiple properties; and provide information about a returned connection so that a requesting application can review the properties associated with the returned connection, in order to determine how best to “fix-up” or otherwise use that connection.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for limiting the maximum number of connections per tenant or per database shard. For example, when a tenant is associated with a service, configuring a maximum connections per service limit on a shared connection pool indicates to the system that the shared pool should not repurpose existing connections, or create new connections for a service, if the maximum connections per service limit has been reached for that particular service. The system can also maintain a parameter that keeps track of the total number of connections created to each shard of a sharded database. The connection pool can scan the sharded database topology, to determine which shard or sharded instance can satisfy the request, without exceeding the maximum limit for that shard.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for efficient connection validation. For example, the system can support a “seconds to trust idle connection” functionality, which enables lazy validation of connections in the connection pool. The seconds to trust idle connection is the time period, expressed, for example, as a number of seconds, within a particular connection usage, that the connection pool trusts that the connection is still viable, and if so will skip a connection validation test before delivering the connection to a requesting application.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for live addition of a tenant. When a pluggable database (PDB), for use by a tenant, is added to a multi-tenant database, it can generate an event to notify the connection pool. The connection pool environment consumes this PDB-add event, and dynamically configures a new tenant to access the shared pool. Since the new tenant addition is based on receipt of an event from the database, the connection pool does not require manual configuration for that tenant. Once a tenant is added, it can borrow connections from the pool in the same manner as existing tenants, and can also share existing pool properties, such as, for example a maximum pool size, or maximum number of connections per tenant.

Abstract: Described is a system, method, and computer program product is provided that implements high-volume data ingestion in a relational database system. A middle-tier structure is provided that sits between the IoT data producers and the back-end database system. Data records are gathered together and organized at the middle tier, and groups of those records are ingested on a group-basis into the database in a manner which bypasses standard SQL engine processing.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for server-side connection pool multiple tagging. For example, the system can provide a capability to associate multiple connection properties with a particular server-side connection in, e.g., an Oracle Database Resident Connection Pooling (DRCP) environment; look up a connection with one or multiple properties; and provide information about a returned connection so that a requesting application can review the properties associated with the returned connection, in order to determine how best to “fix-up” or otherwise use that connection.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for efficient connection validation. For example, the system can support a “seconds to trust idle connection” functionality, which enables lazy validation of connections in the connection pool. The seconds to trust idle connection is the time period, expressed, for example, as a number of seconds, within a particular connection usage, that the connection pool trusts that the connection is still viable, and if so will skip a connection validation test before delivering the connection to a requesting application.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for live addition of a tenant. When a pluggable database (PDB), for use by a tenant, is added to a multi-tenant database, it can generate an event to notify the connection pool. The connection pool environment consumes this PDB-add event, and dynamically configures a new tenant to access the shared pool. Since the new tenant addition is based on receipt of an event from the database, the connection pool does not require manual configuration for that tenant. Once a tenant is added, it can borrow connections from the pool in the same manner as existing tenants, and can also share existing pool properties, such as, for example a maximum pool size, or maximum number of connections per tenant.

Abstract: Described herein are systems and methods for providing access to a database in a multi-tenant environment, including the use of a connection pool, and support for limiting the maximum number of connections per tenant or per database shard. For example, when a tenant is associated with a service, configuring a maximum connections per service limit on a shared connection pool indicates to the system that the shared pool should not repurpose existing connections, or create new connections for a service, if the maximum connections per service limit has been reached for that particular service. The system can also maintain a parameter that keeps track of the total number of connections created to each shard of a sharded database. The connection pool can scan the sharded database topology, to determine which shard or sharded instance can satisfy the request, without exceeding the maximum limit for that shard.