Home
SQL Image Viewer online help Prev Page Prev Page
Introduction
About SQL Image Viewer
Version history
Contact us
User Guide
System requirements
Editor command selection
Exporting large number of images
Reference Guide
Main menu
Connect to Database
Connecting to databases directly without client libraries installed
Connecting to an Oracle database
Connecting to a DB2 database
Options
General options
Thumbnail options
Hex view
The work area
SQL editor
Results
Other binary data
Image viewer
Hex viewer
Export items wizard
Post-processing Office files
Image options
File naming convention
Datetime format specifiers
Command line interface
Parameters, logs and exit codes
Advanced options
CROP option
Troubleshooting
Expired trial
Invalid licenses
Unidentified images or binary data
DICOM images
Hidden Excel worksheets

Exporting large number of images

All images retrieved by a query that you run from the SQL editor is stored in memory. Hence, if your query retrieves a lot of large images, you may run out of system memory and affect the responsiveness of your system.

To avoid this low memory condition, SQL Image Viewer offers the option to stop the retrieval of images when the virtual memory utilization on your system hits a predefined limit. You can adjust this limit using the Options dialog.

memory-1a  

When you want to save images to disk, we suggest that you first retrieve only a small number of images, and check if they are the correct images. When you then start the Export Images Wizard, you can enter a query that retrieves all the images. When SQL Image Viewer runs this query, it does not store all the images in memory, but retrieves them in batches and saves them to disk directly. In this way, SQL Image Viewer will not need to store all the images in memory, and this allows you to export very much more images than can actually fit on your system's memory.

memory-2a

If you are connected to SQL Server databases, you can also adjust the batch size for the new query, which is the number of rows that SQL Image Viewer retrieves from the database each time. The rule of thumb is to use a batch size value that retrieves enough rows from the database that will not adversely affect the system's memory utilization.

If you are connecting to a database using ODBC drivers, look for a setting that prevents SQL Image Viewer from retrieving the entire result set when the query is executed. If that setting is not present, look for a setting that allows SQL Image Viewer to fetch rows from the server on demand. See the example for DB2 servers for further details.