Abstract: A business intelligence (BI) server is described that supports data and schemas stored in multiple languages. The BI server implements a lookup table and lookup function that allows users to work with queries in different languages. When the user logs in, a session object is created for the user, which maintains the state information. A session variable specifies the language currently being used by the user. The BI server can inspect this session variable to determine the language of the user and perform the lookup translations as necessary. For example, if the language used by the session is different from the language of the base table storing the necessary information, the BI server can perform a translation by invoking a lookup function. The execution of the lookup can include performing a join operation of the base table with the lookup table to yield a translated value requested by the query.

Abstract: An administration tool can be used to provide data flexibility in a business intelligence (BI) server that is associated with a data warehouse. The administration tool can display one or more data objects that are adapted to be imported from an application framework into a physical model maintained on the BI server. The administration tool can further map the one or more data objects in the physical model into a logical model, also maintained on the BI server, which corresponds to at least one target table in the data warehouse. Additionally, the administration tool can publish an extension input to an extender associated with the data warehouse based on the logical model, wherein the extender operates to generate one or more metadata extensions based on the extension input.

Abstract: A scorecard application can support business strategy management using a business intelligence (BI) server. The BI server can take inputs from different data sources. The scorecard application can define an internal data structure that holds a plurality of strategy components and one or more key performance indicators (KPIs). Then, the scorecard application can populate each said strategy component in the internal data structure based on the inputs from the different data sources, and perform one or more actions once an alert is triggered, wherein the alert is triggered when a said KPI meets one or more criteria.

Abstract: A business intelligence (BI) server and repository are described which support a set of customized and/or calculated data members. In accordance with an embodiment, the BI server maintains a connection to a plurality of data sources which may store a set of dimension members. The data source can be relational, file storage based, multidimensional and other types. In accordance with an embodiment, the BI server can accept queries from the user that contain calculated members as a parameter. The calculated member is defined by an expression including multiple dimension members and one or more arithmetic operators. The BI server can parse and validate the query and rewrite the query for the data source. After the query is rewritten and optimized, it is executed against the data source and a set of results is received.

Abstract: A business intelligence (BI) server maintains a plurality of metadata objects to support the extract, transform and load (ETL) processes. These metadata objects includes a transparent view object, which takes a joined set of source tables and represents a data shape of the joined set of source tables using a transformation, and a ETL mapping association object that maps the transformation contained in the transparent view object to a target table. The BI server can then orchestrate the movement of data from source systems into the target data warehouses in a source and target system agnostic way.

Abstract: An extender associated with a data warehouse can support metadata extension for the data warehouse. The extender can create an ETL extension plan for extending the data warehouse. The ETL extension plan includes one or more ETL plan elements that indicate extensions on ETL metadata objects. The one or more ETL plan elements within the ETL extension plan can be ordered, and ETL metadata extension can be performed based on the ETL extension plan.

Abstract: An input extension specification can be generated, via an administration tool on a business intelligence (BI) server, for an extender associated with a data warehouse in order to extend the data warehouse. The administration tool can request for data flow information of the data warehouse from the extender. The data flow information indicates the mapping relationship between one or more source data objects and one or more target tables in the data warehouse. The administration tool further allows a user to select said one or more target tables in the data warehouse to be extended based on the data flow information, and builds the input extension specification for the extender.

Abstract: A method of partitioning a schema object containing Web server log file data that includes a plurality of dated entries. Existing partitions within the schema object are identified, as well as the date associated with each existing partition. Unique dates of the entries within the log file data are also identified. A separate partition within the schema object is then automatically created for a) each identified unique date of the entries within the log file data that is not associated with an identified existing partition, and for b) each date immediately preceding each date in a) unless the partition has previously been created. This method avoids splitting loaded partitions when the Web server log file data is loaded out of turn.

Abstract: A method of partitioning a schema object containing Web server log file data that includes a plurality of dated entries. Existing partitions within the schema object are identified, as well as the date associated with each existing partition. Unique dates of the entries within the log file data are also identified. A separate partition within the schema object is then automatically created for a) each identified unique date of the entries within the log file data that is not associated with an identified existing partition, and for b) each date immediately preceding each date in a) unless the partition has previously been created. This method avoids splitting loaded partitions when the Web server log file data is loaded out of turn.

Abstract: A method of optimizing an execution of a query on data may include steps of creating schema object(s) in a database schema, enable monitoring of the schema object(s) to monitor the amount of change of a predetermined characteristic of the schema object(s) over time and loading the data into the created schema object(s). It is then determined whether the amount of change of the predetermined characteristic exceeds a selectable threshold. Updated statistical information may be obtained only when the amount of change exceeds the threshold. The updated statistical information may then be provided to a query execution optimizer, which selects an execution plan based upon the updated statistical information when the amount of change exceeds the threshold or based upon previously provided statistical information when the amount of change does not exceed the threshold. The query may then be executed using the selected execution plan.