Base64 takes 160% Size, that means to store 100 bytes, you will need 160 bytes, so 60% extra overhead. If you consider time of encoding/decoding, it will consume more CPU time. You can send Base64 and expect clients to decode it, but even in that case, if client is a mobile device, then cpu on mobile will eat more battery. We are storing millions of files, and after nearly 5 years of research, everything listed here is the only best option we have that we can easily deploy and manage with limited manpower and limited knowledge of simple ASP.NET and Database access.

I’ve a question.

If we save files like (.doc, .swf, etc..) we need to save this as Binary data. Would it be a performance intensive which needs the data conversion while serving this request? In case of file system i don’t it need conversion, i assume its a direct access to the file with out any conversion.

Hope my question make sense.

i was really looking for the comparison about the file saving in database or file system but could not find any good resource on the internet, but i am fortunate in this morning to see your article. it is really beneficial for me and my organization to take decission, because we handle very huge data.

Regards,
Ghazanffer Javaid

I read your article with great interest. You make some very valid points about the disadvantages of a file system, and considering the number and size of the files that will have to be stored in the system I’m currently working on, database storage is definitly the way to go. I’d like to point out however that Windows Vista SP1 / Windows 2008 and up support transactions (see Wikipedia).