1 / 6

Short Introduction to the RDBMS Software Redundancy Proposal

Short Introduction to the RDBMS Software Redundancy Proposal. PROBLEM / GOAL: avoid any loosing of up-time service of an application using either commercial or non-commercial databases due to yet uncovered and undiscovered bugs in database middleware.

tien
Download Presentation

Short Introduction to the RDBMS Software Redundancy Proposal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Short Introduction to theRDBMS Software RedundancyProposal PROBLEM / GOAL: avoid any loosing of up-time service of an application using either commercial or non-commercial databases due to yet uncovered and undiscovered bugs in database middleware. PROPOSED SOLUTION: Do make use of a redundant approach in the use of the database middleware by diversifying databases, schemas in the databases, relational or non relational data models, or using explicitly modifiers of any kind to SQL statements. The “Multiple Paths” model is proposed: do use multiple different paths and algorithms to access the very same data beneath them all.

  2. Schema 1. Oracle 11g Handler Solution A: multiple databases paths Handler Schema 2. MS SQL Server 2008 Databases Pool DB Pool Managers (N managers) Schema 3. IBM DB2 Handler Application Application Schema 4. Ingres, PostgreSQL, etc… Handler Schema 5. Flat Files Data Model (Critical data access path) Handler

  3. Handler Schema 1. Full Relational Data Model Solution B: multiple access paths e.g. in Oracle Handler Schema 2. “Snow-Flake” Data Model (Partially Denormalized) Handler Schema 3. “Star” Data Model (Completely Denormalized) Oracle DB Pool Managers (N managers) Application Handler Schema 4. “Multi-dimensional” Data Model (DWH non relational alike) Handler Schema 5. Oracle Object-Oriented Relational Data Model (i.e. Oracle “Types”) Schema 5. Flat Files Data Model (Critical data access path) Handler

  4. Solution C: e.g. multiple Oracle statements paths • It is a FACT that Oracle SQL statements may be modified by: • Choosing the optimizer: RULE, CHOOSE, ALL_ROWS, FIRST_ROWS, etc… • Using hints: /*+index …*/, /*+parallel …*/, etc… • Using Analytical functions instead of sub-queries • Using Semi-joins and Anti-joins instead of sub-queries • Using WITH clause • … other ways …

  5. Solution D: e.g. multiple paths via Oracle procedures • It is a FACT that Oracle SQL statements may be embedded in PLSQL code: • PLSQL is interpreted by DIANA, which is modeled following ADA. • In PLSQL procedures in a package you may use: • Embedded SQL Statements • Dynamically created views • TEMP Tables • Associative arrays and PLSQL (memory) Tables • Oracle Types • … etc etc …

  6. Henceforth: • Combining all of these observations, on average we have hundreds (100’s) of magic paths per statement • Attach a probability and a time-out to each path • Do compute explicitly for all paths, sum up contributions. • The Proposed Solution will have (minimally) the following features: • An abstract DataModel generator  The input DataModel is entered and checked and from it, iteratively if needed, the whole number of different “paths” is generated. • A software interface consisting of either the DBO (Dynamic Business Object) model (presented in the dbo.zip file) to represent data-types (intrinsic architecture) or a pre-compiler able to adapt to existing concrete objects and able to generate adapted concrete classes (extrinsic architecture). • A software interface consisting of the DB pool managers and handlers specific to commercial and non-commercial databases alike (as well as platforms).

More Related