9 replies
by bamis4u Accepted solution
by purpleskys Accepted solution
by tobif Accepted solution
Try to imagine for yourself, what you could use your new database for.
How would you model the reality you want to describe?
What relationships?
What features would help you to make your system useful?
Etc.
by santeewelding Accepted solution
by ansugisalas Accepted solution
it could make carbon dioxide gas spontaneously congeal into diamonds.
And maybe they could be really really big diamonds, and they could fall on top of people I hate from very very high up in the air.
O - How I would laugh.
And then collect, wipe, sell.
And then I would laugh more. Much more.
But maybe that's what you meant?
by tony hopkinson Accepted solution
Get a book/course/tutorial on database theory.
Learn the fundameantals.
Nullability, normalisation, relations.
Then pick a tool (my pick would be sql server express 2008 (free from ms)).
Choose what you want to design a database for and apply the fundamentals with it.
If you really want to learn it, do not start with the graphical tools. Do it in SQL.
If you are stuck for a starter example
Orders, Customers and invoices is nice and the classic hospital, patients and beds is a lot of fun.
Can a patient be in two beds?
Can one bed have two patients?
Can the bed switch wards?
Or change can to should or would?
Ah memories...
by brian Accepted solution
by tony hopkinson Accepted solution
not dragging arrows about on a GUI.
I'm always forgeting join syntax. It's not what I'd call intuititive. As long as you know it's there, F1 and Google will rescue you.
The real trick is to realise that a table is no more a rectangular array of cells than it is a piece of furniture.
by tobif Accepted solution
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending