Integrated execution of relational and non-relational calculation models by a database system

A method comprising:

• receiving, by a database server from a remote application server, a query that is associated with a calculation scenario that defines a data flow model that includes calculation nodes arranged in a hierarchy, a first subset of the calculation nodes performing operations on non-relational data and a second, different subset of the calculation nodes performing operations on relational data, the data flow model maintaining a format of the non-relational calculation nodes;
• optimizing, by a calculation engine model optimizer, the first subset of calculation nodes included in the complete calculation scenario;
• optimizing, by a relational database optimizer, the second subset of calculation nodes included in the complete calculation scenario, the relational database optimizer identifying the second subset of calculation nodes based at least on an indicator associated with each of the second subset of calculation nodes;
• executing, by the database server, the operations defined by the first subset of calculation nodes and the second subset of calculation nodes of the complete calculation scenario optimized by both the calculation engine model optimizer and the relational database optimizer to result in a responsive data set;
• and
• providing, by the database server to the application server, the data set.

A method comprising:

• receiving, by a database server from a remote application server, a query that is associated with a first calculation scenario, a second calculation scenario, and a third calculation scenario that each define a data flow model that includes one or more calculation nodes arranged in a hierarchy, the first calculation scenario and second calculation scenario each comprising non-relational calculation nodes performing operations on non-relational data and the third calculation scenario comprising relational calculation nodes performing operations on relational data;
• merging, by the database server, the first calculation scenario, the second calculation scenario, and the third calculation scenario into a complete calculation scenario, while maintaining a format of the non-relational calculation nodes, the complete calculation scenario comprising the non-relational calculation nodes and the relational calculation nodes;
• optimizing, by a calculation engine model optimizer, the non-relational calculation nodes included in the complete calculation scenario;
• optimizing, by a relational database optimizer, the relational calculation nodes included in the complete calculation scenario, the relational database optimizer identifying the relational calculation nodes based at least on an indicator associated with each of teh relational calculation nodes;
• executing, by the database server, the operations defined by the relational calculation nodes and the non-relational calculation nodes of the complete calculation scenario to result in a responsive data set;
• and
• providing, by the database server to the application server, the data set.