information about a column, the TriggerInfo class to obtain the information about

a trigger, and so on. Furthermore, the metadata information for a given database object is added up in the class representing it. For instance, the TableInfo class

consists of a list of columns, a list of check constraints, and so on. Figure 5-6show the class diagram used in our application.

Figure 5-6 Class diagram that reflects DB2 metadata

Our application only uses a small subset of the DB2 metadata, and each class contains only a subset of the information available for that particular database object. For further details see the source code that can be downloaded from the IBM Redbooks Web site. Refer to Appendix B, “Additional material” on page 267 for the download instruction

5.5.4 Alternatives: DB2 tools

An alternative is to use a migration tool to migrate one database to another. These tools are usually comprehensive and require some manual steps and user interactions. One of these tools are the DB2 Migration Toolkit. The primary purpose of this tool is to migrate a non-IBM database such as Oracle or MSSQL into an IBM database — either DB2 or Informix. However, it is also a possibility to use the DB2 Migration Toolkit for the purpose described in this chapter. You can read more about the DB2 Migration Toolkit at:

http://www-306.ibm.com/software/data/db2/migration/mtk/?S_TACT=105AGX42&S_CMP=M

GST

5.6 Samples overview

In this section we list all the scripts, command files, and Java programs we present in this chapter. We refer to “a script” as a text file containing DDL and SQL statements; “a shell script” as a command file at the operating system level.

Chapter 5. Deploying pre-configured databases

251

Page 265
Image 265
IBM manual Samples overview, Alternatives DB2 tools, 251