help
- From: <Paula_Stankus@xxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 22 Sep 2005 22:55:04 -0400
When we don't get a full data dictionary from a COTS vendor and even
in-house. Then there is no possible way to verify the data especially
when no one knows for certain what field represents what - i.e. the
field names are obtuse or archaic.
In that case as knowledge of that system grows - it becomes clear that
the system is not working perfectly correct the users ask for
corrections. The way the data is stored and various defaults are
changed.
Then at the last minute the users (through looking at their reporting
system) request a massive update.
To me it went wrong when we could not obtain a good data dictionary.
Any thoughts on how to keep from having to make massive updates to data
all in one day?
--
//www.freelists.org/webpage/oracle-l
Other related posts:
