Decisions to make before you begin

Before you install the Empirica Healthcare Analysis ETL utility, you must determine the method for transferring data from the source database to the Empirica Healthcare Analysis database. You have the following options. Both options use the Oracle Data Pump technology to transfer the data to the Empirica Healthcare Analysis database.

• Import across a database link.

  A remote database link can save local disk space on the Empirica Healthcare Analysis server. If you have limited space on the Empirica Healthcare Analysis server, consider using this option.

  Keep in mind that ETL activity is subject to network traffic and performance while the ETL execution script runs over a database link. If you experience network latency issues, or if you are running other applications in the destination database, importing across a database link could be a lengthy process.

• Import using export files created by the Oracle Data Pump technology.

  You create the export files at the source instance and move the files to the Empirica Healthcare Analysis database server. Complete this step at your convenience before executing the ETL utility.

  You have the following options for storing the files:

  • Save them on the source server, and then transfer them to the Empirica Healthcare Analysis server.
  • Export the files to an external hard drive and manually move it to the Empirica Healthcare Analysis server.
  • Export the files to a network file location that is accessible to both servers.

  The export files that you create could be very large. Make sure that you have sufficient space for storing the files.

  If you disregard the time spent transferring data files to a locally accessible folder on the Empirica Healthcare Analysis server, a data file import might be faster than a database link import.

  For information about exporting source data, see Exporting source data and making the data files accessible.