KB10566 - What are the SQL database options for generating a SQL based PixelStore image file file? My PixelStore output exceeds the 2 GB size limitation of the default MSJET database engine.

By default the TatukGIS Aerial Imagery Corrector (AIC), GIS Editor, and free Viewer products generate the PixelStore output to the Microsoft JET/Access SQL database, which is limited to 2 Gigabytes. To accommodate the generation of PixelStore image sizes exceeding 2 GB, any of these TatukGIS products can be manually configured to generate the PixelStore output to just about any SQL Server database product, e.g., MySQL, MS SQL, Oracle, DB2, Interbase, etc.

For guidance on how to configure a PixelStore image to one of these other SQL Server database products, refer to Knowledge Base number KB10649.

A second option to circumvent the 2GB MSJET size limitation is to divide the coverage into two or more MSJET based PixelStore files, each less than the 2 GB, with each PixelStore image covering a unique portion of the overall coverage. Then open the multiple PixelStore files as separate layers in a single project.

Note: Microsoft Access may not provide a specific message stating that 2GB limit has been breached. This can make the situation a bit confusing. As a rule, if the process of generating a PixelStore output image to an Access database i) stops without a clear reason why and ii) if the amount of data already written to the PixelStore image file at that point exceeds 1 GB, the Access size limitation is most likely the problem.