which column in the Employee table should you a create a unique constraint?

You administer a Microsoft SQL Server 2012 database. The database contains a table
named Employee. Part of the Employee table is shown in the exhibit. (Click the Exhibit
button.)

Confidential information about the employees is stored in a separate table named
EmployeeData. One record exists within EmployeeData for each record in the Employee
table. You need to assign the appropriate constraints and table properties to ensure data

integrity and visibility. On which column in the Employee table should you a create a unique
constraint?

You administer a Microsoft SQL Server 2012 database. The database contains a table
named Employee. Part of the Employee table is shown in the exhibit. (Click the Exhibit
button.)

Confidential information about the employees is stored in a separate table named
EmployeeData. One record exists within EmployeeData for each record in the Employee
table. You need to assign the appropriate constraints and table properties to ensure data

integrity and visibility. On which column in the Employee table should you a create a unique
constraint?

A.
DateHired

B.
DepartmentID

C.
EmployeelD

D.
EmployeeNum

E.
FirstName

F.
JobTitle

G.
LastName

H.
MiddleName

I.
ReportsToID



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Henk

Henk

C

“One record exists within EmployeeData for each record in the Employee
table.”

This means that each unique row in Employee table is linked to a row in the EmployeeData table. This describes a UID, a PK.

Milen

Milen

No. D is correct – “On which column in the Employee table should you a create a unique
constraint?” you need to define uniqueness not referential integrity between both tables.

Henry Figgins

Henry Figgins

It’s D, but this is a 461 question

Henry Figgins

Henry Figgins

Skip to 110 to resume 463 questions