>>>>Hi,
>>>>
>>>>In VFP I would never store files (like PDF/DOC) in a table, however, now that I am using SQL Server I have been using the FILESTREAM features to store the files. Works fine and super fast for me, although the table with the files is almost 8GB now. Another developer is now needing access to these files and is suggesting that we don't use the filestream as "it's always a bad idea to store files in a database" and "the table is getting too big" and "accessing the files is too slow".
>>>>
>>>>What is your opinion?
>>>
>>>If you have a lot of files that need to associate with SQL records, filestream works very well. It gives you SQL security w/o performance degradation or database bloat.
>>>
>>>The other developer should do some reading.
>>
>>Thanks William,
>>
>>why does the table that stores/references the files get so big?
>
>?? I haven't noticed that.
>
>If it's the table, have you tried SHRINKing it (in case you have a pile of wasted space for some reason)?

No, I have read that shrinking databases is not a god idea.

From my reading it seems that the table appears to have the file stored within it, hence the apparent size of the table, but that is just smoke and mirrors.