Consider the following two tables where employeenum is primary key in both tables. what is the result of combining the two tables? employee (employeenum, lastname, firstname, wagerate, socsecnum, departmentnum) employee (employeenum, lastname, firstname, street, city, state, postalcode)

The result of combining the both tables is:

Employee(EmployeeNum, LastName, FirstName, WageRate, SocSecNum, DepartmentNum, Street, City, State, PostalCode)

Explanation:

Since the EmployeeNum is the primary and it is available in both tables, what happens is that, it will not list the primary key column twice. It will list the primary key first then all the other attribute in the first table followed by the attribute in the second table. And it will take note so as not to repeat attribute that already occur in the first table.

For instance; in this case, besides EmployeeNum, LastName and FirstName also appear in the both tables but only one instance of them were listed in the resulting table.

building and maintaining the topology is difficult and time consuming. the chance of redundant connections is high, which adds to the high costs and potential for reduced efficiency.

explanation: