Jay Lazarus wrote:
>
> > >Can I do this using SQL Server? My user is probably not going
> > >to be able to afford something like the Oracle Workgroup Server
> > >and would need to run it off of Windows NT or 95. What DBMS's
> > >are affordable enough for a small user community of 5 or so
> > >people?
> > >
>
> You can certainly do it with any brand product that supports blobs,
> but when the question of scaling size upwards arises, watch out.
>
> For a system with several thousands of images (jpegs and gifs),
> MS-SQL worked fine for us. Without some serious-er horsepower
> underneath it (not our puny P100 box), I'd not suggest it
> for the 2e6 image database mentioned earlier in this thread...
>
> > >What format should the image data be stored in (.jpg, .gif, .tif,
> > >....)?
>
> You're trading speed for accurancy here. tiffs don't lose content,
> but are far bigger to store an equivalent image than the jpeg/gif
> options. Can your viewers tolerate some distortion? If so,
> avoid tiff and take your savings to the speed bank. If not, better
> get a bigger hardware budget (for more cycles, memory buffers, faster
> disk & network controllers, faster spindles, etc).
If you are doing business documents which don't need color, use group
III fax compression. It is very fast and many business scanners (such as
those made by Ricoh, Fujitsu, and Kodak) will be able to do the
compression in hardware at scan time. This will reduce the average page
of a business letter which will scan to about 1 meg down to about 30k.
Don't use .gif or .tif for anything serious. These were early
implementations of compression and do not work nearly as well as jpeg or
mpeg.
Received on Fri May 23 1997 - 00:00:00 CDT
