attribute

QUESTION 6 The attributes made up of more than one single attributes are called     Single Value     Composite      Multi-value     Derived

a) Referring to the company database, which relations have the same set of attributes for their default superkey and primary key? b) Referring to the company database, which relations have a reasonable candidate key that is not its primary key? C) Referring to the company database, specify an update operation to the department relation that will violate a primary key constraint constraint. D) Referring to the company database, what constraints to the database would be violated if Smith were deleted from the employee relation? Include the relevant relations and attributes in your answer.

What considerations should be taken into account when deciding on the data type for an attribute?

What is the relationship between the primary key of a relation and the functional dependencies among all attributes within that relation?

StayWell also rents out properties on a weekly basis to students attending summer school in the Seattle area. Design a database to meet the following requirements, using the shorthand representation and a diagram of your choice. For each student renter, list his or her number, first name, middle initial, last name, address, city, state, postal code, telephone number, and e-mail address. For each property, list the office number, property address, city, state, postal code, square footage, number of bedrooms, number of floors, maximum number of persons that can sleep in the unit, and the base weekly rate. For each rental agreement, list the renter number, first name, middle initial, last name, address, city, state, postal code, telephone number, start date of the rental, end date of the rental, and the weekly rental amount. The rental period is one or more weeks.

Explain why an index is only helpful if the values of an attribute vary enough.

using the design file in the image attached to the question : Normalize the database in the design file Be aware of the possibility of duplicate data. Name in Role and Employee and Emp_Contact_name all refer to the same data. Name and Email in Vendor refer to the Vendor. Assumptions made: An employee works with one or more vendors. An employee may have none or many dependents. An employee may have many roles over the employee's work history and a record should be retained for each role.

Don't copy again and again that is wrong.  Please help me with this question.

using the design file in the image attached to the question : Normalize the database in the design file Be aware of the possibility of duplicate data. Name in Role and Employee and Emp_Contact_name all refer to the same data. Name and Email in Vendor refer to the Vendor. Assumptions made: An employee works with one or more vendors. An employee may have none or many dependents. An employee may have many roles over the employee's work history and a record should be retained for each role. Make sure to have a primary key for each table . Make sure to include the relationships between the tables .