Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Changing the Past Expand / Collapse
Author
Message
Posted Tuesday, January 25, 2011 5:31 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, December 16, 2013 7:19 AM
Points: 98, Visits: 226
It depends on who is asking what question. For example: a wrongfully terminated employee (Bob) is reinstated and his personnel record is supposed to be "cleared". If someone runs a report of employees with negative actions, Bob should not appear on report. If someone else runs a report to determine staffing levels on a date between Bob's firing and reinstatement then Bob should not be on the list. If someone wants to run a report of wrongfully terminated employees then like duh, Bob should be on that list.

Some things are done on a timely basis and some are not. Hiring is usually done in real time but separations frequently are not. Before the final check can be cut their leave has to be audited to be sure of how many hours of unused leave must be paid; some companies do not pay final commissions until 30 days later in case a big purchase is returned.

Most times and places preserving the "raw" data in the "historical ODS" but having "corrected" data in the Data Marts works pretty well.
Post #1053034
Posted Friday, January 6, 2012 10:47 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, October 26, 2012 11:50 AM
Points: 5, Visits: 69
My answer? NEVER, well, ALMOST never.

I recently had a very interesting case where changing past data was required. Without going into to many details, the college decided to change all classes from a QUARTER credit system to a SEMESTER credit system. This change was able to be done with no issues EXCEPT for the student transcript details and GPA summaries. Those would have been either very complicated, or downright impossible to correct given that they are generated by a third party software.

Bottom line? We followed suit done by other colleges and changed our historic data so that everything was in semester credits, recording exactly what records were changed along with the original and corrected values. We then put a notation on ALL of our transcripts (bold in a red box) stating that we had made this change as a college and that earlier transcripts would reflect quarter credits instead of semester.

My goal is to avoid historic changes if at all possible. If not, make sure that every change is fully documented, preferably in a table inside the database, so that the change log stays with the database, for the life of the database.


David A. Sousa
Database Administrator
Post #1231609
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse