Regenerator REGENERATOR is the code generator for the RESOLUTION REPOSITORY database. Because REPOSITORY uses a rigorous object-orientated design methodology (Objective SQL), it is possible to automatically generate a very large proportion of the database code required for building and managing the REPOSITORY database. Benefits The benefits of the Regenerator are: Consistent database code for all database objects Complete set of views and stored procedures for all tables Database changes and customization can be done quickly and accurately Database objects can be sized to meet specific site requirements Database can be highly normalized for flexibility, while generated views and stored procedures present a simplified interface to end users and developers. Record level audit and access control structures can be applied to any table in the database based on client security requirements. Capabilities REGENERATOR is a custom tool which takes the schema defined in a database and generates the following database objects: Core Database Objects: CLUSTERS TABLES INDICES - unique & non-unique CONSTRAINTS - primary, foreign & field level TRIGGERS		Search this site: PRODUCTS Repository Reevaluator Regenerator Reloader Relayer List of Interfaces Real-Time APIs STEPCtrl XMLCtrl Resolver for Windows Window Applets Reviewer VB Scripting Reconciler RISnet for Web Management View Flexible Navigation Forms Generation Web Services Reports Resolutions Project Services

The following stored procedures and views are created for every table in the database: Stored Procedures: <table>_NW: A stored procedure that creates a new record in the table. If requested by the mode of the procedure, the corresponding foreign key table records will also be created if they do not exist. <table>_UP: A stored procedure that updates the contents of the record in the table. If required this procedure will cascade up to modify contents of superset tables. <table>_DL: A stored procedure that deletes the record identified by key values supplied as parameters. If required, this procedure will cascade down and delete any dependent foreign keys. <table>_RI: A stored procedure that checks the existence of records in the table with the combination of fields provided as arguments to the procedure. <table>_CO: A stored procedure that changes ownership of records in the table. (See audit and access control) <table>_DP: A stored procedure that duplicates records in the table based on any combination of input fields. <table>_VA: A stored procedure that provides for custom validation code to be added. Views: <table>_VT: A view that returns only the records in the table that the user is allowed to see. <table>_VN: A view that returns only the records in the table that the user is allowed to see along with any attributes from superset tables. <table>_VQ: A view that returns appropriate subsets of database resources for display in a hierarchy. <table>_VU: A view that returns the set of primary key combinations that could possible exist in a table but are not currently in the table. Database Sizing Prior to any RESOLUTION database build, a questionnaire is filled out defining approximate numbers for equipment items, documents, units, plans, schedules etc. From these answers detailed table and index sizing factors are created. This is reviewed with the site Database Administrator. Disk assignments are made balancing load and storage requirements. The database is then built accurately sized to meet specific client needs. Record Level Audit and Access Control A feature of the RESOLUTION database is that record level access and audit control structures can be applied to any table in the database according to client security needs. This is done at build time but can also be added later as needs arise. Any combination of the following access and audit control features can be added to any table: AUDIT - When the record was changed and by whom. HISTORY - Historical timestamped record of all changes. Allows reconstruction of the state of the database at any time. OWNERSHIP - Record level ownership by security group. Only members of the group, or groups that have been granted privileges, can access the record.

	Copyright 2003, Resolution Integration Solutions, Inc. Web Design & Development by