Skip to main content

Storing BLOB Data: Data Base vs NTFS File System

BLOB/Image/Videos are unstructured data. RDBMS like SQL Server is made to store relational data. File stream is new feature of SQL Server since 2008 to store large data. This is not always the best solution to store images on db. Store the pictures on the file system and picture locations in the database. My previous experience is also saying. Why? Because...


1.       It gives Integrity and consistency @ business layer & application layer.
2.       Data Migration bit easy because it can accommodate other technology like SSIS.
3.       Reading images via Database is faster than slower NTFS Disk because we can index it at Db level.
4.       If objects are under 256 kb in huge number than DB is best.

1.       Putting all of those images in database will make it very, very large. This means DB engine will be busy caching all images. So it can impacting to Relation Data processing.
2.       Dumping data in database means slower backups and other operations.
3.       Slower Data Distribution to various location using any HA Technology (Log ship/Replication).

NTFS File System

a.       File systems are made to store files and are quite efficient at it.
b.      We will be able to serve the pictures as static files.
c.       No database access or application code will be required to fetch the pictures.
d.      The images could be served from a different server to improve performance.
e.      It will reduce database bottleneck.
f.        The database ultimately stores its data on the file system.
g.       Images can be easily cached when stored on the file system.
h.      No server-side coded needed to serve up an image, just plain old IIS/Apache.
i.       If object is  larger than 1 MB on an average than NTFS is best.

1.       There is no direct way to do an INNER JOIN between the product table and your images 
           older to determine what orphaned files you have left.
2.       Integrity may fall in slow network between files and actual data.

To Blob or not to Blob


To Blob or Not To Blob ( .. ..


Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to recover msdb database from suspect mode

 It was Monday 9 th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server. “MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..