SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Site Related Forums
 Article Discussion
 Article: Database Design and Modeling Fundamentals
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

AskSQLTeam
Ask SQLTeam Question

USA
0 Posts

Posted - 07/02/2000 :  00:00:00  Show Profile  Visit AskSQLTeam's Homepage  Reply with Quote
This article covers the basics of database design including normalization, relationships and cardinality. A great tutorial on database design.

Article Link.

Anonymous
Starting Member

0 Posts

Posted - 07/27/2000 :  23:42:34  Show Profile  Reply with Quote
Great article!

Very helpful article. Thanks!

Go to Top of Page

Anonymous
Starting Member

0 Posts

Posted - 07/29/2000 :  07:53:08  Show Profile  Reply with Quote
Thanx

I'll use this recommends while i was designing to my db.

Go to Top of Page

Anonymous
Starting Member

0 Posts

Posted - 01/28/2001 :  19:27:33  Show Profile  Reply with Quote
Thanks... Now, Coding from a Model??

Thanks very much for a very clear and concise dissertation.

Now, having drawn up hte model in a modelling program, and output the
SQL tables, I am intimidated by how exactly to write the handling code (in PHP)?

Your mention that the parent must exist before the Child looks like a starting point.

Thanks.
:-)
John

Go to Top of Page

MossyBlog
Starting Member

Australia
1 Posts

Posted - 12/05/2005 :  05:13:30  Show Profile  Visit MossyBlog's Homepage  Reply with Quote
Great article, except there seems to be a bit of confusion surrounding entities..

In SQLTeam.com via "Database object naming conventions" article, the following was put forward:

http://vyaskn.tripod.com/object_naming.htm

quote:

Tables:

Tables represent the instances of an entity. For example, you store all your customer information in a table. Here, 'customer' is an entity and all the rows in the customers table represent the instances of the entity 'customer'. So, why not name your table using the entity it represents, 'Customer'. Since the table is storing 'multiple instances' of customers, make your table name a plural word.

So, name your customer table as 'Customers'.
Name your order storage table as 'Orders'.
Name your error messages table as 'ErrorMessages'.




Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.17 seconds. Powered By: Snitz Forums 2000