By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,567 Members | 1,056 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,567 IT Pros & Developers. It's quick & easy.

File Storage- Asp.NET app

P: n/a
Hi,

Is it better to store files in Database or to store on Hard Disk /network ?

On a Web application using .NET...
Aug 3 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Are you talking about attachements. I don't see any benefit of storing them
into the database other than
1) a central location
2) security from careless viewing of content
3) reduce dependencies

typically what I do is create records in database tables that refer to the
attachements and folders and physically store the files in a File Share. I
store about 5000 files per folder, that way I don't have to worry about too
many files in one folder. That ssaid you will have to maintain the path and
along with the FileName in the database.

Do you have an estimate on the amount of files you are expecting.

Regards,

Trevor Benedict R
MCSD

"SSUK" <SS**@newsgroups.nospamwrote in message
news:A7**********************************@microsof t.com...
Hi,

Is it better to store files in Database or to store on Hard Disk /network
?

On a Web application using .NET...

Aug 3 '06 #2

P: n/a
If programming was that easy, we wouldn't have jobs.

"Better" is relative. It all depends on the type, size, quantity, security
implications, etc etc etc. On the balance, it will be much easier to store
the files on disk than in a database, imho. If you're fresh to the scene, go
that route.

"SSUK" wrote:
Hi,

Is it better to store files in Database or to store on Hard Disk /network ?

On a Web application using .NET...
Aug 3 '06 #3

P: n/a
Hello SSUK,

I agree that it's hard to say which one is absolutely superior to the
other. You need to estimate the performance of disk I/O accessing and
database accessing on your server machine. Based on my experience, for
server-side application such as ASP.NET web application(which may suffer
high volume concurrent requests), disk I/O access is quite expense and we
should avoid large number of concurent disk I/O processing. Using database
as storage can take advantage of those querying and maintenance features in
the DBMS, one drawback of database storage is that we need to rely on the
DBMS interface to transfer or backup data since all the files are storaged
as binary data into DB storage.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Aug 4 '06 #4

P: n/a
Thanks for your responses.
"Trevor Benedict R" wrote:
Are you talking about attachements. I don't see any benefit of storing them
into the database other than
1) a central location
2) security from careless viewing of content
3) reduce dependencies

typically what I do is create records in database tables that refer to the
attachements and folders and physically store the files in a File Share. I
store about 5000 files per folder, that way I don't have to worry about too
many files in one folder. That ssaid you will have to maintain the path and
along with the FileName in the database.

Do you have an estimate on the amount of files you are expecting.

Regards,

Trevor Benedict R
MCSD

"SSUK" <SS**@newsgroups.nospamwrote in message
news:A7**********************************@microsof t.com...
Hi,

Is it better to store files in Database or to store on Hard Disk /network
?

On a Web application using .NET...


Aug 4 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.