I have an application that stores images in a database.
Now I have learned that this isn’t the best way to do this because of performance.
I’ve started extracting all the “blobs” out of the database and added them (through a virtual folder) into the data folder
the problem is that I allready have 8000 blobs stored and if I put them in the folder like this “data/< blobid >/< blobname.extension >” this folder will contain to many folder to be manageable.
I was wondering how you can store your files the best?
group them in dates of creation like this “data/< year >/< month >/< day >/< blobid >/< name >”.
I also have to add that our files are stored in a tree in the database.
I was wondering if I should map that treestructure to the filesystem, the only problem there is that you can move branches. That would mean that I have to move the branches on the filesystem.
Any help is welcome.
Grtz,
M
What version of SQL Server are you using? Because if you are using 2008 you can use the FILESTREAM datatype to store images. This is just as efficient as storing them on the filestore but without any of the associated hassle. See Getting Traction with SQL Server 2008 Filestream.