Assignment Requirements 1. Look up other database-naming conventions. Is there one that makes the most sense to you? Explain why. 2. Look for Entity Relation Diagrams. What other ways of diagramming entities and relations did you find? Describe any similarities and differences between them.
Solutions
1. A naming convention is important when working with databases in order to provide a clear structure and format; especially in team environments. By using these conventions the database can be understood by anyone applying these conventions; thus increasing maintainability. These are not rules but guidelines that can be adapted to any working environment. All names should be in camelcase with the first letter in lower case. Separate name parts by using camel case and NOT underscores or spaces. This provides better readability and you will not have to use quotes when doing SQL statements. Prefixes or namespaces are the ONLY parts of names that should be separated by underscores. This defines a clear separation between names and areas. Do not use numbers in names. This is poor design, indicating divided table structures. Do not use dot (.) separator between names, remember use camel casing. This way you will avoid problems when doing SQL statements as fields are accessed using dot notation. It goes without saying, do not use reserved database words in any name. Always try to use names that make sense and are descriptive of their purpose. Avoid abbreviations whenever possible. ONLY use abbreviations that are well known and documented. Avoid acronyms whenever possible. Only use acronyms that are well known and documented. Also, they should all be in uppercase if used. Tables are usually entity you are modeling for persistence. So make sure the names are in proper English and carry natural meanings. These names should make sense and should be descriptive. Avoid acronyms and abbreviations if at all possible. If acronyms are used, then make sure to capitalize them. Abbreviations used should be well known abbreviations and should be camel cased. Avoid using plural names for tables, use singular forms. This will avoid errors due to pluralization of words and also when moving table design to objects or entities. The name should map to the entity it is modeling. Use namespaces for tables whenever grouping is needed. This grouping is a clear separation when working with the tables and can also provide a good basis for security, as you could secure via the namespace. Namespaces should be separated by an underscore and then the name should be camel cased. Do not use prefixes like tbl,db as they are EXTREMELY redundant and useless. All tables should have at least ONE primary key. Columns are usually attributes of an entity you are modeling via a table. So make sure the names are in proper English and carry natural meanings. These names should make sense and should be descriptive. Avoid acronyms and abbreviations if at all possible. If acronyms are used, then make sure to capitalize them. Abbreviations used should be well known abbreviations and should be camel cased. Get used to naming primary or foreign keys with an ID identifier suffix. DO NOT use the column name id to identify a primary key. Be more descriptive, usually looking at the table name. Foreign keys should be prefixed with a capitalized FK_ in order to visually denote relationships and also to avoid ambiguous table selects. After the FK_ the name of the column must comply with our naming conventions. Boolean columns should use the is prefix. Date columns should be suffixed in camel case with the word Date. This is what I found and it makes the most sense because it keeps everything clean-cut and simple. 2. I couldn’t find any other diagramming entities and relations.