The most visible limitation of the relational model has been its inability to handle multimedia files, but the importance of this has been overstated. In fact, the relational model has some far more significant limitations that have not yet been challenged:2. To Laugh or Cry?
Every new relational application needs a new set of programs developed from scratch, which is labour-intensive, expensive and wasteful.
Relational applications cannot be readily tailored to the needs of large numbers of individual users, which is an issue for ASPs.
Relational applications cannot record a piece of information about an individual thing that is not relevant to every other thing of the same type. This limits our ability to continually improve customer service levels.
Information about identical things in the real world is structured differently in every relational database, so it is difficult and expensive to amalgamate two databases."
--Simon Williams, The Associative Data Model
Rare Alan Turing journal shows his genius at work"
It's clear that fundamental logic is at the heart of computer science and everything we do--and in that sense it's clear the whole field owes Turing so very much" ... But in a sense, it also shows how far we've come."
Including away from logic.
GE: The future in data modeling is Object Role Modeling (ORM). It is a far superior way to approach data modeling (compared to any record-based methods such as relational) that avoids all the pitfalls of "Table Think" and the necessity of normalization.
Big data or any other kind of data--you still need to know your data and what it represents. That is the myth in big data--that you don't need a schema, i.e., knowledge of what the data means. True you may not need a SQL schema in Oracle, but you do need to know your data. You need to have names for things (that is the vocabulary) and their relationships.
I was wondering what people were using and what people would recommend as a good data modelling application? I guess I want to do two things - one reverse engineer existing databases into an ER diagram, as well as start from scratch and design a new conceptual/logical/physical data model. Any suggestions?
--LinkedIn.com
Just Give Me the Factless Facts, Ma'am
42% of Database Specialists Struggle to Manage NoSQL Solutions
Test shows big data text analysis inconsistent, inaccurate
The First Normal Form in Theory and Practice Part I
I like a GUID as a primary key on every table so that I can uniquely identify that row. For consistency I'll call it "UID" and defined as a NewSequentialID. I'm aware of the various discussions that have been had regarding Guids vs sequences vs COMB etc., etc., but for me any performance issues have occurred in the size of databases I've worked with. The ability to create a new UID as part of an insert is of huge benefit to reduce round trips if you're handling that kind of thing from within a business layer outside of the database server. --LinkedIn.com
Data Principles
Comments on Relational Fidelity & Analytics Integrity
Comments on Data Model: Neither Conceptual, Nor Logical, Nor Physical Model
Thou shalt not commit logical fallacies
The future in data modeling is Object Role Modeling (ORM). It is a far superior way to approach data modeling (compared to any record-based methods such as relational) that avoids all the pitfalls of "Table Think" and the necessity of normalization. --LinkedIn.com2. To Laugh or Cry?
Types of database management system and their evolution3. Online debunkings
Big Data is Dead!5. And now for something completely different
