The document discusses the dilemmas of data management, focusing on the trade-offs between size and complexity in relational and entity-relationship data models. It emphasizes that while the relational approach prioritizes speed and size, the entity-relationship model offers better management of complexity. Ultimately, it concludes that both models have their strengths, with Metasafe serving as a multifunctional system adaptable to various needs.

1. SIZECOMPLEXITY
DATA MANAGEMENT DILEMMA
www.Metasafe-Repository.com

2. COMPLEXITY
SIZE versus COMPLEXITY
ER
Entity-Relationship
SIZESIZE
RELATIONAL
Tables/Cols
RELATIONAL
Tables/Cols

3. COMPLEXITY
SIZE versus COMPLEXITYONE «data approach» does not fit ALL:
Both … HIGH RISK
?
ER
Entity-Relationship
Complexity is priority:
Entity-Relationship is king
SIZE
RELATIONAL
Tables/Cols
SIZE is priority:
RELATIONAL is king
RELATIONAL
Tables/Cols

4. Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Model Editor
Designer
The «Relational» Approach for large Applications
ENTITY-RELATIONSHIP
DATA MODEL

5. Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Model Editor
Designer
The «Relational» Approach for large Applications
Table-B
Columns
RELATIONAL
DATABASE
Management
System
(DBMS)
SQL-Query
Language
STORAGE
Table-A
Columns
Tables - Columns
Map Physical Storage
(Buffers, Disks, Sectors…)
GAP
ENTITY-RELATIONSHIP
DATA MODEL
RELATIONAL
DATABASE MODEL

6. Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Model Editor
Designer
The «Relational» Approach for large Applications
Optimizes for Speed and Size at the Expense of Complexity
Table-B
Columns
RELATIONAL
DATABASE
Management
System
(DBMS)
SQL-Query
Language
STORAGE
Table-A
Columns
Tables - Columns
Map Physical Storage
(Buffers, Disks, Sectors…)
GAP
MODEL is
ENTITY-RELATIONSHIP
IMPLEMENTATION is
RELATIONAL
STEP (1) Create DataModel
to deal with Complexity
Step (2) CONVERT
DataModel to RELATIONAL
Optimize for Speed/Size
Browser
Data Editor
Import/Export
XLS, XML, PDF
(3) Develop TOOLS

7. Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Model Editor
Designer
The «Relational» Approach for large Applications
Browser
Data Editor
Import/Export
XLS, XML, PDF
(3)DevelopTOOLS
Optimized for Speed and Size at the Expense of Complexity
Over Time DataModel OBSOLETE
Table-B
Columns
RELATIONAL
DATABASE
Management
System
(DBMS)
SQL-Query
Language
STORAGE
Table-A
Columns
Tables - Columns
Map Physical Storage
(Buffers, Disks, Sectors…)
- Model not tested / obsolete
- Structure GAP to DB
+ Speed, Size optimized

8. Metasafe – The “Entity-Relationship” Approach
Entity-A
Attributes
Entity-B
Attributes
Bi-directional
Relationships
Attributes
ER-
DATABASE
Management
System
(DBMS)
Java API
Framework
Model Editor
Designer
Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Java API / Framework
Access to Model
Access to Data

9. Metasafe – The “Entity-Relationship” Approach
Entity-A
Attributes
Entity-B
Attributes
Bi-directional
Relationships
Attributes
ER-
DATABASE
Management
System
(DBMS)
Java API
Framework
Model Editor
Designer
Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Automatic Mapping
Model and Data
are always in sync

10. Metasafe – The “Entity-Relationship” Approach
ACCESS-RIGHTS
TRANSACTIONS
Entity-A
Attributes
Entity-B
Attributes
Bi-directional
Relationships
Attributes
ER-
DATABASE
Management
System
(DBMS)erSQL-Query
Language
Java API
Framework
Browser
Data Editor
->Eclipse
Import/Export
XLS, XML, PDF
XML/FO, BIRT
Model Editor
Designer
Types
Properities
Bi-directional
Relationships
Properties
DATA
MODEL Types
Properities
Access Rights + Transactions
Multi-UserAccess

11. Graphical
Query-Editor
QUERY
Execute
Runtime
Flexible Reporting with the erSQL Query Language
Point&Click - Query-Editor
from DataModel to Query
in easy steps
Query extracts structured
Data and Metadata

12. Graphical
Query-Editor
QUERY
Execute
Runtime
BIRT
Reporting
Structured
Formatted
PDF-File
Output to Excel
Output to XML..
Flexible Reporting with the erSQL Query Language
Graphical Output
Advanced Output
Integration with BIRT*)
Business Intelligent and Reporting Tool

13. Conclusion – ONE is not for ALL
Metasafe – ENTITY-RELATIONSHIP
- Newcomer, No large Customerbase, physical Constraints (SIZE)
+ DataModels tested, in Sync with DataBase, Basic Tool Set integrated
+ Open / Controlled Access with powerful API and erSQL-Query
> optimal 4 Development Prototypes and Applications with up to XX GB
Standard - RELATIONAL
- Large ECO-System of DBMSs and Tools available
- DataModel becomes obsolete, Difficulty with complex Data
+ DataBaseModel can be adapted to phsical Constraints
> optimal 4 large Applications where SIZE and SPEED are Priority
Conclusion –> Both

14. Metasafe delivers – an integrated multifunctional SYSTEM
Get started –> info@Metasafe-Repository.com