Databases Reference
In-Depth Information
Chapter 40
A Practical Example
of Data Conversion
Charles Banyay
C
,
ONVERSION
THE
WORD
IS
ENOUGH
TO
DIM
THE
ENTHUSIASM
of most sys-
.
tems developers
The word instills fear in some, trepidation and loathing
in others. Regardless of the nature of the project with which she/he is in-
volved, if there is any conversion effort involved, the reaction is the same.
Exclude it from project scope! Let someone else do it! Although some
might suspect that there may be some religious connotation here, and
rightly so, the topic of this chapter is not converting from one religion to
another. Nor is the topic software conversion, although this would be clos-
er to the mark. This chapter deals with the various forms of the conversion
of data.
Even if the project promises to be primarily development and/or imple-
mentation, which is usually the dream of most developers. Even if it in-
volves some of the latest state-of-the-art technology, the word conversion
immediately throws a pall over all the luster and glitter, and hopes of an in-
teresting endeavor. Most systems implementations involve some form of
conversion. When the software changes, the data model or the data itself
often changes with it.
For some reason, conversions have come to be associated with the mun-
dane, boring, and tiresome aspects of systems implementation. Most de-
velopers would consider conversion efforts as boring, tiresome, and
devoid of interesting challenges, when compared to the implementation of
state-of-the-art technology.
This is a misconception in many instances. Conversion efforts can be as
challenging as any state-of-the-art technology. They can exercise the most
creative abilities of technology professionals. An entire chapter probably
could be devoted to discussing the possible reasons behind the general
lack of enthusiasm for the conversion effort. This chapter, however, will fo-
cus on examining the following:
Search WWH ::
Custom Search