Download Guidelines for database impact analysis

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Oracle Database wikipedia , lookup

Database wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Clusterpoint wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Ingres (database) wikipedia , lookup

Object-relational impedance mismatch wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

Relational model wikipedia , lookup

Database model wikipedia , lookup

Transcript
Guidelines for Database Impact Analysis – PROXY_TABLE_USAGE
Table: PROXY_TABLE_USAGE
Purpose:
This table shows dependency between Ministry corporate applications and physical
database tables, for standard Oracle based applications. The intent is for use in impact
analysis of database table changes.
Structure:
Column Name
-----------------------APPLICATION_ACRONYM
TABLE_NAME
SELECT_IND
INSERT_IND
UPDATE_IND
DELETE_IND
FOREIGN_KEY_IND
UPDATE_TIMESTAMP
Null?
-------NOT NULL
NOT NULL
Type
------------VARCHAR2(30)
VARCHAR2(30)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
VARCHAR2(1)
DATE
APPLICATION_ACRONYM is the application short name, assigned by IMB.
TABLE_NAME is the physical table name in the database.
UPDATE_TIMESTAMP is the timestamp when the row was entered/updated.
All other columns are currently empty, reserved for future use.
Limitations and Use:
The information in this table is based on Ministry standard web applications, that use the
common WebADE proxy connections to the corporate shared database. Other nonstandard applications may not show up in the list. Tables/applications not residing in the
corporate database are not included.
As mentioned, this list is not guaranteed 100% complete, however it’s pretty close. It is
an extremely good guideline to help determine the impact of changing a corporate
application table.
This table does not show what type of dependency exists – it could be a direct grant, it
could be a stored procedure, etc. The purpose of this table is to show that a dependency
exists, as a starting point to investigate further.
This table does not show foreign key dependencies (ie. physical table to table
dependencies). That information is currently held on the application data model.
However, this information may be added in future.
Example Queries:
1. Find all tables used touched by application FTA
select * from PROXY_TABLE_USAGE
where application_acronym = 'FTA'
order by table_name ;
2. Find all the applications that reference table CUT_BLOCK
select * from PROXY_TABLE_USAGE
where table_name = 'CUT_BLOCK'
order by application_acronym ;
Access to PROXY_TABLE_USAGE:
Access is granted upon request to DBAHELP. This table is part of a common query role
(IMG_TABLE_INQUIRY). It is assumed anyone asking already has an appropriate
Oracle account in place and is currently working on an existing application project. If
not, an approved request for an Oracle userid can be sent to SECURITY.