40. Can the UPLOAD ODBC connector load images directly into a SQLServer/Oracle database column?

Yes. but we don't recommend doing this as the database files may become very big, causing poor database performance and system backups may take too long to complete.  Do this at your own risk!  That said, here is here is how to do it. 

The SQL Server database column must be setup as an 'image' type. The Oracle Server database column must be setup as a BLOB.

Please note if you are using Oracle you must use the Oracle Oracle ODBC driver, not the Microsoft Oracle ODBC driver. The Microsoft Oracle ODBC driver does not support loading images into a BLOB.

1. The 2 SQL statements used to load the document image into the database are similar to the following example.

insert into images (image_number, image_contents) values ('<<IF6>>','');
UPDATE_WITH_IMAGE (select image_contents from images where image_number = '<<IF6>>');

The first statement is used to insert all of the column data except the image into a new row in the database tables that manages the images.

The second statement uses the special prefix UPDATE_WITH_IMAGE. This tells the EzeScan UPLOAD ODBC connectore that the next sql statement will return the unique row that was just loaded so that the image can be inserted in that row.

 OR

2. The 2 SQL statements used to load a zone image into the database are similar to the following example.

insert into images (image_number, image_contents) values ('<<IF6>>','');
UPDATE_WITH_ZONE_IMAGE (select image_contents from images where image_number = '<<IF6>>');

The first statement is used to insert all of the column data except the zone image into a new row in the database tables that manages the images.

The second statement uses the special prefix UPDATE_WITH_ZONE_IMAGE. This tells the EzeScan UPLOAD ODBC connectore that the next sql statement will return the unique row that was just loaded so that the zone image can be inserted in that row.