What method or script I should notice if MS-SQL is no problem on accessing
photo-typed data.
Thanks any way!
Wilbertsorry, not following you there I'm afraid, can you clarify your question?
j|||Sorry for my poor English. I am from Taiwan.
Actually I have seen the artiles you posted on this Forums.
And thank you again for looking at my question.
Ok, I try my best to clarify my question.
I want to make a webpage which connects to a DB in order to for user upload or download image data from DB.
Primaryly I want to take advantage of DB to manage image data instead of a file folders created at purpose for storing image data.
That's all
Thank you, Atrax|||ah, I see. . I thought youmight mean this but wasn't sure.
my usualy advice is don't store image data (or other potentially large binaries) in SQL Server unless you have a very, very good reason. 99 times out of 100 it's better to store the image itself as a file, and then store the path to the file in the SQL Server. Storing a lot of image data can bloat your database rapidly, is more work to display (hence more strain on the server) and less easy to move around.
this isn't to say it can't be done - I've done it in the past - but it IS to say usually it's not such a grand idea. Have you got a good reason to do so?|||Actually that advice is out of date. It was still true to some extent for SS7 but MS did a lot of work to optimize SS2K for storing binary data. I think it was in response to other database engines that do it efficiently.
There should be an architectural reason to store binary data or to avoid it. But it just doesn't drain SQL Server like it used to.
Don|||storage isn't as bad as it used to be, but pulling data backwards and forwards, as you probably would - is less efficient. that's the major reason.|||Well,
First of all, I have to say in advanced that I am new to coding with vb.net even the
MS-SQL. For the security issue and efficiency in management of data ,
using folders or DB to stroe image data , which way is better? and Why?
Thank you all,
Wilbert|||That's hard to say. It really is an architectural decision that depends on the requirements of your app.
First, what is the security issue? Are you trying to protect the binary images or the other data in the database? Do you want to control access to the images? You can do that using Windows file system security. What is required for your application?
The answer to what is most efficient depends on how you're using the images. Are they in constant use, or might a particular image be accessed only once a year? How large are they? How many are there? Do you have to store a lot of information with them in the records?
Tell us more about your application and we'll try to give you more specifics.
Don|||Hi donkiely,
In my work place, one of my job now is to post the image to our website
and keep the imformation up to date. For this website just start, the data now is not huge.
These image are photoed from newspapers. We will find news related to my company on newspaper. If there are news which are suitable for posting to our website. I take it down.
We are setting these thing to record what thing happen in our company.
Sometime I will just take one picture a day and sometime I also could take more 10 pictures a day. Something I am sure that the quantity will go up quickly.
As the information above, Can it give you a picture or architectural thing that might
help my question.
With Regards
P.S. Please be patient of my poor English.
Wilbert|||Hi Wilbert,
That sounds like a reasonable use of images in the db, based on your description.
Here's an article that will give you the details.
Don|||Thank you, Donkiely
No comments:
Post a Comment