Lattix LDM for Oracle
Architectural Governance for Oracle Databases
Large database implementations can consist of thousands of tables, views, stored procedures and a variety of other elements. To add to the complexity, all of these elements depend on each other in a variety of ways. None of the approaches in use today provide a way for database administrators and developers to visualize or understand these relationships effectively.
The Lightweight Dependency Model is the first approach which allow you to understand the architecture of your database system by taking all the elements of the database and their relationship into account. You can now get a precise big picture of how your database is organized. Not only that you can also formalize, communicate and control the architecture of your Oracle database so that it remains robust and modular.
- Look down a column to see the dependencies for each subsystem (element of the database).
- Decomposition hierarchy enables massive scalability.
- Aggregating dependencies by hierarchy creates a precise big picture view.
- Design rules allow precise specification of layering and componentization.
Discover and Analyze and the Architecture of your Database System
Create a Dependency Model by examing the dependencies between all objects of the database including schemas, tables, constraints, indexes, sequences, stored procedures, packages, types, java classes, synonyms etc. Create what-if and should be architectures to improve modularity and increase coupling. You can:
- Identify and group schemas for specific applications and those which provide common services.
- Identify schemas which are independent of each other.
- Layer schemas so that modularity of schemas is preserved.
- Refactor schemas which have become intertwined as a result of evolution.
- Determine how to move stored procs and packages to enhance modularity and reduce unnecessary coupling.
Control the Architecture
Specify design rules to prevent undesirable couplings. Here are just a few things that you can do with design rules:
- Minimize or prevent the coupling between schemas for different applications.
- Maintain the layering of schemas to prevent application schemas from mixing with schemas which provide platform data and services.
- If desired, allow data in schemas to be accessed through well defined synonyms and strored procedures.
Understand the Impact of Change
Understanding the dependencies between various elements of the database will improve your ability to understand how change affects the rest of the system. For example, you can:
- Get a list of what is affected when you change an element of the database such as a table or stored procedure
- Determine what needs to be tested when a change is made.
- Estimate the difficulty associated when a change change to the database is requested.
Reports
Lattix LDM supports a variety of reports to display and print:
- Export the DSM, Rules, Usage, Violations and Worklist to an Excel spread sheet.
- Export the DSM and conceptual architecture image to jpg files
- Generate and export the architectural metrics of your database design
Examine your own System
The most effective way to learn about this approach is to analyze your own database system. It is easy to understand and apply. You will end up with a much improved understanding of the architecture of your own database and understand what should be changed to improve the architecture and make the database more robust. You will also get a precise big picture view that is simple and intuitive and can easily be shared by a diverse group of stake holders such as managers, architects, developers and users.
Click here to download a trial version of Lattix LDM for Oracle