Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

To Database or File System Expand / Collapse
Author
Message
Posted Wednesday, March 27, 2013 2:52 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 6:56 AM
Points: 5, Visits: 69
I was looking for others thoughts on topic of saving pdf to Database or File System. Currently we save all documentation, (PDF), created by our application to Filesystem with PATH stored in Database. That way we can access a copy of the documentation readily to send copies or whatever.....

The problem is the handling of that filesystem "Archive". If you should venture into one of those folders the time the system takes to generate the directory is enormous and "hungry on resource". We are looking at hundreds of thousands of files @ 30-70kb in size.

I ask those with the experience of similar design, is it better to store the pdf in the Database or is it better to store to filesystem. I appreciate the question is a little open ended, but wondering what was the experience of others that started the way we did by saving to Filesystem then converting to Database.

Obviously Database would grow significantly, but Backups and performance may / may not be improved.

Hope question makes sense and appreciate any constructive feedback.
Post #1435798
Posted Wednesday, March 27, 2013 9:48 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 7:06 PM
Points: 7,125, Visits: 12,720
At only 30-70kb each I would look into storing them in the database in a VARBINARY(MAX) column provided the database is the only way people need to access the files directly, i.e. that people do not also need to be able to manage the files at the file system level. If they need to also be able to access the files on disk then what you have might be your best option in SQL 2005. For your issue about loading the directory with so many files, consider implementing a sub-folder structure to keep the files in any one folder down to a manageable size.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1435999
Posted Wednesday, March 27, 2013 10:14 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 18, 2014 6:56 AM
Points: 5, Visits: 69
Thanks opc.three for your thoughts.
We may need to email lost copies and print the PDF, but these are all functions we would have to write. I would envisage sticking the PDF in a seperate Archive DB to teh actual production database as this will cause the Database to grow significantly if we did databse the files.
Access to the Filesystem would reduce to nothing the more we can get "done" within teh database.

Again thank you for your input.
Regards
Post #1436018
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse