One of the companies I work for has millions of employees in total, and keeps records on them in several databases that exchange data through flat files. While this system seems to violate the principle of a single source of data, it’s been in place for years and works well. There must be a reason for this replication of data, and for allowing some inconsistency.
 
People almost always expect their cases to be unique and different. A person may fall behind on their insurance or their 401k contributions for reasons beyond their control, and they don’t expect to lose their be

One of the major problems in any organization is the oldest code hasn’t been tested against more newly discovered bugs. VB6, classic ASP, and even COBOL can be vulnerable to more modern flaws like SQL injection. As "Charles" writes on stack overflow,
 
“Non-parameterized dynamic statements are what you need to worry about…for example,
 
STRING "INSERT INTO TBL (a,b,c) VALUES (" X ", "Y ", "Z ")" INTO WSQLSTMT.
 
EXEC SQL PREPARE MYSTMT FROM :WSQLSTMT END-EXEC.
 
EXEC SQL EXECUTE MYSTMT END-EXEC. ”
 

Most large organizations already follow a corporate backup policy. However, for individual develope...

Fully 75% of respondents reported significant problems as a result of defective data. ... Little over 40% of them were 'very confident' in their own data quality.

PWC

Testing mainframe applications, such as CICS screens, for us...

Batch automation is frequently included by both database and operating system vendors; and typically, these two software categories approach the problem differently. Databases on the windows platform, for example, typically offer much greater scripting and control flow than the native Windows task scheduler. Similarly, Unix-based database vendors offer bat...