Abstract: In a multitenant database, one or more supporting data tables are used to write and store tenant data. Based on the contextual data returning an indication of validity of a detected database transaction, various actions are performed. Data changes may be captured if no valid context is found. At runtime, triggers are used to set a valid context or fix mode context, and database operations causing the data corruptions are captured in a change tracking data structure. The captured data from the database operations include a primary key and an original value for each data change. The original value and primary key for each data change is used to nullify the unintended write.

Abstract: Trigger-free asynchronous maintenance of custom indexes and skinny performance meta-structures is described. A database system receives a request to manipulate data in an object in a database table, and determines whether the object in the database table is associated with a user-based data structure. If the object in the database table is associated with the user-based data structure, the database system manipulates the data in the object in the database table and data in an object in an intermediate data table. The database system receives a query, and determines whether the query requests any data that is in the user-based data structure. If the query requests any data that is in the user-based data structure, the database system creates a query result by combining any data that is in the object in the intermediate data table with any requested data that is in the user-based data structure, and outputs the query result.

Abstract: A seed value assigned to a database table is determined. Numerically ordered invocation numbers are determined. Unordered pseudorandom numbers are generated based on the seed value and the invocation numbers to index temporally ordered data changes to the database table. It is determined whether the total number of yet-to-be-saved pseudorandom numbers reaches a maximum total number threshold. If so, the yet-to-be-saved pseudorandom numbers and a sequence of corresponding invocation numbers are saved in a sync table.

Abstract: A database query may be determined based on a database query definition. The database query definition may include a filter criterion that contains a wildcard match, which may include a first fixed portion and a second wildcard portion. The first fixed portion may include one or more combining characters. The database query may include a first query portion including a first canonical representation of the first fixed portion that omits the one or more characters. The database query may include a second query portion including a second canonical representation of the first fixed portion. The database query may be executed to select a result set that includes a plurality of query result values by applying the second query portion to filter values accessed by the first query portion.

Abstract: A seed value assigned to a database table is determined. Numerically ordered invocation numbers are determined. Unordered pseudorandom numbers are generated based on the seed value and the invocation numbers to index temporally ordered data changes to the database table. It is determined whether the total number of yet-to-be-saved pseudorandom numbers reaches a maximum total number threshold. If so, the yet-to-be-saved pseudorandom numbers and a sequence of corresponding invocation numbers are saved in a sync table.

Abstract: A plurality of database access requests are received at a database system within a designated database access scope. The plurality of database access requests may include a first request to read from a first database table and a second request to write to a second database table. The second request may occur during or after the receipt of the first request. A database access dependency rule linking the first database table and the second database table may be created. The database access dependency rule may impose a protected database access framework when executing a subsequent write request to the second database table when the first database table is updated. The protected database access framework may store one or more values associated with the subsequent write request in a staging table that are capable of being used to undo the subsequent write request.

Abstract: A request to update an original data value in a first row in a database table in a database system. An updated data value is written to a second row in a staging table in the database system. The updated data value corresponds with the original data value. The first row includes a database table key, which is also included in the second row. The original data value in the database table is replaced with a corresponding replacement value, which is determined based on a value replacement update function that takes as input the updated data value. The staging table maintains a record value for reversing the update to the database table.

Abstract: A database query may be determined based on a database query definition. The database query definition may include a filter criterion that contains a wildcard match, which may include a first fixed portion and a second wildcard portion. The first fixed portion may include one or more combining characters. The database query may include a first query portion including a first canonical representation of the first fixed portion that omits the one or more characters. The database query may include a second query portion including a second canonical representation of the first fixed portion. The database query may be executed to select a result set that includes a plurality of query result values by applying the second query portion to filter values accessed by the first query portion.

Abstract: A method, system, and apparatus provide for multiple custom fields associated with an application running at a computing device, where the multiple custom fields are received in a specified sort order. The method includes dynamically building multi-column indexes of the multiple custom fields corresponding to multiple intrinsic datatypes stored in multiple custom field columns of a shared table, where the multiple intrinsic datatypes are converted into a generic-indexable datatype to preserve the specified sort order. The method further includes building a sorted index in a specified order in a multi-column indexable table, where the multi-column indexable table includes a partial copy of data from multiple tenants that inhibit the shared table.

Abstract: Automated query tuning. A database query to be executed against a database is received. The database query is analyzed to determine one or more potential indexes to be evaluated. The one or more potential indexes are evaluated to determine if an optimization utilizing a selected potential index provides improved performance over performing the database query without the selected potential index. The one or more potential indexes are scored based on results of the evaluating. A recommendation of one or more of the potential indexes is provided to a source of the database query.

Abstract: A data table comprising one or more table columns including but not limited to an organization table column for identifying individual organizations, data entities and one or more table columns storing common-denominator data type values is accessed. Discriminant values and first native index values are generated by applying discriminant mappings and native index value mappings to table rows in the data table. A function-based table index using the discriminant values and the native index values is generated for the data table. The function-based table index is used for accessing at least a portion of data values in the data table.

Abstract: A query to retrieve database values for a first subset of table columns in a database table is determined. Runtime column selection variables are set up to identify the first subset of table columns for data retrieval, and are dynamically bound to a prepared query statement with single-column query statements joined by interstitial union operators. Each single-column query statement in the prepared query statement specifies a single-column query directed to a corresponding table column with a corresponding predicate to be bound at runtime dynamically with a corresponding portion of the one or more runtime column selection variables. The predicate is evaluated to be true or false in dependence on whether the corresponding table column is in the first subset of table columns. The prepared query statement is executed to retrieve database values for the first subset of table columns in the database table.

Abstract: Systems, methods, and computer-readable media for obtaining database records during an index update process are described. A database system may identify indexes having a first data format to be converted into a second data format, and obtain a first query for retrieval of a set of records in a database. The first query may comprise a filter to be used for retrieval of the set of records. The database system may convert the filter into the first data format to obtain a first filter value, convert the filter into the second data format to obtain a second filter value, and generate a second query to include the first data format filter and the second data format filter. The database system may issue the second query to obtain the set of records. Other embodiments may be described and/or claimed.

Abstract: A database entry may be stored in a container in a database table corresponding with a partition key. The partition key may be determined by applying one or more partition rules to one or more data values associated with the database entry. The database entry may be an instance of one of a plurality of data object definitions associated with database entries in the database. Each of the data object definitions may identify a respective one or more data fields included within an instance of the data object definition.

Abstract: A database entry may be stored in a container in a database table corresponding with a partition key. The partition key may be determined by applying one or more partition rules to one or more data values associated with the database entry. The database entry may be an instance of one of a plurality of data object definitions associated with database entries in the database. Each of the data object definitions may identify a respective one or more data fields included within an instance of the data object definition.

Abstract: A database entry may be stored in a container in a database table corresponding with a partition key. The partition key may be determined by applying one or more partition rules to one or more data values associated with the database entry. The database entry may be an instance of one of a plurality of data object definitions associated with database entries in the database. Each of the data object definitions may identify a respective one or more data fields included within an instance of the data object definition.

Abstract: A query to retrieve database values for a first subset of table columns in a database table is determined. Runtime column selection variables are set up to identify the first subset of table columns for data retrieval, and are dynamically bound to a prepared query statement with single-column query statements joined by interstitial union operators. Each single-column query statement in the prepared query statement specifies a single-column query directed to a corresponding table column with a corresponding predicate to be bound at runtime dynamically with a corresponding portion of the one or more runtime column selection variables. The predicate is evaluated to be true or false in dependence on whether the corresponding table column is in the first subset of table columns. The prepared query statement is executed to retrieve database values for the first subset of table columns in the database table.

Abstract: A method for processing database package connections and updates has been developed. First, an execution request for a database package is received. A connection context is then established which can execute the execution request. The database package is determined whether or not it is valid with proper package updates prior to establishing the connection. If the database package is determined to not be valid, change packages are retrieved for the database package. The valid change packages are then compiled for the database package and the connection request is executed for the updated database package with the connection context.

Abstract: Described are mechanisms for creating and utilizing a specialized index to improve the efficiency of various types of leading wildcard searches without having to unduly burden the system with write requests. The mechanisms may identify particular fields to be included in one or more types of specialized indexes that are accessed in response to particular types of wildcard queries including various combinations of leading, trailing, and intermediate wildcard operators. In addition, the mechanism may perform various pre-processing by an application when creating such indexes to conserve resources of an underlying database system. The mechanisms may also execute such wildcard queries in a manner that appears to be synchronous to a user while maintaining such indexes asynchronously for efficiency purposes.

Abstract: In a multitenant database, one or more supporting data tables are used to write and store tenant data. Based on the contextual data returning an indication of validity of a detected database transaction, various actions are performed. Data changes may be captured if no valid context is found. At runtime, triggers are used to set a valid context or fix mode context, and database operations causing the data corruptions are captured in a change tracking data structure. The captured data from the database operations include a primary key and an original value for each data change. The original value and primary key for each data change is used to nullify the unintended write.