Files, such as XML documents or “flat files” such as configuration files and comma-delimited text files, are also common sources of legacy data.Software, including legacy applications that have been wrapped (perhaps via CORBA) and legacy services such as web services or CICS transactions, can also provide access to existing information. What type of problems are you likely to experience with legacy data?That isn’t to say that the advice presented below couldn’t be modified for such a situation.
If so, consider yourself amongst the lucky few because the vast majority of developers are often forced to tolerate one or more existing legacy data designs.
Their past experience dealing with similar design problems, as well as their personal relationship with the owners of the legacy data source(s), will prove to be a valuable asset to the project team.
Agile DBAs need to be aware of the problems with the data architecture within your enterprise, information that they will often gain through discussions with enterprise architects.
Agile DBAs will be aware of the potential problems summarized in Table 1 and will work closely with the application programmers to overcome the challenges. Existing data designs, or even new data designs, are rarely perfect and often suffer from significant challenges.
Common data design problems you will likely discover: These design problems may be the result of poor database design in the first place, perhaps the designers did not have a very good understanding of data modeling.