Are this database design (ERD) IS true for the following table
-
I have table for instructor in university This center give courses for programming language specialized to Microsoft product this interface as following in image . Simple File Sharing and Storage.[^] SQL,c#,access,c++ courses that given by center D(4),G(2),G(5),G(6),G(3) is sections B.A ,I.S is departments of year in university university consist from 4 year as following department as (INFORMATION SYSTEM (I.S) OR BUSINESS ADMIN(B.A)OR TRADE ENGLISH (T.E) I make ERD design as following : This ERD for interface above Can you tell me are this design is true for table above . Simple File Sharing and Storage.[^]
-
I have table for instructor in university This center give courses for programming language specialized to Microsoft product this interface as following in image . Simple File Sharing and Storage.[^] SQL,c#,access,c++ courses that given by center D(4),G(2),G(5),G(6),G(3) is sections B.A ,I.S is departments of year in university university consist from 4 year as following department as (INFORMATION SYSTEM (I.S) OR BUSINESS ADMIN(B.A)OR TRADE ENGLISH (T.E) I make ERD design as following : This ERD for interface above Can you tell me are this design is true for table above . Simple File Sharing and Storage.[^]
DayNo => DayID in section is probably not a good idea. Instead of using ID for every primary key use tablenameID, sql server will do a lot more work for you. The structure looks ok.
Never underestimate the power of human stupidity RAH
-
I have table for instructor in university This center give courses for programming language specialized to Microsoft product this interface as following in image . Simple File Sharing and Storage.[^] SQL,c#,access,c++ courses that given by center D(4),G(2),G(5),G(6),G(3) is sections B.A ,I.S is departments of year in university university consist from 4 year as following department as (INFORMATION SYSTEM (I.S) OR BUSINESS ADMIN(B.A)OR TRADE ENGLISH (T.E) I make ERD design as following : This ERD for interface above Can you tell me are this design is true for table above . Simple File Sharing and Storage.[^]
The instructor table looks a bit odd to me, having both
IDandInstructorIDI would assume you meantInstructorIDandInstructorName. And as an addition to what Mycroft said, in a fully normalized database you always use the same name for an entity throughout the database. It's not just a good idea, it's a standard[^]. And just like Mycroft said, for a surrogate key, using + "ID" is a good ideaWrong is evil and must be defeated. - Jeff Ello
