Database Systems with SQL - Full Course - Database Systems - Data Discovery, Glossary, and ER Diagrams - APPFICIAL

When designing a database from scratch, database designers will look at old records, Excel spreadsheets, or interview with potential database users to get an idea of what entities, relationships and attributes to put together. Most entities end up being nouns (person, places or things), relationships are verbs (action words), and attributes are nouns that describe the entity. Once all the ideas come together, they make an ER diagram before they start implementing the database. See my other video on ER diagram design. Once you start designing the database, there are some standard naming conventions to follow: - Entity names are singular nouns. For example, Artist, rather than Artists. - Relationships are in the form Entity-Verb-OtherEntity. For example, Artist-Sings-Song, or Album-Contains-Song. Make the verb sound present tense, and not past tense or passive. For example, you don’t want Artist-SangBy-Song, you want it to be Artist-Sings-Song Attribute names have the form EntityQualifierType, such as ArtistFirstName. The qualifier describes what the attribute means. Also you shouldn’t have the table’s name also in the name of an attribute. If you have a Product table, don’t name an attribute ProductName, just call it Name. Then the attribute will be ProductName, rather than ProductProductName, which sounds confusing. When choosing attribute names, they should also be singular, and make sense. If there are several options to choose from when naming an entity, relationship, or attribute, then choose the best one as the one official name. Document all the names of your entities, synonyms, and descriptions in the data glossary or data dictionary. Subscribe to Appficial for more programming videos coming soon. Also, don't forget to click LIKE and comment on the video if it helped you out!