TABLE OF CONTENTS After any reformatting problems have been identified and resolved, loading legacy data to a new database can be accomplished in many ways. Moving data within the same suite of applications is generally straightforward but can become more complicated with each change of operating system, DBMS, or other variation. Although direct input from the user is usually easier, data validation and overall quality control must be considered. This chapter presents some of the most common methods of loading data to a new database as well as the basic concepts of direct user input methods.
By far the easiest method of moving data into a database is by transferring it from another part of the same database or from a directly compatible interpretive application. Even after the database is populated, there will continue to be a need to transfer data into the database either through direct input or from other applications.
Most commercial geoscience interpretive applications provide some element of underlying data management support. The two most popular and widespread application suites from Schlumberger GeoQuest and Halliburton Landmark are discussed here. In general, other application packages generally provide some sort of data transfer capability to one or both of these systems.
GeoQuest Finder . Schlumberger offers a wide range of interpretive and visualization applications intended to share the same underlying data. The underlying data management product, Finder , was originally designed as a map-based database interface that lets the user search, visualize, and transfer selected data to a...
