Outsourcer 3.0

I took the time of around Thanksgiving to work on Outsourcer 3.0. I have used the feedback I have received to enhance the security and performance of the application. I also addressed one of the known issues and found and fixed an unreported bug.

Administrator Guide


  • The External Tables created by Outsourcer no long contain the username and password for the source connection.
  • Oracle sources now use ALL_% objects rather than DBA_% objects. This means you don’t need to grant DBA or SELECT on the DBA Views in Oracle to use Outsourcer.
  • TRUST authentication is used to start Outsourcer so no password is stored.


  • Oracle connections are now faster and use less memory than with 2.x.
  • New External Table feature for defining a SQL statement to execute in Oracle or SQL Server to be the source of an External Table.
  • Better examples of the job types for Oracle and SQL Server


  • When a job fails and under certain conditions, Outsourcer could leave a database connection open to the source. Outsourcer now properly closes the connection on failed jobs.
  • If multiple jobs executed at the same time, it was possible for more than 1 job to attempt to create the target schema at the same time. This no longer is a problem.

2 thoughts on “Outsourcer 3.0

    1. Jon Post author

      No, it uses External Web Tables. If your data is already only in Oracle or SQL Server, it will be faster to use Outsourcer to load the data than to export the data, move the files to an ETL server, and then load the data with gpload. The reason why is the bottleneck isn’t the loading but the extract from Oracle or SQL Server and writing the data to a file adds more time. Plus, you often times have to clean the files which Outsourcer does for you.

      Read the documentation. It explains how it is done.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.