Abstract: Embodiments are directed to defining a query expression over a dynamic system model and to transforming a dynamically built query expression into a simplified, canonical form. A computer system receives various user inputs that are to be included as part of a query expression for querying a dynamic system model. The dynamic system model is queryable to determine features provided by a service hosted by a back-end server. The computer system dynamically builds the query expression based on both the received inputs and the available features provided by the service as indicated by the dynamic system model. The query expression also includes metadata structures representing those features of the service which are provided by the service. The computer system also queries across the dynamic system model using the dynamically built query expression to retrieve and provide the service features requested in the received user input.

Abstract: Embodiments are directed to implementing a dynamically changeable system model that is customizable per version, programmatically generating system models at runtime and to extending a programmatically generated system model. In an embodiment, a computer system determines that a dynamically changeable system model corresponds to a managed system. The dynamically changeable system model includes various managed system objects. The computer system indicates for the dynamically changeable system model which managed system objects are available in each version of the managed system. The available managed system objects are stored in a data store of the dynamically changeable system model.

Abstract: Embodiments are directed to defining a query expression over a dynamic system model and to transforming a dynamically built query expression into a simplified, canonical form. A computer system receives various user inputs that are to be included as part of a query expression for querying a dynamic system model. The dynamic system model is queryable to determine features provided by a service hosted by a back-end server. The computer system dynamically builds the query expression based on both the received inputs and the available features provided by the service as indicated by the dynamic system model. The query expression also includes metadata structures representing those features of the service which are provided by the service. The computer system also queries across the dynamic system model using the dynamically built query expression to retrieve and provide the service features requested in the received user input.

Abstract: Embodiments are directed to implementing a dynamically changeable system model that is customizable per version, programmatically generating system models at runtime and to extending a programmatically generated system model. In an embodiment, a computer system determines that a dynamically changeable system model corresponds to a managed system. The dynamically changeable system model includes various managed system objects. The computer system indicates for the dynamically changeable system model which managed system objects are available in each version of the managed system. The available managed system objects are stored in a data store of the dynamically changeable system model.

Abstract: Embodiments are directed to combining service operations with various managed system objects to form a new dynamic programming interface combination and determining valid dynamic programming interface combinations. A computer system determines which service operations are offered by a selected managed system. The selected managed system is configured to provide various services comprising multiple different service operations. The computer system determines that managed system objects of the managed system are to be combined with at least one of the service operations. The computer system also combines the service operation with the managed system object, so that a new dynamic programming interface combination is created. The new dynamic programming interface combination is configured for use by the services offered by the managed system.

Abstract: System performance data and program performance data may be collected, converted into the same format and correlated by time. A graph or other display of system performance data over a time period may be displayed. A bar may be superimposed on the graph. A corresponding grid or other display, of program performance data over the same time period may be displayed. An item or line of the grid corresponding to a program event at a particular timepoint may be selected. A timepoint in the system performance graph may be selected by adjusting the position of the bar superimposed on the system performance graph. In response to the movement of the bar, the portion of the grid of program performance data displayed may be changed so that the grid of program performance data displays program performance data corresponding to the selected timepoint in the system performance graph.

Abstract: An automated database tuning tool may include a user interface component and a tuning engine. The user interface may be a graphical component that interfaces with a user to collect configuration parameters for a tuning session for a specified database. The configuration parameters may be stored in a tuning database. A tuning engine that performs the actual tuning process may generate physical design recommendations and reports. The recommendations and reports may be stored in the tuning database, enabling the tuning tool to be run off-line or in background. Communication between components of the tuning tool may occur via stored procedures.

Abstract: Internal communications within components of an automated physical database design tool may be conducted in a data description language such as XML. Inputs to and outputs from the automated physical database design tool may also be presented in the data description language (e.g., XML). The communications, inputs and outputs may comply with a schema for the data description language. The schema may be written in a schema language such as XSD. Inputs presented in the data description language may comprise tuning options. Outputs may comprise a proposed physical design for a database and reports.

Abstract: An automated physical database design tool may provide an integrated physical design recommendation for horizontal partitioning, indexes and indexed views, all three features being tuned together (in concert). Manageability requirements may be specified when optimizing for performance. User-specified configuration may enable the specification of a partial physical design without materialization of the physical design. The tuning process may be performed for a production server but may be conducted substantially on a test server. Secondary indexes may be suggested for XML columns. Tuning of a database may be invoked by any owner of a database. Usage of objects may be evaluated and a recommendation for dropping unused objects may be issued. Reports may be provided concerning the count and percentage of queries in the workload that reference a particular database, and/or the count and percentage of queries in the workload that reference a particular table or column.

Abstract: System performance data and program performance data may be collected, converted into the same format and correlated by time. A graph or other display of system performance data over a time period may be displayed. A bar may be superimposed on the graph. A corresponding grid or other display, of program performance data over the same time period may be displayed. An item or line of the grid corresponding to a program event at a particular timepoint may be selected. A timepoint in the system performance graph may be selected by adjusting the position of the bar superimposed on the system performance graph. In response to the movement of the bar, the portion of the grid of program performance data displayed may be changed so that the grid of program performance data displays program performance data corresponding to the selected timepoint in the system performance graph.