70-100 Exam

I recently failed the 70-100 exam and I am giving it another try today. I'm aware that calculated fields should not be included as a field but how about the # of something. On the test there was a scenario on an insurance company. The premium is calculated on many fields including the # of Violations. This was listed as one of the fields to choose from. The #of Violations can be derived by doing a count on the driver violations table. Should it be included in the drivers table or would this be considered a calculated field? Also there is a driverflag field that could be used based on the #of Violations for a driver. Should this be added since it is must be derived from the #ofViolations? Help!AnyOne?????
bufordkAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
wsh2Connect With a Mentor Commented:
To make # of Violations a field.. then you must find a way to maintain integrity between the Driver and Violation tables.

ie.. Whenever/whereever a user Adds/Deletes a Violation Record, code must be executed to increment/decrement the Driver.#OfViolations field to reflect the proper count. If an  Add/Delete occurs and the posting is somehow omitted, then the Driver.#OfViolation field count becomes corrupted.. and the error is carried ad infinitum within the Driver record.. in effect referential integrity is lost.. and could only be recovered by a user written synchronization process.

In the question you pose, because of all the additional overhead needed to keep the #OfViolations field / Violations Table synchronized, you arte much better off leaving referential integrity to the guiles of the System. One would be best served by making #OfViolations a calculated variable.. primed with a SELECT COUNT SQL statement.. 'cause then.. what you see.. is what you get.. <smile>.





0
 
wsh2Commented:
Now.. Lets talk the real world.. <wink>.

Depending on how VOLATILE your Violation data is and how precisely you have to know the number of violations (ie.. timing and quantity), summarizing referential information can improve application performance dramatically and greatly simplify data retrieval programming. Yes, referential errors may occur (and hence incorrect output), but one has to balance the risk of this with the value of data accuracy. When working with limited resources, there is some wisdom to the old saying.. "Close enough for Government work".

To greatly reduce the risk of bad data, the developer should always provide easily accessible and/or routinely timed table referential integrity audits.. to assure that the data is accurate at a given moment or predetermined interval. "Good Housekeeping" is a must practice, and a very popular magazine.. <smile>.

0
 
wsh2Commented:
PSsssst.. Let me know how you make out.. k?
0
 
bufordkAuthor Commented:
Thank You ........I Passed!
By a whole......FIVE POINTS!
0
 
wsh2Commented:
Atta B!!!... <huge smile>
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.