Steelhead Appliance

[mbrockney]

Unfortunately, scanned images like .tiff, are not very optimizable. Even though you are using the same form, two scans of the same form can produce two very different bit patterns. This could be due to differences in lighting from once scan to the next, how the paper was loaded, etc. At the bit level, the images will be very different, hence the inability for data streamlining to see redundant data. Add compression to the mix, and that further obscures the data. You could use the transparent CIFS prepopulation (with built in RCU), to pre-position the data. But this would only be beneficial if users were requesting the exact same image more than once. You would still not get much, if any benefit from one form to the next.

Good luck,

Mike

[apopsis]

We are trying to optimize an MS-SQL application at a customer, where images are scanned, compressed and saved in the MS-SQL DB. When the application clients retrieve the data, although many of the forms are the same, they are not optimized because they are compressed.

If a record is retrieved once that same record is then optimized for all users, but if another record with same scanned form is opened it is not optimized the first time.

If we use RCU to prepopulate all the database files will we get the optimization we need or do we need the MS-SQL rules configured on th SH appliances?

Thank you