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 developers, maintaining local backups before major changes can be critical in avoiding the embarrassment of calling an IT manager for help. Every developer has their own way of accomplishing this; while local backups are necessary, their actual implementation is a matter of taste. If accuracy and ease of restoration is the primary concern, full backups may be taken and stored locally. If space is a concern, differential or record-level backups may be taken.

Testing mainframe applications, such as CICS screens, for usability is significantly different than ...

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

Batch automation is frequently included by both database and...

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 inconsi...