Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Level 3: Relational Database Design Expand / Collapse
Author
Message
Posted Monday, September 5, 2011 9:07 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, May 27, 2015 11:47 PM
Points: 1,040, Visits: 281
Comments posted to this topic are about the item Level 3: Relational Database Design

Gregory A. Larsen, MVP

Need SQL Server Examples check out my website at http://www.sqlserverexamples.com
Post #1169994
Posted Wednesday, November 9, 2011 12:04 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, November 21, 2012 9:20 AM
Points: 14, Visits: 58
Why the article is titled "Relational Database Design" while it presents bunch of DDL&DML statements and shows implementation rather than design?
Post #1203147
Posted Wednesday, November 16, 2011 6:04 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, May 27, 2015 11:47 PM
Points: 1,040, Visits: 281
Thank you for pointing out the title problem. For some reason when this article got posted it was posted with a different title then was original contained in my article. The site owner has now corrected the title.

Greg


Gregory A. Larsen, MVP

Need SQL Server Examples check out my website at http://www.sqlserverexamples.com
Post #1206615
Posted Thursday, December 18, 2014 3:20 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, April 23, 2015 1:49 PM
Points: 45, Visits: 24
Hi Mr. Larsen,

Thank you for the stairway!

It works as is; however, in Listing 5, for naming consistency, shouldn't "FK_Reservation_CustomerPaymentType" be "FK_Reservation_CustomerId"?

Charlene
Post #1645211
Posted Wednesday, May 13, 2015 1:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Today @ 3:00 AM
Points: 40, Visits: 94
I was going to ask the same question!
Post #1684975
Posted Wednesday, May 13, 2015 2:35 PM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: 2 days ago @ 9:28 AM
Points: 8,738, Visits: 10,565
The title change certainly reduced the awfulness, but what I see is a rather sloppy diagram and some code that maiht represent one possinle interpretation of it. What fields are the sources of which pointers? What fields are the destinations? Neither is at all clear.
In what sense can the diagram be interpreted as a relational model? A relational model of some thing has to conform to relational principles, and the only way one can discover that this diagram does is to look at the SQL code provided and assume that the code determines what the diagram means. So the way to implement a relational model in SQL is to have a relational model in SQL and then draw a diagram representing (albeit rather sloppily) the table and constraints structure that that model represents and say that's the model the code was supposed to implement? Which is the cart and which is the horse here?

I realised this is an ancient article, and I should have commented years ago. But someone else commented ealier today, and that drew my attention to it, so I commented now.


Tom
Post #1685262
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse