Follow @DBDebunk
Follow @ThePostWest
See Relationships and the RDM Part 1: Kinds of Relationships
Sunday, July 21, 2013
Monday, July 15, 2013
Site Update (UPDATED)
Follow @DBDebunk
Follow @ThePostWest
07/19/13: I have also added my latest post at All Analytics to the FP ONLINE page.
07/18/13: This update referred to items that were erroneously dated 7/3/13 instead of 7/15/13. This has now been corrected.
1.
The 'Quote of the Week' was posted to the QUOTES page.
2.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
Everything should be as simple as possible, but not simpler.
--Albert Einstein
3.
A link to an exchange I participated was posted on the FP ONLINE page.
4.
And now for something completely different.
If You Search, Advertise on, Invest in, or Have Kids Who Use Google, You Must See
Too much power is always dangerous, no matter who holds it.
07/19/13: I have also added my latest post at All Analytics to the FP ONLINE page.
07/18/13: This update referred to items that were erroneously dated 7/3/13 instead of 7/15/13. This has now been corrected.
1.
The 'Quote of the Week' was posted to the QUOTES page.
2.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
Everything should be as simple as possible, but not simpler.
--Albert Einstein
3.
A link to an exchange I participated was posted on the FP ONLINE page.
4.
And now for something completely different.
If You Search, Advertise on, Invest in, or Have Kids Who Use Google, You Must See
Too much power is always dangerous, no matter who holds it.
Monday, July 8, 2013
Relational Theory and Database Practice
Follow @DBDebunk
Follow @ThePostWest
I shared the links to my recent three-part series on foreign keys (and integrity constraints in general) on LinkedIn. Comments on the second installment raised an important issue about keys (discussed in more depth in Business Modeling for Database Design), which deserves attention.
I shared the links to my recent three-part series on foreign keys (and integrity constraints in general) on LinkedIn. Comments on the second installment raised an important issue about keys (discussed in more depth in Business Modeling for Database Design), which deserves attention.
NK: Let me first affirm my position that I believe foreign keys are the fundamental bases on which relational database managements system operate. Foreign keys provide the relationship in database normalization. Foreign keys are like the framework of a building structure. While some developers may have the notion that constraints and integrity checks can be handled better at the application layer, I would want to refer them to tools like ER Studio, ERWIN, and Visual Studio ... A good database design starts at the logical design level. Abstracting constraints and integrity checks from this layer to the application layer can lead to corrupt database designs. A simple case in point; How would you enforce a unique constraint on a table with 10 million rows? Will it make better sense to have a unique index on the table\field or have the application layer enforce the constraint?
Saturday, June 29, 2013
Site Update
Follow @DBDebunk
Follow @ThePostWest
1.
On the SCHEDULE:
A private database design seminar, October 9-10, Milan, Italy (sponsored by Microsoft and SolidQ)
A public presentation to the SQL Server User Group Italy (UGISS), October 8, Milan, Italy.
Details forthcoming. Contact Davide Mauri @SolidQ.
2.
The 'Quote of the Week' is an online question that is too long to post to the QUOTES page, so I posted the link to the exchange it initiated.
3.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
Remember my claim that we are regressing to this?
4.
A link to an exchange I participated was posted on the FP ONLINE page.
5.
Life and Work of Ted Codd (YouTube)
Is everything accurate?
6.
And now for something completely different.
How the Hum of a Coffee Shop Can Boost Creativity
The logical conclusion and real risk of digitizing everything in sight.
1.
On the SCHEDULE:
A private database design seminar, October 9-10, Milan, Italy (sponsored by Microsoft and SolidQ)
A public presentation to the SQL Server User Group Italy (UGISS), October 8, Milan, Italy.
Details forthcoming. Contact Davide Mauri @SolidQ.
2.
The 'Quote of the Week' is an online question that is too long to post to the QUOTES page, so I posted the link to the exchange it initiated.
3.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
Remember my claim that we are regressing to this?
4.
A link to an exchange I participated was posted on the FP ONLINE page.
5.
Life and Work of Ted Codd (YouTube)
Is everything accurate?
6.
And now for something completely different.
How the Hum of a Coffee Shop Can Boost Creativity
The logical conclusion and real risk of digitizing everything in sight.
Tuesday, June 25, 2013
Data Model: Neither Business, Nor Logical, Nor Physical Model
Follow @DBDebunk
Follow @ThePostWest
Note: For a more in-depth discussion see Business Modeling for Database Design.
Chris Date once wrote a paper titled Models, Models Everywhere, Nor Any Time to Think, deploring the confused and distorted way in which fundamental concepts and terminology in general and relational ones in particular, are used in the industry. But no matter how many times a misconception is debunked, the abuse continues and will do so given educational failure and disregard for precision. Data model is a case in point (see Unmuddling Modeling, Parts 1,2) and What Is a Data Model?)
Note: For a more in-depth discussion see Business Modeling for Database Design.
Chris Date once wrote a paper titled Models, Models Everywhere, Nor Any Time to Think, deploring the confused and distorted way in which fundamental concepts and terminology in general and relational ones in particular, are used in the industry. But no matter how many times a misconception is debunked, the abuse continues and will do so given educational failure and disregard for precision. Data model is a case in point (see Unmuddling Modeling, Parts 1,2) and What Is a Data Model?)
Thursday, June 20, 2013
Site Update
Follow @DBDebunk
Follow @ThePostWest
1.
The following were added to the SCHEDULE:
The 'Quote of the Week' was posted on the QUOTES page.
3.
My latest All Analytics column was posted on the FP ONLINE page.
Two of the previously posted exchanges have new comments:
Different Types of DBMS
Comments on my Foreign Keys, Part 2 The Costs of Application-Enforced Integrity
4.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
5.
A link to an exchange I participated was posted on the FP ONLINE page.
6.
And now for something completely different
1.
The following were added to the SCHEDULE:
- Private database design seminar, October 9-10, Milan, Italy (sponsored by Microsoft and organized by SolidQ)
- Public presentation to the SQL Server User Group Italy (UGISS), October 8, Milan, Italy, organized by SolidQ.
The 'Quote of the Week' was posted on the QUOTES page.
3.
My latest All Analytics column was posted on the FP ONLINE page.
Two of the previously posted exchanges have new comments:
Different Types of DBMS
Comments on my Foreign Keys, Part 2 The Costs of Application-Enforced Integrity
4.
A 'To Laugh or Cry' item was posted on the LAUGH/CRY page.
5.
A link to an exchange I participated was posted on the FP ONLINE page.
6.
And now for something completely different
European data protection watchdogs are closing in on Google, with Spain charging the software giant with six legal infringements punishable by up to €1.5m (£1.3m) in fines, while France has given it three months to rewrite its privacy policy.I'm sure this will put stop to abuses cold.
...
On the same day, France's Commission Nationale de l'Informatique et des Libertés (CNIL) gave Google formal notice that it risks a fine of up to €150,000 and a second of €300,000 if it fails to rewrite its privacy policy within three months.
--Google and privacy: European data regulators round on search giant
Subscribe to:
Posts (Atom)