The Database-Naming Convention
10/09/14
Marius Ouambo
2520
Mohammed Suleiman
Oak Brook
Unit 3 Assignment 1
There are many database-naming conventions to choose. As I read each of them I wanted to make sure, I got the idea that they were trying to explain for each of the different conventions. Though some of them had, more guidelines than other I still took into account all of the instructions because some of them did repeat each other with certain things.
The convention that made the most sense to me is the views convention because by trying to use less abbreviations and acronyms is helps everyone to understand what you are saying. When you are using imaginative and common sense names then everyone even those who do not know much about will be able to recognize the names. The views convention was short and it made sure there not only was the abbreviations common but also that the prefix could be distinguished from the other conventions. The other ways of diagramming entities and relations is electronic facsimile collections, parametric schema implementation, and FDA. There were many different illustrations that individuals had made using entities and relations yet I felt it was best to keep it to a basic. During my search, I learned that you could use the entities and relations design for numerous things. The things that all three of them have in common are the primary key and the descriptions. In addition, the electronic facsimile collections and parametric schema implementation both have foreign keys. The difference between all three of them is that the parametric schema implementation has a unique type; the electronic facsimile collection has administrative data; and for the FDA it has nulls and varchar.
References
Database Naming Conventions. (2013, September 23). Retrieved October 10, 2014.
Drugs. (2014, October 8). Retrieved October 10, 2014.
Gorman, P. (Ed.). (2004, April 23). Entity Relationship Diagram for Electronic Facsimile Collections. Retrieved
Marius Ouambo
2520
Mohammed Suleiman
Oak Brook
Unit 3 Assignment 1
There are many database-naming conventions to choose. As I read each of them I wanted to make sure, I got the idea that they were trying to explain for each of the different conventions. Though some of them had, more guidelines than other I still took into account all of the instructions because some of them did repeat each other with certain things.
The convention that made the most sense to me is the views convention because by trying to use less abbreviations and acronyms is helps everyone to understand what you are saying. When you are using imaginative and common sense names then everyone even those who do not know much about will be able to recognize the names. The views convention was short and it made sure there not only was the abbreviations common but also that the prefix could be distinguished from the other conventions. The other ways of diagramming entities and relations is electronic facsimile collections, parametric schema implementation, and FDA. There were many different illustrations that individuals had made using entities and relations yet I felt it was best to keep it to a basic. During my search, I learned that you could use the entities and relations design for numerous things. The things that all three of them have in common are the primary key and the descriptions. In addition, the electronic facsimile collections and parametric schema implementation both have foreign keys. The difference between all three of them is that the parametric schema implementation has a unique type; the electronic facsimile collection has administrative data; and for the FDA it has nulls and varchar.
References
Database Naming Conventions. (2013, September 23). Retrieved October 10, 2014.
Drugs. (2014, October 8). Retrieved October 10, 2014.
Gorman, P. (Ed.). (2004, April 23). Entity Relationship Diagram for Electronic Facsimile Collections. Retrieved