Re: Long Raw field in table

In article <2lnc36$daq_at_ucunix.san.uc.edu>, baljepsu_at_ucunix.san.uc.edu (Sailaja U Baljepalli) writes...
>I was wondering if anyone out there has experienec with long raw
>columns in tables. We created a table with one long raw column to
>store binary information. The problem is that any activity on that
>table takes an enormous amount of time. For example if we do a select
>count(*) via sqlplus when the table has about 50 rows, it takes almost
>5 minutes for the query to come back !
 ..
>Thanx
>Sailaja Baljepalli
>baljepsu_at_ucunix.san.uc.edu
>

Reprinted without permission:

      From: ddruker_at_agsm.ucla.edu (Daniel Druker)
      Date: 23 Feb 93 13:39:31 PST


      I recommend HIGHLY that you break your image data out into a seperate
      table from the data used to index each image. That is, if there are 15
      fields that describe your  image, and you want to be able to do a select
      on some set of criteria to bring up the image, make 2 tables -
      1 with the 15 columns + an image id #, 1 with the image id# and the
      image.

      This will save you lots of headaches and will greatly speed up your
      queries if you ever have to do table scans against your criteria.