database-normalization

Explain Like I am Five -> How a Primary Key Satisfies First Normal Form

那年仲夏 提交于 2020-07-09 09:55:35
问题 Thank you for your knowledge in advance. I am studying for the Microsoft Technology Exam and one of the practice questions is : Creating a primary key satisfies the first normal form. True or False? I personally think it is False because the first normal form is to get rid of duplicate groups. But there is a sentence in the text (Database Fundamentals, Exam 98-364 by Microsoft Press) that says the following: "The first normalized form (1NF) means the data is in an entity format, which

Is it possible to have more than one foreign key in a normalised database schema?

徘徊边缘 提交于 2020-06-17 14:10:30
问题 Address ( addressID , houseNumber, postcode, roadName, city, county) Reservation ( reservationID , roomNo, leadGuestID, guest2ID, guest3ID , arrivalDate, departureDate, addressID , amountOutstanding) Guest ( guestID , firstName, lastName, adultFlag, telephoneNo, addressID , emailAddress) Room ( roomNo , roomTypeName ) RoomType ( roomTypeName , floor, basePrice, extraAdultPrice, extraChildPrice) The above schema is supposed to be normalised 4NF. But I cannot see how leadGuestID, guest2ID &

database normalization - merge/combine tables

假如想象 提交于 2020-02-07 06:57:54
问题 Please consider the following scenario. We have a 0NF table StudentTeacherTable: StudentName StudentDepartment StudentDepartmentAdd TeacherName TeacherDepartment TeacherDepartmentAdd John CS London Dave Eng, CS Oxford Mike CS London Dave Eng, CS Oxford Chris Eng Oxford Dave Eng, CS Oxford Ideally after normalization I would like to have tables like Student Table: StudentName Department TeacherName John CS Dave Mike CS Dave Chris Eng Dave Teacher Table: Name Dave TeacherDepartment Table:

database normalization - merge/combine tables

孤街醉人 提交于 2020-02-07 06:57:11
问题 Please consider the following scenario. We have a 0NF table StudentTeacherTable: StudentName StudentDepartment StudentDepartmentAdd TeacherName TeacherDepartment TeacherDepartmentAdd John CS London Dave Eng, CS Oxford Mike CS London Dave Eng, CS Oxford Chris Eng Oxford Dave Eng, CS Oxford Ideally after normalization I would like to have tables like Student Table: StudentName Department TeacherName John CS Dave Mike CS Dave Chris Eng Dave Teacher Table: Name Dave TeacherDepartment Table:

Normalize or Denormalize in high traffic websites

浪子不回头ぞ 提交于 2020-01-22 05:30:50
问题 What are the best practices for database design and normalization for high traffic websites like stackoverflow? Should one use a normalized database for record keeping or a normalized technique or a combination of both? Is it sensible to design a normalized database as the main database for record keeping to reduce redundancy and at the same time maintain another denormalized form of the database for fast searching? or Should the main database be denormalized but with normalized views at the

Better way to add extra attributes in RBAC (Role Based Access Control) tables?

断了今生、忘了曾经 提交于 2020-01-16 08:33:33
问题 I have implemented RBAC (Role Based Access Control) tables. I have a requirement to add extra attribute on some roles, like 2nd_pwd attribute in Admin role, address attribute in Customer role. I have done this design, but it violates data integrity. When you removed (let's say) Admin role, you also need to remove admin data from Admin table. So I decided to add trigger for this job. Question: Is there a design for this requirement without trigger but still doesn't violate data integrity? What

Normalizing a variety of properties with similar data types

半腔热情 提交于 2020-01-16 01:52:33
问题 I'm working on setting up a database to house properties related to a game, for example whether or not it supports multiplayer, what genres it is, release dates, etc. It seems like creating two additional tables (genres, genres_data for example) for each category type isn't nearly as dynamic as it could be. My initial thought was to set it up one of two ways... Have a games table with skeletal information, then a properties table to list all the properties, and a third table to contain all