June 12, 2007 at 2:28 pm
Here is my dilemma...
Currently, we are grabbing images from a WMS Web service that are used as tiles to display on a map. The only problem is that each time the user closes their session and then comes back to the map that they have to download these images all over again. I have been given the task to make this part of our application faster.
What I propose to do is this, when the user comes to the map the server downloads and saves the images to either the hard disk or database, then these images are streamed to the user. Currently, the server grabs the images from the Web service and then streams them to the user.
My question is, eventually the number of images could range in the millions, so would it be more efficient to store the images in any SQL Server 2005 database where I can index the name column (that is actually a unique number that will become my primary key), or directly on the Windows 2003 filesystem. I will not be doing many updates or deletes, just reads and inserts.
June 12, 2007 at 2:47 pm
Most systems I have seen that needs images, have used SQL to store the location on the file system where the images are stored, not to store the images themselves.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply