Complex SQL Benefits - Research Paper Example

Ans # 1The information shall be sourced and processed from the “Customer Details File”. In order to generate a report, a table was created with dummy data. See Appendix-I below containing the Design View & Report generated in MS Access – “Customer Volume by Month”:Ans # 2(1) In case Customer Names/Driver Names require to be printed then a complex SQL Statement will have to be written for each table. The Statement shall logically join the two tables on ID – i.e. ID field in Master & ID field in Detail tables will need to be connected to retrieve the corresponding (Customer/Driver Name) information.(2) It would be very difficult to incorporate “Driver Performance by Month” in parallel with Month of Customer’s total shipments/weights in the Customer Summary Report, especially when different months appear in both tables. (3) A typical SQL Statement will have to be written determining/rating the drivers’ performance on the basis of # of manifests on time and/or delivered late.

It involves calculation + IF and THEN condition statements(4) Driver ID will have to be added into the Customer Table and logically joined with ID field in the Driver Table, to retrieve the corresponding information of Drivers’ Performance.Ans # 3I understand that the Driver Table may be created on a need basis, because the purpose of this table is to get the status of Drivers’ Performance, which is also being recorded/saved into the permanent Customer File.Ans # 4I feel “Driver Performance by Month” in the Customer File is against the concept of table normalization because the drivers’ performance is nothing to do in the Customer Table carrying customers’ transactions.

APPENDEX-I