database design is the process of producing a detailed data model of a database. this logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a data definition language, which can then be used to create a database. a fully attributed data model contains detailed attributes for each entity. the term database design can be used to describe many different parts of the design of an overall database system. principally, and most correctly, it can be thought of as the logical design of the base data structures used to store the data. in the relational model these are the tables and views. in an object database the entities and relationships map directly to object classes and named relationships. however, the term database design could also be used to apply to the overall process of designing, not just the base data structures, but also the forms and queries used as part of the overall database application within the database management system (dbms).gehani, n. (2006). the database book: principles and practice using mysql. 1st ed., summit, nj.: silicon press the process of doing database design generally consists of a number of steps which will be carried out by the database designer. usually, the designer must: *determine the relationships between the different data elements. *superimpose a logical structure upon the data on the basis of these relationships.teorey, t.j., lightstone, s.s., et al., (2009). database design: know it all.1st ed. burlington, ma.: morgan kaufmann publishers ==er diagram (entity-relationship model)== thumb|320px|a sample entity-relationship diagram database designs also include er (entity-relationship model) diagrams. an er diagram is a diagram that helps to design databases in an efficient way. attributes in er diagrams are usually modeled as an oval with the name of the attribute, linked to the entity or relationship that contains the attribute. within the relational model the final step can generally be broken down into two further steps, that of determining the grouping of information within the system, generally determining what are the basic objects about which information is being stored, and then determining the relationships between these groups of information, or objects. this step is not necessary with an object database. ==design processdatabase design basics. (n.d.). database design basics. retrieved may 1, 2010, from http://office.microsoft.com/en-us/access/ha012242471033.aspx== #determine the purpose of the database - this helps prepare for the remaining steps. #find and organize the information required - gather all of the types of information to record in the database, such as product name and order number. #divide the information into tables - divide information items into major entities o
Database_management_systems Database_theory Databases