Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Huge Image Databse

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2003-10-08 : 07:59:21
Jimmy writes "I would first like to say that I really appriciate your site I think it is very helpful, but now to the question. I am in the process of setting up an enormous image database with over 10,000 images and of all of those image there is going to be three different resolution to choose from. In having that said do you think the best way to display them would be using a direct url in the field instead of doing the BLOB thing? O and if you have any suggestions on how I should design the database I would really appriciate it this is a first time thing for me.

thanks

Jimmy

....and im using Microsoft SQL Server"

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2003-10-08 : 08:49:30
Be me you, I'd choose the first way of storing..
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-10-08 : 12:37:57
The BLOB thing is highly not recommended. The recommended solution is storing the image on the server and placing the path and file name in the database.

Tara
Go to Top of Page

JimL
SQL Slinging Yak Ranger

1537 Posts

Posted - 2003-10-08 : 13:00:49
Mmmmmm......... 10,000 images at 3 Rez. almost sounds like a porn site.

I go with Tara on this one. I have some the other way and its getting to be a problem.

...... Scratches head.... still having problems getting App to follow stored path myself. But thats Probably my error.



Jim
Users <> Logic
Go to Top of Page

aiken
Aged Yak Warrior

525 Posts

Posted - 2003-10-09 : 01:19:42
Depending on the application, you may not even need to store the path in the DB. For instance, if the images are just going to be sequentially added and you don't need to preserve the filename (like on a porn site, say), you might just use an identity column and then come up with a path scheme whereby the images are stored in /size1/[id].jpg, /size2/[id].jpg, and /size3/[id].jpg.

Getting up to 10K images in a single dir can be ugly, so you might further consider a path structure like /[size]/[int(id/1000)]/[id mod 1000] to keep no more than 1000 images per dir.

Just some additional ideas.

Cheers
-b
Go to Top of Page
   

- Advertisement -