Follow @DBDebunk
Follow @ThePostWest
My August Post @All Analytics
To ensure data operations make sense and results correspond to the real
world and are interpreted correctly, analysts need to know the business
rules on the basis of which a database was designed. Here are the types
of rules for which they should be looking.
Read it all. (Please comment there, not here)
Tuesday, August 26, 2014
Sunday, August 24, 2014
NEW: Paper revisions available
Follow @DBDebunk
Follow @ThePostWest
Pls see PAPERS page for the current version of this paper, when it becomes available.
Pls see PAPERS page for the current version of this paper, when it becomes available.
Friday, August 15, 2014
Weekly Update
Follow @DBDebunk
Follow @ThePostWest
1. Quote of the Week
2. To Laugh or Cry?
3. Online Debunkings
5. And now for something completely different
@The PostWest
1. Quote of the Week
Invoice number is the key (key is not unique in this table). Although structure or key constraints doesn't enforce uniqueness of rows, the assumption is there will not be duplicate rows. --LinkedIn.com
2. To Laugh or Cry?
Relational Queries by Reference
3. Online Debunkings
What is Weak Subtype
5. And now for something completely different
Tim's VermeerFascinating
@The PostWest
- ISIS Bad, Hamas OK: Only One Difference
- Efraim Karsh: It's Anti-Semitism, Stupid
- Pinch Me
- The West Prefers to Deplore Dead Jews To Letting Them Defend Themselves
- Israel and the Arabs in War: Two observations
- Just Sayin'
- Obama to Israel: Do As I Say, Not As We Do
- Cairo talks: Deja Vu
- Reality Check
- Gaza Blame: Upside Down and Backwards
Sunday, August 10, 2014
The 'Real World' and Database Design
Follow @DBDebunk
Follow @ThePostWest
Conveying data fundamentals to practitioners, losing neither rigor, nor the audience is a difficult task. There are many experienced professionals with tool expertise, but poor foundation knowledge for which there is little regard. Even in academia education has been substituted by training, which is not the same thing.
One dilemma faced by an educator is the tension between the simplicity of examples effective for conveying general concepts or principles and the complexity of the reality to be represented in databases. The latter requires integration of many concepts and principles, as well as thorough business knowledge. This is part of the reason why I normally refrain from specific online modeling/design advice and limit myself to the general principles that must be adhered to in the process.
Conveying data fundamentals to practitioners, losing neither rigor, nor the audience is a difficult task. There are many experienced professionals with tool expertise, but poor foundation knowledge for which there is little regard. Even in academia education has been substituted by training, which is not the same thing.
One dilemma faced by an educator is the tension between the simplicity of examples effective for conveying general concepts or principles and the complexity of the reality to be represented in databases. The latter requires integration of many concepts and principles, as well as thorough business knowledge. This is part of the reason why I normally refrain from specific online modeling/design advice and limit myself to the general principles that must be adhered to in the process.
Wednesday, July 30, 2014
Big Data & Analytics: Table Interpretations
Follow @DBDebunk
Follow @ThePostWest
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)
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
Follow @DBDebunk
Follow @ThePostWest
1. Quote of the Week
2. To Laugh or Cry?
3. Online Debunking
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
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
Sunday, July 6, 2014
Weekly Update
Follow @DBDebunk
Follow @ThePostWest
1. Quote of the Week
2. To Laugh or Cry?
3. Online Debunkings
4. Interesting Elsewhere
5. And now for something completely different
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
- Big data means the reign of the relational database is over
- Conceptual Muddling and Database Kludges
- What do Data Scientists and Unicorns have in Common
4. Interesting Elsewhere
5. And now for something completely different
- S.F. housing prices bidding wars fiercer than ever
- Pinterest Threatens Long-Time San Francisco Tenants With Eviction
- San Francisco Protests at the Home & Office of David McCloskey
- San Francisco's guerrilla protest at Google buses swells
- Few applicants for blue-collar jobs in S.F.
- Shame of the City-Homeless in San Francisco
- A decade of homelessness - Thousands in S.F. remain in crisis
- AngelHack CEO's Attack On Homeless
- S.F. to offer George Lucas prime lot for his museum
Google Exec Rises Ire in Portland
Subscribe to:
Posts (Atom)