Load

Use the load process to prepare the contents of source file (an archive or extract file) for a particular DBMS loader. If wanted, you can also start the corresponding database load utility.

For each table in the source file, the load process generates a data file in the correct format. If you are not using named pipes, the Optim™ solution also generates an SQL or batch execution file that contains the syntax needed to start the database loader.

Specifications for the load process are embodied in a load request. You can name and save the load request in the Optim directory, so that it is available for various users and uses. An unnamed load request can also be embedded in a restore request and you can edit it as part of the restore request. The load request provides parameters that are used to prepare data for a DBMS loader. The load request also provides instructions needed to process the load. A table map is used to map the destination for the data to load. Also, optional column maps transform data before loading.

Load versus Insert

Your Optim solution can move data into a database by loading or inserting. For details on using a particular DBMS loader, see the documentation for your database management system. Also, consider the following when deciding the best method:

Process Files

The Optim solutions generate several types of files to support the database utility load process. If your file server does not support file names of more than eight characters, the load process cannot process a source file with a long name. Do not use long file names for source files or copy and rename a file before you use it for a load process.

As you design or modify a load request, you can use the resource estimator to calculate the storage needed for these files. From the Load Request Editor, click Tools > Estimate Resources to calculate the amount of storage needed for the conversion process and create a Resource Estimation Report. Generally, you might want to run the resource estimator offline or during nonproduction times to prevent possible resource contention issues.

Run online or automate

If you have DBMS authorization, you can run a load request by clicking File > Run or you can schedule named load requests by clicking File > Schedule. You can also run a load request from the command line, whether manually, in batch, or from an external application. When running a command-line process, you can supply overrides to tailor the process to circumstances as they exist at run time.

A load request can also be run as part of a restore request. Also, you can direct the load process to generate the necessary files immediately, but defer running the database load utility. If deferred, the loader must be started manually.

Naming conventions

The fully qualified name of a load request is in the form identifier.name.

identifier
Identifier that serves as the prefix for the request name (1 - 8 characters).
name
Name assigned to the request (1 - 12 characters).

It is helpful to use a logical set of naming conventions to identify the use for each load request and to organize them for easy access. For example, TDMRefresh.AcctsRec.

Section contents

This section explains how to create and maintain a load request, including how to:



Feedback