Abstract: Disclosed herein are system, method, and computer program product embodiments for modular fragmentation and messaging across different web applications. An example system may include at least one computer processor, a memory, and a first database, the first database comprising a first procedure specification of at least one first procedure, and a first data field configured to store a data item, the first data field comprising a first logical link within a first data structure of the first database, the first logical link comprising a respective first set of first link specifications, and the first procedure being configured to retrieve the data item stored in the first data field upon execution by the processor. Semantic links between procedure specifications may be determined from matches with logical links. A linked data item stored in one field may be transferred to another field that has a matching logical link.

Abstract: Disclosed herein are system, method, and computer program product embodiments for modular fragmentation and messaging across different web applications. An example system may include at least one computer processor, a memory, and a first database, the first database comprising a first procedure specification of at least one first procedure, and a first data field configured to store a data item, the first data field comprising a first logical link within a first data structure of the first database, the first logical link comprising a respective first set of first link specifications, and the first procedure being configured to retrieve the data item stored in the first data field upon execution by the processor. Semantic links between procedure specifications may be determined from matches with logical links. A linked data item stored in one field may be transferred to another field that has a matching logical link.

Abstract: The invention relates to a tail stock device (10) for supporting a workpiece in a machine tool, for example a grinding machine. The tail stock device (10) comprises a tail stock arm (16) that is pivotally supported about a pivot axis (S), said tail stock arm having arranged on its outer end (16a) a centering tip (12) that is oriented parallel to the pivot axis (S). By means of a pivot drive (30) comprising a first pneumatic cylinder (31), the tail stock arm 16 can be pivoted between a working position (A) and a resting position (R). The movement of the piston (32) of the first pneumatic cylinder (31) is transmitted—via a first coupling arrangement (35)—to the tail stock arm (16).

Abstract: A computer system maintains a repository of software products. The software products include a plurality of business processes, and each business process includes a business object. The system maintains a plurality of archiving objects, and further maintains a mapping of each business process to at least one business object, a mapping of each business object to at least one related database table, and a mapping of each database table to at least one related archiving object. The system receives a selection of a business process for which data is to be archived, and uses the mapping of the each business process to the at least one business object, the mapping of the each business object to the at least one database table, and the mapping of the each database table to the at least one archiving object to determine the database tables to transmit to the archiving objects.

Abstract: A computer system determines a first criticality relating to frequency of execution of computer programs, a second criticality relating to frequency of execution of transactions, a third criticality relating to a number of users who execute the transactions, a fourth criticality relating to programs that modify the database tables having a large change in data, and a fifth criticality relating to the amount to time that each computer program is executed and the amount of time that each transaction is executed. The system determines intersections among the criticalities, and assigns a weighted value to each of the intersections. The system determines an overall criticality for a particular computer program or a particular transaction. The overall criticality is a function of the number of intersections in which the particular computer program or the particular transaction appears and the weighted values assigned to the intersections.

Abstract: Various embodiments illustrated and described herein pertain to at least one of systems, methods, databases, and instructions stored on computer-readable mediums for data allocation identification. One method according to some embodiments includes determining a database allocation of an entity and identifying a domain directly associated with the entity. The method may further include determining at least one header table field directly associated with the entity by identifying a directly associated type definition linked to the directly associated domain, wherein the directly associated type definition refers to the header table field, wherein each header table field is in a corresponding header table. This, and other embodiments, are illustrated and describe in detail herein.

Abstract: A computer system maintains a repository of software products. The software products include a plurality of business processes, and each business process includes a business object. The system maintains a plurality of archiving objects, and further maintains a mapping of each business process to at least one business object, a mapping of each business object to at least one related database table, and a mapping of each database table to at least one related archiving object. The system receives a selection of a business process for which data is to be archived, and uses the mapping of the each business process to the at least one business object, the mapping of the each business object to the at least one database table, and the mapping of the each database table to the at least one archiving object to determine the database tables to transmit to the archiving objects.

Abstract: A computer system determines a first criticality relating to frequency of execution of computer programs, a second criticality relating to frequency of execution of transactions, a third criticality relating to a number of users who execute the transactions, a fourth criticality relating to programs that modify the database tables having a large change in data, and a fifth criticality relating to the amount to time that each computer program is executed and the amount of time that each transaction is executed. The system determines intersections among the criticalities, and assigns a weighted value to each of the intersections. The system determines an overall criticality for a particular computer program or a particular transaction. The overall criticality is a function of the number of intersections in which the particular computer program or the particular transaction appears and the weighted values assigned to the intersections.

Abstract: Certain implementations provide systems, computer program products, computing devices, and methods to analyze how a preexisting database will be affected during a solution transition event (e.g., upgrading a database to a new version). Analysis can be conducted before the solution transition event has occurred. Analysis can yield a report detailing how upgrading will affect the data and data structures contained within a preexisting database system. The database system being analyzed can be part of a broader system upon which the solution transition event is performed. Analyzing how the solution transition event will affect a database system can be performed in preparation for performing the solution transition event on the broader system.

Abstract: Various embodiments illustrated and described herein pertain to at least one of systems, methods, databases, and instructions stored on computer-readable mediums for data allocation identification. One method according to some embodiments includes determining a database allocation of an entity and identifying a domain directly associated with the entity. The method may further include determining at least one header table field directly associated with the entity by identifying a directly associated type definition linked to the directly associated domain, wherein the directly associated type definition refers to the header table field, wherein each header table field is in a corresponding header table. This, and other embodiments, are illustrated and describe in detail herein.

Abstract: Certain implementations provide systems, computer program products, computing devices, and methods to analyze how a preexisting database will be affected during a solution transition event (e.g., upgrading a database to a new version). Analysis can be conducted before the solution transition event has occurred. Analysis can yield a report detailing how upgrading will affect the data and data structures contained within a preexisting database system. The database system being analyzed can be part of a broader system upon which the solution transition event is performed. Analyzing how the solution transition event will affect a database system can be performed in preparation for performing the solution transition event on the broader system.