Abstract: The subject technology identifies a change interval for a table. The subject technology determines a set of unregistered partitions and a set of registered partitions within the change interval. The subject technology identifies one or more partition lineage graphs (PLGs) connecting partitions in the set of unregistered partitions with partitions in the set of registered partitions. The subject technology determines a first set of changes from one or more PLGs. The subject technology determines a second set of changes from a set of remaining partitions in the set of unregistered partitions with partitions in the set of registered partitions. The subject technology consolidates the first set of changes determined from one or more PLGs and the second set of changes from the set of remaining partitions to generate a final set of changes for the table within the change interval.

Abstract: The subject technology receives a first query, the first query comprising a first set of statements, the first set of statements including at least a first statement for performing a first Data Manipulation Language (DML) operation on a first table, the first table included in a source file. The subject technology executes the first query, the executing including determining whether to perform a copy-on-write (CoW) process. subject technology performs a CoW fallback process. The subject technology performs the copy-on-write process for the first query based on a result of the CoW fallback process.

Abstract: The subject technology provides techniques for enabling hidden database objects, which in an example are utilized for testing and verifying new database objects against existing workloads. Hidden database objects are a mechanism for bridging that gap by running user workloads on user data in advance of exposing the feature to users. This mechanism allows placing a database object as a hidden object nested beneath a user's visible object (e.g., table, column, view, and the like). Hidden database objects can be used to verify the functionality, parity, performance, and correctness of new unreleased features.

Abstract: The subject technology provides techniques for enabling hidden database objects, which in an example are utilized for testing and verifying new database objects against existing workloads. Hidden database objects are a mechanism for bridging that gap by running user workloads on user data in advance of exposing the feature to users. This mechanism allows placing a database object as a hidden object nested beneath a user's visible object (e.g., table, column, view, and the like). Hidden database objects can be used to verify the functionality, parity, performance, and correctness of new unreleased features.

Abstract: Systems and methods that supply extensibility mechanisms for analysis services, via a plug-in component that enables additional functionalities. The plug-in component provide additional custom logic for the analysis services unified dimensional model (UDM). Accordingly, server functionalities can be extended in an agile manner, and without a requirement for a new release, for example.

Abstract: Systems and methods that supply extensibility mechanisms for analysis services, via a plug-in component that enables additional functionalities. The plug-in component provide additional custom logic for the analysis services unified dimensional model (UDM). Accordingly, server functionalities can be extended in an agile manner, and without a requirement for a new release, for example.