Abstract: A distributed computing system includes a memory storing execution state collected prior to an operator pause state. A controller modifies, during the operator pause state, characteristics of the distributed computing system. The controller invokes execution of the operator after the pause state such that the operator accesses the execution state to complete an operation.

Abstract: A computer readable storage medium with executable instructions specifies the execution of a state machine operating across a set of computing nodes in a distributed computing system. The executable instructions execute a set of operators, where the execution of each operator is under the control of a state machine that periodically invokes pause control states to pause the execution of an operator in response to a violation of a service level agreement specifying an operating condition threshold within the distributed computing system. Partitions of input data are formed that are worked on independently within the distributed computing system. A set of data batches associated with the input data is processed. Data partition control states to process the partitions associated with the set of data batches are specified. Key control states to process a set of keys associated with a data partition of the partitions are defined.

Abstract: Systems, methods, and other embodiments associated with hybrid optimization strategies in automatic SQL tuning are described. One example method includes receiving a first (e.g., cost-based) execution plan for a user structured query language statement (User SQL) from a first (e.g., cost-based) optimizer. The example method may also include receiving a second (e.g., rules-based) execution plan for the User SQL from a second, different (e.g., rules-based) query optimizer. The method may include identifying a preferred execution plan based on data produced by test executing the execution plans in a reproduced execution environment that reproduces at least a portion of an execution environment in which the user SQL runs. The method may also include controlling a database to execute the User SQL using the preferred execution plan.

Abstract: An X-ray tube anode target assembly (101) having a support shaft (107) connected to a pivot assembly (109) and a movable anode target (105) having a target surface (106) disposed at one end of the support shaft and a contact element (108) disposed at the opposite end of the support shaft. A first drive assembly (115) is operably arranged with respect to the support shaft to provide oscillatory motion to the anode target about a first axis substantially parallel to the support shaft and a drive cylinder (125) is operably arranged with respect to the contact element to provide a pivoting motion to the support shaft. A second drive assembly (127) is operably arranged with respect to the drive cylinder to provide an oscillatory motion to the drive cylinder, the second drive cylinder being further configured to provide a linear motion parallel to the first axis.

Abstract: A high flux X-ray tube anode target assembly (101). The assembly includes a support shaft (107) connected to a pivot assembly (109). The assembly further includes a movable anode target (105) having a target surface (106) disposed at one end of the support shaft. The target surface includes a single radius of curvature. The radius of curvature extends from a pivot point (110). The assembly also includes a drive member (119) operably arranged with respect to the support shaft to provide motion to the anode target. The assembly is configured to maintain a substantially fixed distance between the pivot point and the target surface.

Abstract: Systems, methods, and other embodiments associated with hybrid optimization strategies in automatic SQL tuning are described. One example method includes receiving a first (e.g., cost-based) execution plan for a user structured query language statement (User SQL) from a first (e.g., cost-based) optimizer. The example method may also include receiving a second (e.g., rules-based) execution plan for the User SQL from a second, different (e.g., rules-based) query optimizer. The method may include identifying a preferred execution plan based on data produced by test executing the execution plans in a reproduced execution environment that reproduces at least a portion of an execution environment in which the user SQL runs. The method may also include controlling a database to execute the User SQL using the preferred execution plan.

Abstract: An automated system that defines, implements and tracks the sales cycle applied by salespersons within an organization to sell goods or services offered by the organization to prospective customers. A graphical user interface displays a sales workflow that includes at least a plurality of pre-defined steps of the sales cycle, and automatically tracks a completion status of each of the pre-defined steps with respect to each sales opportunity being pursued by a salesperson. The system automatically tracks the completion status displayed by the graphical user-interface by tracking actions that the sales person has taken in furtherance of the sales opportunity using the graphical user-interface.

Abstract: A database system providing methodology for execution of functions in queries requesting data from markup language documents is described. In one embodiment, for example, a method is described for executing a function in a query requesting data from a markup language document stored in a database, the markup language document organized hierarchically into nodes, the method comprises steps of: receiving the query requesting data from the markup language document, the query including a function to be executed during execution of the query; determining nodes of the markup language document satisfying the query; deriving values of the nodes of the markup language document; and executing the function with the derived values and the nodes of the markup language document.

Abstract: A system providing methods enabling data in Extensible Markup Language (“XML”) format to be extracted, transformed and stored in a database, file system or main memory is described. The extraction and transformation process is generalized and can be used on various types of XML data, enabling XML data to be stored and queried using standard database query methodologies. The system includes parse-time functionality to transform XML documents into a structure having an interface that enables efficient access to the underlying data. The system also includes query execution-time functionality providing greater efficiency by bringing only the relevant portions of transformed XML data into memory in response to a query. The system parses and translates queries into a structure that can be executed without the need to write custom application-specific navigation code to search XML data. The system also enables original XML documents (or portions thereof) to be recomposed when required.

Abstract: A system providing methods enabling data in Extensible Markup Language (“XML”) format to be extracted, transformed and stored in a database, file system or main memory is described. The extraction and transformation process is generalized and can be used on various types of XML data, enabling XML data to be stored and queried using standard database query methodologies. The system includes parse-time functionality to transform XML documents into a structure having an interface that enables efficient access to the underlying data. The system also includes query execution-time functionality providing greater efficiency by bringing only the relevant portions of transformed XML data into memory in response to a query. The system parses and translates queries into a structure that can be executed without the need to write custom application-specific navigation code to search XML data. The system also enables original XML documents (or portions thereof) to be recomposed when required.