CIS 515 Week 2 Assignment 2 Database2
Strayer University
CIS-515 assignment2: Database Systems and Database Models
QUE 1:
SELECT Employee.EmpNumber, Employee.EmpFistName, Employee.EmpLastName, EmployeeCommision=Employee.EmployeeCommissionRate*MTPUC AS EmployeesCommision
FROM Employee;
QUE 2:
SELECT Employee.EmpNumber, Employee.EmpFistName, Employee.EmpLastName, EmployeeCompensation=Employee.EmployeeCommissionRate*MTPUC+Employee.yrlySalary+Benefitss AS EmployeesCompensation
FROM Employee
WHERE (Employee.EmpNumber=Employee.EmpNumber);
QUE 3:
Referential Integrity empowers you to support a predictable and accepted database. For instance, in a patient database you may need to guarantee that no patients might be entered into the framework without an extraordinary patient ID. Else, you could wind up with a failure to rapidly record, sort and discover patients who have relating scenes of forethought, arrangements, authentic cases, and so forth.
Similarly, you may need to guarantee that patients with open scenes of consideration, for example, those that are inpatients or are on a holding up rundown can't be erased or changed, on the grounds that such dataprogressions could have a risky impact on your database's honesty.
Whether the issue causes lost or degenerate patient records, whichever way such datacould possibly be left unattached, gliding around your framework with no placeholder or legitimate way. In this manner, without referential trustworthiness you will be left with a database that can't run at an ideal execution level and is at danger from datamisfortune.
Referential Integrity empowers you to administer a predictable and approved database. Case in point, in a patient database you may need to guarantee that no patients could be entered into the framework without an extraordinary patient ID. Else, you could wind up with a failure to rapidly record, sort and discover patients who have comparing scenes of forethought, errands, authentic cases, and so on.
Just as, you may need
CIS-515 assignment2: Database Systems and Database Models
QUE 1:
SELECT Employee.EmpNumber, Employee.EmpFistName, Employee.EmpLastName, EmployeeCommision=Employee.EmployeeCommissionRate*MTPUC AS EmployeesCommision
FROM Employee;
QUE 2:
SELECT Employee.EmpNumber, Employee.EmpFistName, Employee.EmpLastName, EmployeeCompensation=Employee.EmployeeCommissionRate*MTPUC+Employee.yrlySalary+Benefitss AS EmployeesCompensation
FROM Employee
WHERE (Employee.EmpNumber=Employee.EmpNumber);
QUE 3:
Referential Integrity empowers you to support a predictable and accepted database. For instance, in a patient database you may need to guarantee that no patients might be entered into the framework without an extraordinary patient ID. Else, you could wind up with a failure to rapidly record, sort and discover patients who have relating scenes of forethought, arrangements, authentic cases, and so forth.
Similarly, you may need to guarantee that patients with open scenes of consideration, for example, those that are inpatients or are on a holding up rundown can't be erased or changed, on the grounds that such dataprogressions could have a risky impact on your database's honesty.
Whether the issue causes lost or degenerate patient records, whichever way such datacould possibly be left unattached, gliding around your framework with no placeholder or legitimate way. In this manner, without referential trustworthiness you will be left with a database that can't run at an ideal execution level and is at danger from datamisfortune.
Referential Integrity empowers you to administer a predictable and approved database. Case in point, in a patient database you may need to guarantee that no patients could be entered into the framework without an extraordinary patient ID. Else, you could wind up with a failure to rapidly record, sort and discover patients who have comparing scenes of forethought, errands, authentic cases, and so on.
Just as, you may need