Database calculation engine

A system comprising:

• a database server comprising memory and at least one data processor;
• and an application server in communication with and remote from the database server comprising memory and at least one data processor;
• wherein:
• the database server receives, from the application server, a query associated with a calculation scenario, the calculation scenario being one of a plurality of calculation scenarios and defining a data flow model that includes one or more calculation nodes, each calculation node defining one or more operations to execute on the database server to respond to the query, at least one calculated node defining a calculated attribute;
• the database server instantiates the calculation scenario, wherein at least a portion of paths and/or attributes defined by the calculation scenario are not required to respond to the query, and instantiating the calculation scenario includes omitting the paths and attributes defined by the calculation scenario that are not required to respond to the query;
• the database server executes the operations defined by the calculation nodes of the instantiated calculation scenario to result in a data set responsive to the query;
• the database server provides the data set to the application server;
• and
• the calculation scenario being reusable, in whole or in part, across multiple different queries.

A non-transitory computer program product storing instructions, which when executed by at least one data processor forming part of at least one computing system, result in operations comprising:

• receiving data generated by an application server that comprises a query that specifies a calculation scenario, the specified calculation scenario being one of a plurality of calculation scenarios and defining a data flow model that includes one or more calculation nodes, each calculation node defining one or more operations to execute on the database server to respond to the query, at least one calculated node defining a calculated attribute;
• instantiating the specified calculation scenario in a calculating engine layer, the calculation engine layer interacting with a physical table pool and a logical layer, the physical table pool comprising physical tables containing data to be queried, and the logical layer defining a logical metamodel joining at least a portion of the physical tables in the physical table pool, wherein at least a portion of paths and/or attributes defined by the specified calculation scenario are not required to respond to the query, and instantiating the specified calculation scenario includes omitting the paths and attributes defined by the specified calculation scenario that are not required to respond to the query;
• executing the operations defined by the calculation nodes of the instantiated calculation scenario to result in a data set responsive to the query;
• and
• providing the data set to the application server.