Printable View
Hi guys,
I have 15,000 icons on my pc and as you can imagine searching, managing and backing these up is starting to become a nightmare. They are currently stored in folders as im sure most peoples are.
I am in the middle of mocking out an application that will allow me to work with my icons easier and wanted to know if a database setup would be a better option.
So basically my question is based on 15,000 icons which setup would be better. Database or file structure.
Thanks
Hey,
In my opinion, you would want to keep the folder structure that you have in place, but what you might want to do in keep the location of the icon in the database. That way you still have access to the icons on the file system when you need them, but you can easily search for and find an icon that you want by searching a database based on keyword, subject etc.
Gary
I was thinking of that but IMOO that is a large amount of redundancy when I would store the icon itself in the DB.
I can think of no reason not to put the images in the database.
Store the images as VarBinary(max) datatypes in the database.
Or use MS SQL 2008 Express where they have a new datatype of FileStream - I've not used it yet but that might be a match for what you are doing.
My reasoning was simply what would be the point of having a database that stores information on an icon and then have a file system that stores the icon itself. A database is one entity that can be managed easier that a mass of folders.
Does a database store images and information more efficiently than a file structure in terms of memory?
The reason that I suggested that, was mainly based on the fact that I chose to store all the photos for my website on the file system, and not in the database, mainly because there are a lot of photos, and I didn't want the database to get too bloated. With icons I guess it would be different, since they are much smaller in size.
Gary
I was agreeing with you ;)Quote:
Originally Posted by szlamany
Yes, yes - put the icon into a field in a database table. Put a couple of other fields in that row that describe nicely - maybe even a field to put keywords into.
Then you can easily create an app - even a webpage - to display and/or extract them. Sort then - select on ranges of keywords...
Putting images and icons into a DB is a really good idea.
Putting them into a DB gives you a single method of saving and backing them up - and even sharing them with the folks here :bigyello:
We've got 10,000+ photos of students in a DB at one of our customer sites - MS SQL server can handle it...Quote:
Originally Posted by gep13
Sorry, im knackered. I need to go to bed. Super, il do that so (after I teach myself how to use datbases). Thanks!
What about SQL Server Express though? That is what I am using for my personal site.
Sorry for hi-jacking your thread Dean, just interested in the answer :)
There is a 4GB limit to the size of a single MS SQL 2005 Express databaseQuote:
Originally Posted by gep13
http://www.microsoft.com/sql/prodinf...-features.mspx
But I just spent 10 minutes looking around MSDN and it appears that the size limit has been removed with MS SQL 2008 Express
http://msdn.microsoft.com/en-us/library/ms165588.aspx
And of course it has this new FileStream datatype - made specifically for doing things like we are discussing here.
Hmm, interesting.
One of the main reasons that I chose to do it this way was because I was wanting to store the full resolution images. I have just checked, and currently all the files come to just over 3GB. Which is close to the limit of SQL Server Express 2005. Will have to check out SQL Server Express 2008, and see what can be done with that.
Thanks for the info!!!
Gary
I still cannot get a firm answer on whether 2008 express has that file limit of 4gb...
But you could always have just two DB's if you did reach 4 gb...
I cannot imagine how useful the FileStream datatype would be in MS SQL 2008 if there was a limitation on database size - maybe the filestream data partition is excluded from that limitation...
If I find out more info I will get back to you all!
Thank you very much!!!
It isn't made particularly easy to find, but 2008 Express has got the 4GB limit:
http://www.microsoft.com/sqlserver/2...ecialized.aspx
I have no idea whether the FileStream is affected by that limit.