Abstract: A method and system for providing a computing device control interface are provided. A system administrator accesses a graphical user interface and selects a group of actions that are to be executed by a number of computing devices. The actions selected by the system administrator are embodied in a graphical action icon and displayed on the graphical user interface. The system administrator initiates the actions by manipulating the action icon such that it overlaps a computer icon, which embodies one or more computing devices within the network that will execute the selected actions. The computing device icon is also displayed on the user interface. The user interface executes the selected action on the selected computer and then generates an archive file embodying the execution of the selected actions on the selected group of computing devices.

Abstract: A method and system for providing a computing device control interface are provided. A system administrator accesses a graphical user interface and selects a group of actions that are to be executed by a number of computing devices. The actions selected by the system administrator are embodied in a graphical action icon and displayed on the graphical user interface. The system administrator initiates the actions by manipulating the action icon such that it overlaps a computer icon, which embodies one or more computing devices within the network that will execute the selected actions. The computing device icon is also displayed on the user interface. The user interface executes the selected action on the selected computer and then generates an archive file embodying the execution of the selected actions on the selected group of computing devices.

Abstract: A method and system for providing a computing device control interface are provided. A system administrator accesses a graphical user interface and selects a group of actions that are to be executed by a number of computing devices. The actions selected by the system administrator are embodied in a graphical action icon and displayed on the graphical user interface. The system administrator initiates the actions by manipulating the action icon such that it overlaps a computer icon, which embodies one or more computing devices within the network that will execute the selected actions. The computing device icon is also displayed on the user interface. The user interface executes the selected action on the selected computer and then generates an archive file embodying the execution of the selected actions on the selected group of computing devices.

Abstract: Described is a method, system and data structures to logically separate the notations from the semantics of model element objects into separate code components, and to enable subsequent re-association of a selected notation with a selected semantic. Various notations and semantics from different providers may be combined. The invention may be implemented in a Visual Modeling Framework which defines the API set and/or interfaces to which the semantic and notation objects conform, and allows a notation and a semantic to be plugged into each other to create a model element, thereby allowing pluggable notations and pluggable semantics. A paradigm server may load a selected semantic and notation component, combine them, and present the combination to the framework as a model element. The paradigm server may be a pluggable component, having specialized knowledge for validating whether a semantic object can be used in a paradigm and combined with a notation.

Abstract: Described is a method and system providing a dynamic, live (active) surface and/or model elements to complement and enhance what is being modeled or visualized, enabling the addition of new features and functionality to visualization and modeling tools. A dynamic surface is accomplished by extending traditional HTML, rendering APIs and/or components to enable visualization and modeling functionality. The surface background and model elements may comprise HTML elements, and the surface can include a Web site. The model elements are HTML elements layered dynamically atop the surface, as the user interacts with them, and completed designs may be saved in a non-proprietary format, (e.g., HTML). The live surface bases its services on HTML rendering engine services, and further provides a visualization and modeling engine that wraps and extends the rendering engine through multiple interfaces.

Abstract: Described is a method and system that enables open, non-proprietary and extensible visualization and modeling tools by providing multiple-way negotiations between model element end points (nodes) and a connecting model element (arc). Based on these negotiations, a user is guided to make appropriate interconnections between model elements. A protocol is provided for intelligent model elements (objects) to communicate their information to one another, e.g., an arc communicates its capabilities and requirements to a node, and vice-versa, whereby the model element objects themselves decide whether they can interconnect, and if so, how they need to interconnect. The objects themselves enforce semantics and rules. According to the protocol, either object can reject the interconnection (break off the negotiation) with the other object if it determines it is not compatible with the other object, or is otherwise unable to connect to it.

Abstract: Described is a method and system providing a dynamic, live (active) surface and/or model elements to complement and enhance what is being modeled or visualized, enabling the addition of new features and functionality to visualization and modeling tools. A dynamic surface is accomplished by extending traditional HTML, rendering APIs and/or components to enable visualization and modeling functionality. The surface background and model elements may comprise HTML elements, and the surface can include a Web site. The model elements are HTML elements layered dynamically atop the surface, as the user interacts with them, and completed designs may be saved in a non-proprietary format, (e.g., HTML). The live surface bases its services on HTML rendering engine services, and further provides a visualization and modeling engine that wraps and extends the rendering engine through multiple interfaces.

Abstract: A user specifies one or more queries comprising a batch of SQL statements. Each query submitted is displayed and represented as a tree, with each operation in the execution plan for the query represented by a corresponding tree node. This representation intuitively conveys the DBMS execution strategy which would be used to process the queries. The tree nodes are displayed as icons, with a unique one of such icons corresponding respectively to each of the possible query operations. In addition, the computing cost of each operation (each node) as a percentage of overall query cost is displayed, as is the cost of each query as a percentage of the overall cost of the specified query batch. A user may select an operation (tree node) with a conventional mouse, whereupon a user interface will show more detailed cost statistics relating to the selected operation.

Abstract: A user specifies one or more queries comprising a batch of SQL statements. Each query submitted is displayed and represented as a tree, with each operation in the execution plan for the query represented by a corresponding tree node. This representation intuitively conveys the DBMS execution strategy which would be used to process the queries. The tree nodes are displayed as icons, with a unique one of such icons corresponding respectively to each of the possible query operations. In addition, the computing cost of each operation (each node) as a percentage of overall query cost is displayed, as is the cost of each query as a percentage of the overall cost of the specified query batch. A user may select an operation (tree node) with a conventional mouse, whereupon a user interface will show more detailed cost statistics relating to the selected operation.

Abstract: A method and system for providing a computing device control interface are provided. A system administrator accesses a graphical user interface and selects a group of actions that are to be executed by a number of computing devices. The actions selected by the system administrator are embodied in a graphical action icon and displayed on the graphical user interface. The system administrator initiates the actions by manipulating the action icon such that it overlaps a computer icon, which embodies one or more computing devices within the network that will execute the selected actions. The computing device icon is also displayed on the user interface. The user interface executes the selected action on the selected computer and then generates an archive file embodying the execution of the selected actions on the selected group of computing devices.

Abstract: Described is a method, system and data structures to logically separate the notations from the semantics of model element objects into separate code components, and to enable subsequent re-association of a selected notation with a selected semantic. Various notations and semantics from different providers may be combined. The invention may be implemented in a Visual Modeling Framework which defines the API set and/or interfaces to which the semantic and notation objects conform, and allows a notation and a semantic to be plugged into each other to create a model element, thereby allowing pluggable notations and pluggable semantics. A paradigm server may load a selected semantic and notation component, combine them, and present the combination to the framework as a model element. The paradigm server may be a pluggable component, having specialized knowledge for validating whether a semantic object can be used in a paradigm and combined with a notation.

Abstract: Described is a method and system providing a dynamic, live (active) surface and/or model elements to complement and enhance what is being modeled or visualized, enabling the addition of new features and functionality to visualization and modeling tools. A dynamic surface is accomplished by extending traditional HTML, rendering APIs and/or components to enable visualization and modeling functionality. The surface background and model elements may comprise HTML elements, and the surface can include a Web site. The model elements are HTML elements layered dynamically atop the surface, as the user interacts with them, and completed designs may be saved in a non-proprietary format, (e.g., HTML). The live surface bases its services on HTML rendering engine services, and further provides a visualization and modeling engine that wraps and extends the rendering engine through multiple interfaces.

Abstract: A system for tracking the lineage of data in a database. Data within the tables are tracked by attaching lineage information to the data, preferably, by adding a lineage identifier to each row in a table. Data that share a common lineage can be identified by virtue of sharing a common lineage identifier. The lineage identifier can then be used to trace the source of the data, i.e., data having a common identifier share a common history. Preferably, the lineage data type is an identifier that is universally unique and is optimized to provide little impact on the performance of the database. For example, by providing a sufficient size identifier to ensure its uniqueness while minimizing storage size. More preferably, the data lineage data type is a sixteen-byte number.

Abstract: A user specifies one or more queries comprising a batch of SQL statements. Each query submitted is displayed and represented as a tree, with each operation in the execution plan for the query represented by a corresponding tree node. This representation intuitively conveys the DBMS execution strategy which would be used to process the queries. The tree nodes are displayed as icons, with a unique one of such icons corresponding respectively to each of the possible query operations. In addition, the computing cost of each operation (each node) as a percentage of overall query cost is displayed, as is the cost of each query as a percentage of the overall cost of the specified query batch. A user may select an operation (tree node) with a conventional mouse, whereupon a user interface will show more detailed cost statistics relating to the selected operation.

Abstract: Described is a method and system that enables open, non-proprietary and extensible visualization and modeling tools by providing multiple-way negotiations between model element end points (nodes) and a connecting model element (arc). Based on these negotiations, a user is guided to make appropriate interconnections between model elements. A protocol is provided for intelligent model elements (objects) to communicate their information to one another, e.g., an arc communicates its capabilities and requirements to a node, and vice-versa, whereby the model element objects themselves decide whether they can interconnect, and if so, how they need to interconnect. The objects themselves enforce semantics and rules. According to the protocol, either object can reject the interconnection (break off the negotiation) with the other object if it determines it is not compatible with the other object, or is otherwise unable to connect to it.

Abstract: Described is a method and system for interacting with a modeling layout algorithm that enables incremental and interruptible automatic layout operations. A defined set of interfaces (e.g., of a COM object) are described for layout engines, and a modeling engine calls into these interfaces to start and stop the layout process, preserve and restore state information, and perform other functions. The layout engine, which is preferably a pluggable component, raises events through an interface with which it complies to indicate its progress, and to indicate when the engine may be safely interrupted. The modeling engine can call back into the layout engine to stop the layout if the user has requested that the layout be interrupted, providing interfaces to the layout engine for preserving and restoring its state, thereby enabling incremental layout operations that do not lose progress.

Abstract: A system for automatically generating table neighborhoods comprises a database designer which automatically generates a database diagram for a selected table. The database designer automatically compiles a set of tables having the desired relation to a selected table. The desired level of relation may be several levels removed from the selected table, in which case, the database designer searches multiple levels for tables to be included in the database diagram. Thereafter, the database designer gathers format data for the selected table and the set of tables having the desired relation to the selected table. Finally, the database designer displays the selected table, the tables in the set of tables having the desired relation to the selected table, and the relationships between these tables.

Abstract: A user specifies source data, optional transformations and defines a destination database, as well as its location. The user specification creates a package. A package consists of steps of associated tasks, with each step optionally having one or more precedence constraints. Execution of the package causes a data pump to import the user-specified data, conform the data in accordance with the user's definition of the destination database and export the data to that database. Processing occurs on a streaming, contiguous basis. As each row is pulled from source database into data pump, the user-defined transform is optionally applied and data lineage information is bound to the data.

Abstract: A system for tracking the lineage of data in a database. Data within the tables are tracked by attaching lineage information to the data, preferably, by adding a lineage identifier to each row in a table. Data that share a common lineage can be identified by virtue of sharing a common lineage identifier. The lineage identifier can then be used to trace the source of the data, i.e., data having a common identifier share a common history. Additionally, the lineage identifier can provide details about transformations undergone by the data. For example, the lineage identifier can act as a pointer to a detailed history files of operations that were performed on the data to transform it into its current form. Preferably, the lineage identifier tracks program modules as well as specific versions of the program modules that transformed the particular data under consideration.

Abstract: A method for interactive display of a graphical tree structure in a windowing environment. A tree control graphically represents hierarchical data. The user can separate a portion of a tree control at a node and create a new tree control for viewing and editing. Changes to a newly created tree control propagate through to related tree controls.