Postgresql East 2010  Philadephia, PA Databases – A Historical Perspective
WHO AM I? Brent Friedman Senior Solutions Consultant Cincom Systems, Inc [email_address] Databases – A Historical Perspect...
What is a database?  Databases – A Historical Perspective
The earliest computers weren’t sufficiently complex to entertain the idea of a free-standing database.  Data was directly ...
DATABASE – NETWORK MODEL CODASYL References to data are through low-level pointers.  Adding or changing a database require...
DATABASE – HIERARCHICAL MODEL IBM’s IMS These databases allow only 1:1 or 1:many relationships.  Such databases can be inc...
Name a hierarchical database system that is still in everyday use around the world. Hint:  What contact information about ...
Around 1964, the term "data base" was "coined by workers in military information systems to denote collecti...
TIMELINE:  1964 Databases – A Historical Perspective http://www.computersciencelab.com/ComputerHistory/HistoryPt4.htm
TIMELINE:  1967 Databases – A Historical Perspective The term “memory bank” enters, and soon (thankfully) leaves, the Engl...
1969… Was not just about the counter-culture.  But things were about to happen… Databases – A Historical Perspective
TIMELINE:  1970 Edgar F. Codd, commonly cited as E. F. Codd, published a paper on something he called “Relational Database...
Codd, continued Codd’s revolutionary idea did not focus on the relational algebra, but rather on how the data should be ad...
RDBMS – What’s that? A relational database management system is ultimately based on E. F. Codd’s theories. Databases – A H...
TIMELINE – 1970s RDBMS – Path 1 The Ingres Group: Ingres; Sybase; MS Sql Server; and something called Postgres… These used...
TIMELINE – 1970s RDBMS – Path 2 The (IBM) System R Group: DB2; Oracle; Nonstop SQL These used the SQL language Databases –...
TIMELINE - 1976 Peter Chen proposed the Entity-Relationship diagram (ERD), which is still sometimes called a “Chen diagram...
ERD – Chen Diagram http://en.wikipedia.org/wiki/Entity-relationship_model Databases – A Historical Perspective
ERDs and so on There are a multitude of design practices, modelling tools, and even variations on how to diagram relationa...
To avoid tomato throwing, insinuations about lineage, and general bodily harm, we will avoid a direct discussion of specif...
If you really need a hint… Database Design Studio   Lite or Pro versions www.chillisource.com Databases – A Historical Per...
TIMELINE – 1980s The QUEL branch of RDBMS suffers a horrible boating accident, and is not heard from again. Databases – A ...
TIMELINE – 1980s SQL Structured Query Language  becomes the de facto standard among all relational database products. Data...
SQL – The Real Image Databases – A Historical Perspective
TIMELINE – mid 1980s The rise of the personal computer (PC) issues in a host of new ‘personal’ relational databases: Parad...
TIMELINE – early 1990s The trend toward 4GL (4 th  generation languages) leads to visual front-ends for personal databases...
TIMELINE - 1990 Some geek named Tim Berners-Lee, or “Sir Timothy John Berners-Lee, OM, KBE, FRS, FREng, FRSA” for all you ...
TIMELINE – mid 1990s This “World Wide Web” thing really catches on, once Al Gore let everybody know they could do somethin...
TIMELINE – late 1990s Relational databases become so ubiquitous that even your mother knows what “DBA” means. Databases – ...
TIMELINE – 1995ish Graduate students Andrew Yu and Jolly Chen revise Postgres’s query language, POSTQUEL, to use SQL, and ...
TIMELINE – 2000s Object databases, although they have been around for a while, start to get noticed by non-geeks.  Databas...
The role of object databases in “SKYNET” has not yet been determined… Databases – A Historical Perspective
TIMELINE – 2005 Columnar databases find a growing audience in the “need for speed” crowd.  While probably still a niche se...
TIMELINE -2008 Sun Microsystems acquires MySQL Databases – A Historical Perspective
TIMELINE – 2009  The rise of distributed systems inspires the NoSQL movement – rejection of traditional RDBMS systems for ...
TIMELINE – 2010  Will cloud computing  gain ground on  traditional IT  infrastructure models?  Databases – A Historical Pe...
Questions? Comments? Databases – A Historical Perspective
END  OF PART  ONE Databases – A Historical Perspective
Upcoming SlideShare
Loading in …5
×

Normalization: A Workshop for Everybody Pt. 1

1,130 views
1,038 views

Published on

Brent Friedman

- Three hour workshop format, 30 minutes or so on history, trends, quick review of normalization, 45 minutes on a normalization walk-through including everyone, then break into small teams (3-6 ppl) to do a 'normalization challenge' on a real world practical problem

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,130
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • [ Note to trainer : For detailed help in customizing this template, see the very last slide. Also, look for additional lesson text in the notes pane of some slides.]
  • Normalization: A Workshop for Everybody Pt. 1

    1. 1. Postgresql East 2010 Philadephia, PA Databases – A Historical Perspective
    2. 2. WHO AM I? Brent Friedman Senior Solutions Consultant Cincom Systems, Inc [email_address] Databases – A Historical Perspective
    3. 3. What is a database? Databases – A Historical Perspective
    4. 4. The earliest computers weren’t sufficiently complex to entertain the idea of a free-standing database. Data was directly linked with the application in memory at the time. TIMELINE: 1950s Databases – A Historical Perspective
    5. 5. DATABASE – NETWORK MODEL CODASYL References to data are through low-level pointers. Adding or changing a database required considerable reworking of the storage mechanism. TIMELINE: 1960s Databases – A Historical Perspective
    6. 6. DATABASE – HIERARCHICAL MODEL IBM’s IMS These databases allow only 1:1 or 1:many relationships. Such databases can be incredibly fast, but are not well suited to hold disparate types of information. TIMELINE: 1960s Databases – A Historical Perspective
    7. 7. Name a hierarchical database system that is still in everyday use around the world. Hint: What contact information about people do YOU store right now? DATABASE TRIVIA Databases – A Historical Perspective
    8. 8. Around 1964, the term "data base" was "coined by workers in military information systems to denote collections of data shared by end-users of time sharing computer systems." In earlier days, each application had its own "master files" of data, so the concept of a data collection that could be shared by multiple applications was a new idea in efficiency. http://www.snee.com/bobdc.blog/2005/12/25-years-of-database-history-s-1.html Databases – A Historical Perspective
    9. 9. TIMELINE: 1964 Databases – A Historical Perspective http://www.computersciencelab.com/ComputerHistory/HistoryPt4.htm
    10. 10. TIMELINE: 1967 Databases – A Historical Perspective The term “memory bank” enters, and soon (thankfully) leaves, the English language.
    11. 11. 1969… Was not just about the counter-culture. But things were about to happen… Databases – A Historical Perspective
    12. 12. TIMELINE: 1970 Edgar F. Codd, commonly cited as E. F. Codd, published a paper on something he called “Relational Database Theory” Databases – A Historical Perspective http://www.ibiblio.org/jelkner/IntroToIT/database_lesson.html
    13. 13. Codd, continued Codd’s revolutionary idea did not focus on the relational algebra, but rather on how the data should be addressed. His theory separated the schema from the storage mechanism. Databases – A Historical Perspective
    14. 14. RDBMS – What’s that? A relational database management system is ultimately based on E. F. Codd’s theories. Databases – A Historical Perspective
    15. 15. TIMELINE – 1970s RDBMS – Path 1 The Ingres Group: Ingres; Sybase; MS Sql Server; and something called Postgres… These used the QUEL language Databases – A Historical Perspective
    16. 16. TIMELINE – 1970s RDBMS – Path 2 The (IBM) System R Group: DB2; Oracle; Nonstop SQL These used the SQL language Databases – A Historical Perspective
    17. 17. TIMELINE - 1976 Peter Chen proposed the Entity-Relationship diagram (ERD), which is still sometimes called a “Chen diagram” Databases – A Historical Perspective
    18. 18. ERD – Chen Diagram http://en.wikipedia.org/wiki/Entity-relationship_model Databases – A Historical Perspective
    19. 19. ERDs and so on There are a multitude of design practices, modelling tools, and even variations on how to diagram relational data. Databases – A Historical Perspective
    20. 20. To avoid tomato throwing, insinuations about lineage, and general bodily harm, we will avoid a direct discussion of specific schools of thought in the area of relational data representation. Databases – A Historical Perspective
    21. 21. If you really need a hint… Database Design Studio Lite or Pro versions www.chillisource.com Databases – A Historical Perspective http://www.thespeciousreport.com/2006/06060222comedy.html database design tool
    22. 22. TIMELINE – 1980s The QUEL branch of RDBMS suffers a horrible boating accident, and is not heard from again. Databases – A Historical Perspective
    23. 23. TIMELINE – 1980s SQL Structured Query Language becomes the de facto standard among all relational database products. Databases – A Historical Perspective
    24. 24. SQL – The Real Image Databases – A Historical Perspective
    25. 25. TIMELINE – mid 1980s The rise of the personal computer (PC) issues in a host of new ‘personal’ relational databases: Paradox; Dbase III; RBASE; etc. Databases – A Historical Perspective
    26. 26. TIMELINE – early 1990s The trend toward 4GL (4 th generation languages) leads to visual front-ends for personal databases: Powerbuilder; Oracle Developer; and even early MS VB Databases – A Historical Perspective
    27. 27. TIMELINE - 1990 Some geek named Tim Berners-Lee, or “Sir Timothy John Berners-Lee, OM, KBE, FRS, FREng, FRSA” for all you Brits, proposed mating hypertext with the early Internet. Databases – A Historical Perspective
    28. 28. TIMELINE – mid 1990s This “World Wide Web” thing really catches on, once Al Gore let everybody know they could do something with their dial-up modems besides playing DECWar at the local university. Databases – A Historical Perspective
    29. 29. TIMELINE – late 1990s Relational databases become so ubiquitous that even your mother knows what “DBA” means. Databases – A Historical Perspective
    30. 30. TIMELINE – 1995ish Graduate students Andrew Yu and Jolly Chen revise Postgres’s query language, POSTQUEL, to use SQL, and call it Postgres95… http://www.postgresql.org/about/history Databases – A Historical Perspective
    31. 31. TIMELINE – 2000s Object databases, although they have been around for a while, start to get noticed by non-geeks. Databases – A Historical Perspective
    32. 32. The role of object databases in “SKYNET” has not yet been determined… Databases – A Historical Perspective
    33. 33. TIMELINE – 2005 Columnar databases find a growing audience in the “need for speed” crowd. While probably still a niche segment, products such as Monet are increasing in popularity. Databases – A Historical Perspective
    34. 34. TIMELINE -2008 Sun Microsystems acquires MySQL Databases – A Historical Perspective
    35. 35. TIMELINE – 2009 The rise of distributed systems inspires the NoSQL movement – rejection of traditional RDBMS systems for distributed data structures, such as Apache Hadoop Databases – A Historical Perspective
    36. 36. TIMELINE – 2010 Will cloud computing gain ground on traditional IT infrastructure models? Databases – A Historical Perspective
    37. 37. Questions? Comments? Databases – A Historical Perspective
    38. 38. END OF PART ONE Databases – A Historical Perspective

    ×