Saturday, April 18, 2015

Weekly Update



1. Quote of the Week
To clarify my point further, although M doesn't care about how it's implemented, the implementation has a strong influence on the logical structures that it's trying to implement. In a normalized or demoralized [sic] debate, a fully normalized physical schema is always good, when implemented on an infinite performance hardware. --LinkedIn.com

2. To Laugh or Cry?
I recently attended a presentation on Azure DocumentDB, Microsoft's NoSQL cloud product. I made the following notes:

  • Polyglot persistence: Wasn't this what the RDM was supposed to substitute? 
  • Hierarchy: Didn't we get rid of HDM decades ago?
  • NoSQL: No SQL, but a "SQL-like" language (it's barely relational and now it's used for documents?)
  • No integrity, data independence: Nothing learned from the past.
  • Cloud: At least mainframes were under each company's control.
Progress.

3. Online Debunkings

Comments on "Michael Stonebraker Explains Oracle’s Obsolescence, Facebook’s Enormous Challenge"
4. Interesting Elsewhere
Unskilled and Unaware of It
5. And now for something completely different

Wednesday, April 15, 2015

Class Business Rules and Table Constraints



My April post @All Analytics.

Aside from domain constraints, every R-table designed to represent a single class of entities is also subject to table constraints that approximate in the database class business rules in the real world. If the rules are not documented, for the conscientious analyst who wants to guarantee sensible data manipulation and result interpretation they are the next best thing.

Read it All. (Please comment there, not here)



 





Saturday, April 11, 2015

David McGoveran Interview



DBDebunk readers should know of David McGoveran (see his bibliography under FUNDAMENTALS), whose work on relational theory and practice has appeared or been discussed on the old site and here over the years. On more than one occasion I mentioned the Principle of Orthogonal Design (POOD) identified by David, who had published several years ago work he did on the subject with Chris Date. The POOD has relevance to updating relations and particularly views and led to Date's VIEW UPDATING AND RELATIONAL THEORY book .

I recently mentioned that David's and Date's understandings on POOD have diverged since their joint effort--currently Date and Darwen reject the POOD as formulated then and David has problems with Date's understanding of it and with their THE THIRD MANIFESTO (TTM) book.

David is working on a book tentatively titled LOGIC FOR SERIOUS DATABASE FOLKS where he will detail his views on RDM in general and POOD and view updating in particular, but in the meantime I asked him to publish an early draft of a chapter on the latter subject, which he did-- Can All Relations Be Updated?--and which he has just revised.

He has asked me to post a clarification on the nature of the differences with Date and Darwen (see next) and I used the opportunity to interview him about his impressive career, which covers much more than database management. David provided written answers to questions.


Saturday, April 4, 2015

Weekly Update



1. Quote of the Week
Hopefully with the emergence of better cloud infrastructure and unstructured databases, it'll become easier and easier to build utilities to handle the intake and transformation of big, messy datasets into units of info ready for insights. SocialScale (socialscale.io) just launched an MVP a month ago to provide instant access to raw social data (via Gnip), ready-for-analysis, in any tool. --LinkedIn.com

2. To Laugh or Cry?
Are SQL Relational DBMS's Here to Stay?

3. Online Debunkings

4. Interesting Elsewhere

5. And now for something completely different

Saturday, March 21, 2015

Weekly Update



1. Quote of the Week
I'm not sure why you think integrity constraints are purely logical. Primary keys are physical constraints. They enforce that the primary key remains unique. Here's an example of SQL that creates a physical foreign key constraint.
ALTER TABLE FactInventoryCollections
 ADD CONSTRAINT
  FK_FactInventoryCollections_ClientPK,
  FOREIGN KEY (ClientPK)
   REFERENCES ViewCubeDimClient(ClientPK);
Physical constraints allow the database engine to return an error if an operation attempts to insert a row that violates any defined constraints. --LinkedIn.com

2. To Laugh or Cry?
When One Data Model Just Won't Do: Polyglot Persistence

3. Online Debunkings

4. Interesting Elsewhere

David McGoveran has been working on a book tentatively titled LOGIC FOR SERIOUS DATABASE FOLKS intended to set some matters straight regarding the formal, set-theoretic and logic foundations of the RDM which have been misinterpreted. While he is not ready to publish yet, I asked and he agreed to post at his site a draft of a chapter on view updating which I consider a must read (together with the Introduction), particularly since it exposes the thinking behind the Principle of Orthogonal Design rejected by Date and Darwen.
David invites comments.


5. New Links

Added the following to the LINKS page:

6. And now for something completely different

Saturday, March 7, 2015

Weekly Update (UPDATED)




1. Quote of the Week
I have been in the data side of IT for quite some time now and have seen the evolution of how data is ingested, manipulated and regurgitated to the end users in hope of telling our consumers "how much of something did something". The main issue seems to be complexity of the data models and the fact we don't have a model that can expand with the data without adding tons of new schema. The solution.  --LinkedIn.com

2. To Laugh or Cry?

3. Online Debunkings

4. Interesting Elsewhere

5. And now for something completely different

Thursday, March 5, 2015

Domains, R-tables, and SQL



March blog post @All Analytics:

To ensure sensible results from and correct interpretations of analysis of data from SQL tables or extracts thereof, analysts must know the tables’ interpretation -- the business rules underlying them -- which is rarely documented.

They should be represented in the database by integrity constraints -- not perfect substitutes, because they are very loose approximations to the rules -- but if they are enforced in the database by the DBMS they are usually recorded either in the definition statements that created the tables and constraints, or the database catalog.

Read it all




Wednesday, February 25, 2015

SQLSaturday Presentation




March 28, 11:15,  Mountain View

MEANINGLESS, BUT CONSISTENT: DATABASE TRUTH VS. CORRECTNESS


You're a SQL Server ace: your ability to squeeze everything from SQL and your performance tuning skills are unparalleled, but do you know what your tables really mean and, therefore, what queries make sense and whether results are correct and their interpretations sensible? This is a critical part of data fundamentals, the grasp of which is poor. It is a subject usually neither much covered in education, nor part of job requirements and industry dialogue, yet can defeat the entire purpose of your DBMS expertise. This presentation covers
  • Meaning, business rules and table interpretations;
  • Types of business rule; 
  • Meaning and database truth; 
  • Business rules, integrity constraints and database consistency; 
  • DBMS and user reponsibilities.
Session Level: Intermediate

Event full details

Contact: Mark Ginnebaugh  mark@designmind.com




Saturday, February 21, 2015

Weekly Update




1. Quote of the Week
what is an index in database? how can it make the search faster? please help me understanding this. Project Manager Technical
--LinkedIn.com
Note the job title.


2. To Laugh or Cry?
Tableau Data Modeling Resolving Many to Many Relationship

3. Online debunkings
Comments on Codd's Marks are not SQL's NULLs

4. Interesting elsewhere

5. And now for something completely different 

Thursday, February 19, 2015

Understand Class Business Rules




My February post @All Analytics.

To apply manipulation that makes sense to data originating in database tables and interpret results correctly, the analyst must know the meaning of the table(s) -- the underlying business rules. For tables designed to represent facts about a single class of entities each, the analyst should expect two categories of rules: property rules (discussed last month) and class rules, of which there are several types.

Read it all. (Please comment there, not here)



 



Monday, February 16, 2015

Weekly Update




1. Quote of the Week
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:

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
2. To Laugh or Cry?

3. Online debunkings

4. Interesting elsewhere
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.

5. And now for something completely different

Sunday, February 15, 2015

The Conceptual-Logical Conflation and the Logical-Physical Confusion (UPDATED)




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.

Sunday, February 8, 2015

Weekly Update (UPDATED)




1. Quote of the Week
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

2. To Laugh or Cry?
Just Give Me the Factless Facts, Ma'am

3. Online
42% of Database Specialists Struggle to Manage NoSQL Solutions

4. Elsewhere
Test shows big data text analysis inconsistent, inaccurate

5. And now for something completely different

Sunday, January 25, 2015

Weekly Update




1. Quote of the Week
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

2. To Laugh or Cry?
Data Principles

3. Online debunkings
Comments on Relational Fidelity & Analytics Integrity
Comments on Data Model: Neither Conceptual, Nor Logical, Nor Physical Model

4. Elsewhere
Thou shalt not commit logical fallacies

5. And now for something completely different

Sunday, January 11, 2015

Weekly Update




1. Quote of the Week
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.com
2. To Laugh or Cry?
Types of database management system and their evolution
3. Online debunkings
4. Elsewhere
Big Data is Dead!
5. And now for something completely different

Monday, January 5, 2015

Silicon Valley SQL Server UG Presentation




"To Laugh or Cry?" Test Your Foundation Knowledge

Tuesday, January 20, 2015 6:30 PM

Microsoft
1065 La Avenida
Building 1
Mountain View, CA  (map)

RSVP here
 


You are a DBMS ace, able to squeeze every ounce of performance out of it. But how about your foundation knowledge, how good a grasp of data fundamentals do you possess? Are you a data management ace too?

The two are distinct and while the former is necessary for a career, it is insufficient for an informed, intelligent, reliable and productive data management practice. The industry is full of myths, misconceptions and traps and without foundation knowledge you are unable to see through them.

This is your opportunity to test yourself. If your instinct is neither to laugh, nor to cry at the contents of this presentation, education may be in order.

• How misconceptions that you are unaware of, lead you astray;
• Practical implications thereof;
• How foundation knowledge, scarce in the industry, is the only way to see through them.




Understand Property Rules & Domains




My January post @All Analytics 

To ensure operations on database tables or extracts thereof make sense and result interpretation is correct, the analyst must know what the tables mean. The meaning is not in the tables, but in the business rules it is associated with it, which may be undocumented.

Read it all. (Please comment there, not here)



 





Thursday, January 1, 2015

Thursday, December 11, 2014

Happy Holidays!





To all my readers and colleagues, Happy Hanukkah, Merry Xmas and a healthy, prosperous and Happy New Year!!!!

Sunday, December 7, 2014

Weekly Update



1. Quote of the Week
Relational is/was a way for humans to understand how computers could organise data. From a day back when disks were expensive. --LinkedIn.com

2. To Laugh or Cry?
How Google Will Use Firebase to Supercharge Its Cloud Computing
Another reinvention of a (square) weheel.


3. Online debunkings
Calendar supertype

4. Interesting elsewhere
On Persistence and Data Management
An oldie but goodie; check out my comment.


5. And now for something completely different

Fascinating:
John Cleese on the Black Knight and Douglas Adams' High Heels

About The PostWest:
White House exempts Syria airstrikes from tight standards on civilian deaths
Remember all the fuss about Israel not doing enough to prevent civilian deaths? The hypocrisy!




Wednesday, December 3, 2014

Analytics & SQL Tables



My December blog @All Analytics. 

Manipulating/extracting data from SQL databases and interpreting results without knowledge of what the source tables mean is almost certain to lead analysis astray. To ensure sensible analysis and properly interpreted results, the conscientious analyst may have to do some digging that requires basic database knowledge. Here's why.

Read it all. (Please comment there, not here)








Sunday, November 30, 2014

SQL's Incomplete Set-lization, Part 2




by Erwin Smout


[FP: Two weeks ago I posted a debunking of an article blaming some SQL sins. Erwin has some additional comments.]

1. Multisets


From the original article:
It is beyond any doubt that set is the basis of mass data computation. Although SQL has the concept of set, it is limited to describing simple result set, and it does not take the set as a basic data type to enlarge its application scope.
Sidestepping several possible nitpicks here, such as e.g., that SQL allows duplicate rows and thus, in its basic form, has bag, not set algebra, the intention behind the complaint here is mostly accurate.

Sunday, November 23, 2014

Weekly Update UPDATE 2



Housekeeping: I have added a link to Nijssen's paper The Entity-Relationship Model Considered Harmful to FUNDAMENTALS on the HOME page. UPDATE 2: The paper is fine if read with a PDF viewer other than
Adobe Reader XI (11.0.09).


1. Quotes of the Week
Platfora’s mission is to empower customers to transform their businesses into fact-based enterprises. Platfora's Big Data Analytics Platform masks the complexity of Hadoop, making it easy for customers to understand all the facts in their business... --Platfora.com
Q: I don't know what the different between detect inference in database and prevent it, any help?
A: Why would you want to prevent inferences that a DMBS makes? That's where the power of it is. --LinkedIn.com
2. To Laugh or Cry?
Graphs: A Better Database Abstraction
3. Online debunkings

4. Interesting elsewhere
You Too May Be A Victim Of Developaralysis
H/t Will Sisson.

5. And now for something completely different 
  • About The PostWest
If they do this:
Fatah official calls for blood to 'purify' Jerusalem of Jews
PA airs 'anti-Semitic' film as tensions mount in Jerusalem
Four killed in terror attack at Jerusalem synagogue
then obviously we should do this:
Croatia likely to recognize Palestine as a state MidEast
Sweden To Recognize State Of Palestine
Spanish Parliament Calls on Rajoy to Recognize Palestine
UK lawmakers vote to recognize Palestine as a state
and this
EU threatens 'further action' to protect two-state solution
EU considering 'sanctions' against Israel over settlements
Makes perfect sense. So what else is new?



Friday, November 7, 2014

Relational Fidelity and Analytics Integrity




My November blog post @All Analytics:


I have shown in previous posts that reliance on sheer visual inspection of database tables for data analysis is a risky proposition, with high probability of misinterpretation. All the more so when databases are complex, with wide and/or long tables. The analyst needs to know table interpretations -- their real-world meaning derived from the business rules with which the database must be consistent. The problem is that they are left out of the tables because DBMSs do not understand them, nor are they usually documented in the database (as they well should be), because database professionals underestimate their importance.

Read it all. (Please comment there, not here)









Sunday, November 2, 2014

Weekly Update



1. Quote of the Week
Those who argue for natural keys typically do so from a position of philosophical purity, as is the case in the Simple Talk article you cited. In my (25+) years of experience, people who argue from this position are long on education and short on real-world experience. In the real world just about every natural key I've ever come across is subject to duplication and/or redefinition. There are very few cases outside of smallish code tables where it is practical to take the philosophical high ground regarding natural keys. --StackExchange.com

2. To Laugh or Cry?
R2G a Tool for Migrating Relations to Graphs
H/t Erwin Smout.

3. Online debunkings

4. Interesting elsewhere
The Delusions of Big Data
Must read.

5. And now for something completely different
Ebola-- Failures of Imagination
Not to worry, America, Ebola will go to India first.
Can you detect the stealth animals hiding in all these pictures?
Fascinating.

About The PostWest:
Jihadism is OK as long as it kills Jews. Nice people. Let's ...
Irish parliament calls on government to recognize Palestine
... give them a state. Really?
Pat Condell: 'Boo Hoo Palestine'




Sunday, October 26, 2014

Weekly Update




1. Quote of the Week
Q: What's the key technical skills for Data Modeling? 
A: Erwin or Rational or phycial [sic] modelling or conceptual modelling or Logical modelling. --LinkedIn.com 
NULL means data is not available, nothing more...--LinkedIn.com
In case you were wondering.


2. To Laugh or Cry?

Oldie, but goodie from old dbdebunk:
On a Pile of ... what?

3. Online debunkings

4. Elsewhere

5. And now for something completely different
CDC blames cuts for Ebola response, pays millions in bonuses

About The PostWest:
Never again? Think again: they're at it again, to finish the job.
The Bible's Buried Secrets
Fascinating.



Sunday, October 19, 2014

Precision, Procedurality and SQL, Part 1



 by Erwin Smout and Fabian Pascal

"To be as precise as we possibly can is not a luxurious mannerism that the academic prig can afford himself in his (supposedly!) sheltered environment; for people facing the problems of "the real world" it is a Must." --E.W. Dijkstra, An Open Letter to L. Bass


From In Some Cases illustrating drawbacks of SQL in data computing and analytics
The computing power of SQL for mass structured data is complete, that is to say, it is impossible to find anything that SQL cannot compute. But its support layer is too low, which can lead to over-elaborate operation in practical application.
One of the four aspects of this "over-elaboration" is "computation without substep", but before we comment on it, the article glosses over an important matter.

Sunday, October 12, 2014

Weekly Update



Housekeeping: I have added FUNDAMENTALS links on HOME page to:

 1. Quote of the Week
I am teaching a database design course next year. What do you think should be covered in an introductory course? --LinkedIn.com
I have a requirement for an ERwin data modeler (Logical, Physical, 3NF and Star Schema). --LinkedIn.com

2. To Laugh or Cry?
What would be key entities in Automotive Industry MDM

3. Online debunkings

4. Must read elsewhere
Out of the Tar Pit

5. And now for something completely different
Ig Nobel Prize Winners
Cry, don't laugh.
Hey There Little Electron, Why Won't You Tell Me Where You Came From
Fascinating.
Israel is holding back channel talks with the 'Palestinian Authority' relating to Gaza, in which it is making concessions and receiving nothing in return.
The Tower cites a Wall Street Journal report that indicates that Western negotiators are so desperate for a deal with Iran that they are offering more significant sanctions relief for a deal that would not stop Iran from developing nuclear weapons.
Why the West is PostWest: The Blackmailer Paradox (Aumann is Nobel laureate in economics).




Monday, October 6, 2014

Tools Too Good to Be True



My October post @All Analytics

The Wired article Ex-Googler Shares His Big-Data Secrets With the Masses touts a new tool that "mimics the way web giants like Google and Facebook rapidly analyze enormous amounts of online information." The article calls the tool "simple for analysts to query data from anywhere in a company with a single tool, regardless of where that data is stored, without the need to learn new programming languages."

Read it all. (Please comment there, not here)



 






Sunday, September 28, 2014

Weekly Update




1. Quote of the Week
Further to that point, in my mind you can have a database that is both relational and schema-less, in the sense that it is relational if the only thing in it is relations but it is schema-less if any data updating operation is allowed to change the number or degree etc of said relations, rather than that being reserved for so called data-definition operations. --LinkedIn.com
2. To Laugh or Cry?
Turning dirty data words into sweet talk
And an oldie, but goodie
Gardner to DBAs, BI Vendors Reinvent Yourselves
3. Online Debunkings
4. Elsewhere

An old classic:
Unskilled and Unaware of It
and a related consequence
How Our Botched Understanding of Science Ruins Everything
5. And now for something completely different
"Enjoy":
John Oliver: Nuclear Weapons
Fascinating:
Freaky Physics Experiment May Prove Our Universe Is A Two-Dimensional Hologram
About the PostWest:
PA: Israelis Must Return to Their Countries of Origin
How about the Arabs in Palestine, most of of whom originate in immigrants from Arab countries attracted to Palestine by jobs created by Jewish development?
If it's not Jews doing it, who cares. It's not so much care for Palestinians as it is hate of the Jews.
Any way, Nice people. Let's give them a state.
US Providing Indirect Military Aid to Hezbollah
Afghanistan and Iraq redux.
Go Easy on Iran So It Fights ISIS? That's Absurd
Indeed: Why should the US allow an enemy nuclear weapons, when fighting ISIS is Iran's own existential interest anyway? Let radical Shia and Sunni duel it out.
World Council of Churches Demands Israel Release Terrorists
Ah, yes, religion is the source of morality.




Sunday, September 21, 2014

New Paper on Domains



Pls see the PAPERS page for the current version of the paper, when it becomes available.

Sunday, September 14, 2014

Weekly Update




Housekeeping:

  • Added a LINKS page to the top site menu, with links to items I deem worth reading. Added a few from my old site and new ones will be added as I come across them.
  • Overhauled the FUNDAMENTALS list of sources at the right of the HOME page. It now includes links to the bibliographies of E. F. Codd, D. McGoveran, C. J. Date, H. Darwen and myself. 


1. Quote of the Week
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.com
2. To Laugh or Cry?
Survey data model, what is the best approach?
3. Online Debunkings
Dr. Robin Bloor: Big Data is “nonsense”
4. Elsewhere
5. And now for something completely different
Senator Challenges Zuckerberg
American patriot.
The Exorcisms of Anneliese Michel
Fascinating.

@The PostWest:



View My Stats