Unit 3 Research Assignment

I’d say that the SQL Server database-naming convention makes the most sense to me. The database name accurately reflects the database content and all database names must be prefixed with the originating components acronym. The file names match the database name and the table names should accurately reflect the table’s content and function. Each column name must be unique within its table. Guidelines and best practices should be followed as a general rule, but it is understood that exception situations may exist. Developers must be prepared to provide a justification for any exceptions. There are no right and wrong answers for naming conventions as far as I am concerned. It’s all down to factors such as existing naming conventions in your applications and personal preference. I think the most important rule to adhere to is to be consistent. People may argue about whether to have underscores in object names or whether you should have proper case but it doesn't really matter as long as everything adheres to the same set of rules. If you have an existing set of objects then I'd suggest trying to match what is already in place. Of course, it’s also good to ensure names are logical!

Also called an entity-relationship (ER) diagram, a graphical representation of entities and their relationships to each other, typically used in computing in regard to the organization of data within databases or information systems. An entity is a piece of data-an object or concept about which data is stored.
A relationship is how the data is shared between entities. There are three types of relationships between entities:
1. One-to-One
One instance of an entity (A) is associated with one other instance of another entity (B). For example, in a database of employees, each employee name (A) is associated with only one social security number (B).

2. One-to-Many
One instance of an entity (A) is associated with zero, one or many instances of another entity (B), but for one instance of entity B there is only one instance of entity A. For example, for a company with all employees working in one building, the building name (A) is associated with many different employees (B), but those employees all share the same singular association with entity A.

3. Many-to-Many
One instance of an entity (A) is associated with one, zero or many instances of another entity (B), and one instance of entity B is associated with one, zero or many instances of entity A. For example, for a company in which all of its employees work on multiple projects, each instance of an employee (A) is associated with many instances of a project (B), and at the same time, each instance of a project (B) has multiple employees (A) associated with it.