Wednesday, July 30, 2014

Big Data & Analytics: Table Interpretations



My July Post @All Analytics

When, for analytical purposes, you combine data extracted from database tables whose real-world meaning you don't know, you're asking for trouble. The meaning, after all, isn't in the tables. Rather, the meaning is contained in the business rules on the basis of which the tables were designed and which are approximated in the database with integrity constraints. Interpreting results on the basis of just visual inspection of the tables therefore involves guesswork and is almost certain to be wrong.

Read it all. (And please comment there, not here)



 



Sunday, July 27, 2014

Weekly Update UPDATED




1. Quote of the Week
Q: In a nutshell, what does RDF based Linked Data facilitate?
A: The ability to find and describe stuff using attributes (relations, properties, features, fields, characteristics). --LinkedIn.com

2. To Laugh or Cry?
Data Model now offers Relationship Modeling

3. Online Debunking
Data Vaults - Why Or Why Not

4. Elsewhere
 
5. And now for something completely different

In its decline, theWest is becoming impotent and increasingly irrelevant in world affairs e.g. Russia, Syria, Iraq, Afghanistan, China, Libya, you name it. It is taking hypocritically its frustration on Israel and the Jews--its classic scapegoating during crises--reinforced by fear from internal Islam.

I am restarting my PostWest blog and will link regularly to posts in this section.


Critical comments that
  • fail to show my facts to be false; or, if they are true, that my conclusions do not follow;
  • are posted anonymously
will not be published and addressed.







Sunday, July 6, 2014

Weekly Update




1. Quote of the Week
Don't confuse Data(base) Modeling with Business Modeling. All DBA are correct when they are talking about Database Modeling. If you want to ensure unique record on Business level, just add a unique composite index. (not as Key). But far to often, a unique record on business level is not ALWAYS unique (only most of the time) --LinkedIn.com

2. To Laugh or Cry?
Create database vs schema

3. Online Debunkings

4. Interesting Elsewhere

5. And now for something completely different
 And if you like what they're doing to San Francisco, you'll love what they'll do to other cities:
Google Exec Rises Ire in Portland
 Symptoms of societal malaise.



Monday, June 30, 2014

Big Data, Normalization & Analytics: Meaning & Constraints



My June post @All Analytics

Combining data extracts from databases for analytical purposes without knowing what the source database tables mean -- what exactly in the real world they represent -- can produce wrong results.

Read it all. (And please comment there, not here)



 




Sunday, June 29, 2014

Denormalization: Database Bias, Integrity Tradeoff and Complexity




The common and entrenched misconception about normalization was recently visible yet again in a LinkedIn exchange.
R: Unless the need is for ACID compliant transactions, denormalization is generally not considered logically, physically or whatever-ally-–so essentially a thoroughly normalized mode is relevant for a write-infrequently consumption of data and data integrity can be guaranteed by design.

Sunday, June 22, 2014

Weekly Update




I have corrected a mistake in For Codd's Sake: a mathematical relation is not the Cartesian product (CP) of the domains over which it is defined. Two readers correctly pointed out what I actually wrote myself in my business modeling paper:
Mathematically, a relation on domains—which are sets of values of a type—is a subset of the Cartesian product of the domains.
Note that the whole CP is also a subset, so it is also a relation, which happens to have useful applicability to business modeling and database design. In the database context, it can be pictured as the pool of all possible rows--past, present and future--for a R-tablevar defined by the domains' types. A database R-table is the set of actual rows at any point in time that is consistent with the set of all integrity constraints to which the R-table is subject (see Business Modeling for Database Design).


1. Quote of the Week
NoSQL usant correct m'y indeed totof n'y most of the dev ans devops who clearly thing nosql Means they will ne a le to do whatever they wants ans still have answers to their twisted query in a correct time. Those people see nosql as the mean to get ris of DBAs. And il not kiddin since it's happening right now un many companies i know of. --LinkedIn.com

2. To Laugh or Cry?
Architecting IMS for Big Data - a symbiotic relationship.

3. Online 

4. Interesting Elsewhere
IEEE Computer Issue on CAP Theorem
H/t Erwin Smout.


5. And now for something completely different

The PostWest.



View My Stats