Abstract: A computer program file or a sequence of processing steps from an authoring environment of a data processing system is used to generate a graph including nodes representing the processing steps is generated. Unique identifiers (tags) are assigned to the nodes. One or more processing steps are optionally modified while preserving the original identifiers. If an error occurs during execution, error information is saved including the processing step that failed and data records that triggered the failure. The identifier of the failed processing step is attached to the error information. The error information is collected and processed. The collected error information is used to correlate the error to the failed processing step and to data records triggering the error using the identifier of the failed processing step recorded with the error information. The correlated error information indicates cause and location of the error.

Abstract: A computer program file or a sequence of processing steps from an authoring environment of a data processing system is used to generate a graph including nodes representing the processing steps is generated. Unique identifiers (tags) are assigned to the nodes. One or more processing steps are optionally modified while preserving the original identifiers. If an error occurs during execution, error information is saved including the processing step that failed and data records that triggered the failure. The identifier of the failed processing step is attached to the error information. The error information is collected and processed. The collected error information is used to correlate the error to the failed processing step and to data records triggering the error using the identifier of the failed processing step recorded with the error information. The correlated error information indicates cause and location of the error.

Abstract: A computer program file or a sequence of processing steps from an authoring environment of a data processing system is used to generate a graph including nodes representing the processing steps is generated. Unique identifiers (tags) are assigned to the nodes. One or more processing steps are optionally modified while preserving the original identifiers. If an error occurs during execution, error information is saved including the processing step that failed and data records that triggered the failure. The identifier of the failed processing step is attached to the error information. The error information is collected and processed. The collected error information is used to correlate the error to the failed processing step and to data records triggering the error using the identifier of the failed processing step recorded with the error information. The correlated error information indicates cause and location of the error.

Abstract: A computer program file or a sequence of processing steps from an authoring environment of a data processing system is used to generate a graph including nodes representing the processing steps is generated. Unique identifiers (tags) are assigned to the nodes. One or more processing steps are optionally modified while preserving the original identifiers. If an error occurs during execution, error information is saved including the processing step that failed and data records that triggered the failure. The identifier of the failed processing step is attached to the error information. The error information is collected and processed. The collected error information is used to correlate the error to the failed processing step and to data records triggering the error using the identifier of the failed processing step recorded with the error information. The correlated error information indicates cause and location of the error.

Abstract: An automatic task generation mechanism provides generation of tasks such as maintenance tasks for a computer system. A set of tasks is set up along with rules for performing the tasks. The rules may be associated with metadata that allow the tasks to be mapped to the tasks. Events may be detected that are related to database operations such as a create, modify, delete or add command. Upon event detection by the system, the system may store the event and associated metadata. Another process may query the event and metadata storage and compare those items to the rules previously set up. If there is a match between the rules and the event, one or more tasks may be established which correspond to an action that is desired to be taken. The task may then be inserted into a computer system for subsequent execution.

Abstract: Various technologies and techniques are disclosed that automatically optimize package execution performance. A profiling phase executes each task in a control flow package and measures performance metrics, such as task execution length, task memory usage, task correlation to CPU versus input/output operations, network bandwidth, and running applications. An optimization phase optimizes subsequent executions of the package by using the performance metrics to make appropriate adjustments to the package. The profiling phase and optimizing phase are repeated over a period of time as appropriate to improve the package's performance without requiring a user to make adjustments to the tasks in the package.

Abstract: A system and method for cloning objects by configuring a cloned object with properties of a shared object or of a properties collection for a demand event, and for unconfiguring the cloned object for a design event initiated on the cloned object. During a design event, the cloned object may point to or be associated with the shared object or properties collection. A design event performed on the cloned object may actually be performed on the shared object or properties collection with or without user knowledge. Additionally, an embodiment of the invention may allow for dynamic execution of the cloned object at demand time by altering a variable of a property expression.

Abstract: Best practice guidelines are integrated into the design of database applications so that it is less likely that inappropriate values are set. A proposed value for a database object may be compared to an archive of best practice guidelines. If the proposed value does not comply with best practice guidelines, a best practice recommendation may be provided, and an opportunity may be provided to change the proposed value to the recommended value before the database object is manipulated or the setting persisted.

Abstract: An automatic task generation mechanism provides generation of tasks such as maintenance tasks for a computer system. A set of tasks is set up along with rules for performing the tasks. The rules may be associated with metadata that allow the tasks to be mapped to the tasks. Events may be detected that are related to database operations such as a create, modify, delete or add command. Upon event detection by the system, the system may store the event and associated metadata. Another process may query the event and metadata storage and compare those items to the rules previously set up. If there is a match between the rules and the event, one or more tasks may be established which correspond to an action that is desired to be taken. The task may then be inserted into a computer system for subsequent execution.