19 replies
by antsu
by donna
by tbangs
Donna:
I use the analogy of how people meet, find something in common and then can talk to each other. It's simple and they get it. It is best for beginning database students not to go into too much detail. When you start with basic queries, the lightbulbs start to go off.
Hope this helps a bit.
Terri
by donna
by bev
I show them a large table with the following fields names (abbreviated on the table)
FName
LName
Job title
DOB
Salary
Company car yes/no
Make of car
Car Reg
Year of car
Date of last service
Garage used
Get them to undestand this infois all related but table too big and the Date of service will only except one entry and Garage field would get messy (I'm sure u get the picture)
So we seperate it out into 3 tables
1)FName, LName, Job title, DOB, Salary, Company car yes/no
2)Make of car,Car Reg,Year of car
3)Date of last service
Garage used
Explain common denominator needed
Add Employee ID field to tables 1 & 2. I've found if u put the fields you're going to use for the relationship at this point and not at thebeginning - and that they add the same field to both tables pretty much at same time they understand why they are doing it
Then I encourage them to work out what common denominator would be good to link the table 2 & 3 together - already got reg no so why not duplica
by donna
by saratogapete
I think you have to establish the experience of your audience first. Here are two topics I talk about.
Excel
Most users have an Excel view of the world. They think Excel is a database. So I talk about how they have to repeat lots of information, row by row, in order to have a complete "record" about something.
L.L. Bean
Everybody has called L.L. Bean (or Land's End or Eddie Bauer), so I run through the scenario about you giving them your phone number or customer id. And then the repbrings upyour information and she asks you for your order. You order 2 sweaters, some boots, and a tent. (Then I ask the question) Which do you think would be the better way to store the information - To copy your address information over, and over, for each product you ordered or to save it once and then "access it" with a unique number?
It seems when I present it that way, they get the "goal" of trying to store data efficiently. Because what you are really trying to explain is a normalized database desig
by donna
by drexciya
The way I treat this subject in an Access course is first explaining a modelling technique, the ER model.
Making relational databases is like building a house; you need a construction drawing.
That's where the ER model kicks in. You simply putdownwhat the database will be about (take a generic example) and lo and behold, you end up with >1 table. Then you'll fit them together with relationships.
Then explain why you're doing this --> increased efficiency, increased accuracy and less input.
by donna
by gcj01
I've done oracle DBA stuff..... So show your students a table that has
these columns:
fruit name barcode
show your students a 2nd table that has these columns:
barcode price
so the 2nd table can be changed any time the price does without affecting
the first table that probably never changes except for adding new fruit.
Since everybody has to buy fruit sometime at a major grocery store ..
They ought to grasp the concept QUICKLY.
Maybe to make it more fun use candy or booze instead
Just keep the tables very very simple then you can show them more
complex tables and then you can explain the concept of SQL.
hope this helps!
Gloria
by donna
by jlove
1. Make a table called sales reps.
fields are key - salesrep number, data type text, salesperson first name (text) salesperson last name (text) note: you can use the lnm naming conventions for the field names however you choose.
2. make a table called customer with fields for key (customer number) customer first, last, street, city, state, zip and order number (see point 4 on this last item)
3. make a table called orders with order number, order date, item number, item description, price perunit, andnumber ordered.
4. explain the normalization issues concerning key fields, names (ie first and last instead of one name) different tables so as not to repeat information. Ask them which fields might cause data to be repeated.
5. Open the database window to the tables tab. Explain how to view relationships, and show the tables. Get them to drag the correct fields to make the relationships and what the join types are. Then show them and explain the use of referential integrity. Get them to keep the tabl
by donna
by bradbartram
I've always taken a piece of paper with lines drawn on it. I've then taken four post-it notes and stuck them to the back. The post-its also have lines drawn on them. When put all together, the post-its and the paper on top make a square.
I've used this abstract example to show that to make a complete picture, all information doesn't have to be all in one physical place. I build on this example by giving a situation specific example using "real" data and try to fill in all the sheets of paper with data.
I can normally tell when this approach works because that light goes on for the people I teaching.
by donna
by brenlee1
Donna,
Do your students a favor and explain tables as objects with attributes.
This sounds advanced, but when you use an example, such as a person which has attributes of name, DOB, etc.
It will also set them up should they intend to pursue programming later.
by donna
by donna
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending