Each file would be 20-40 K. They will not change once created. I wonder how
the design would impact backups.

--
Arne Garvander
Certified Geek
Professional Data Dude


"Rubén Garrigós" wrote:

> You have to think not only in storing the files inside or outside SQL
> Server.Maybe the most important thing is what are you going to do with the
> files when they are stored. This is the MOST important thing. You have to
> know your data and its use.
>
> SQL Server is very good searching for data and resolving queries If you
> are going to work a lot with metadata of the images (date, exposure, size,
> and so on) it will worth to have these in the database. You have to think
> about the retention period of the data or if you will use more frequently
> some images or not. The performance for streaming files from SQL Server is
> not as good as NTFS (this is one reason why we have the new FileStream
> datatype in SQL Server 2008 )
>
> It is a big and difficult decision. In our experience SQL Server (prior
> 2008) is better for small files (<1MB) or for files that have metadata to
> query (great performance vs NTFS).
>
> --
> Rubén Garrigós
> Solid Quality Mentors
>
> "Arne Garvander" <ArneGarvander@discussions.microsoft.com> wrote in message
> news:9B426916-74F0-49D2-A4C5-25651C892ED7@microsoft.com...
> >I am using SQL Server 2005.
> > I have the option to store a Tiff image inside SQL Server or In the file
> > system.
> > I have 15,000 images per day. I have the option of storing them in PCL
> > format orTIff format.
> > One of our concerns is convenience of retrieving the file and backing up
> > the
> > file.
> >
> > --
> > Arne Garvander
> > Certified Geek
> > Professional Data Dude
>
>
>