Skip to main content

Read from MS SQL BLOB column

In SQL SERVER 2005 the most common data type for storing BLOBs was an IMAGE  datatype. When SQL Server 2008 and later SQL SERVER  2008 R2 occured the image datatypes coexists with several new and recomended by Mictosoft BLOB datatypes such varbinary(MAX). Let`s have a look:


  • varbinary(max) /binary(n) variables store variable-length binary data of approximately n bytes, may store a maximum of 2 gigabytes.
  • image variables store up to 2 gigabytes of data and are commonly used to store any type of data file (not just images).


But when you`re designing a new database structure be patient and choose the newest one type according to the Microsoft note:
"ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead.
Fixed and variable-length data types for storing large non-Unicode and Unicode character and binary data. Unicode data uses the UNICODE UCS-2 character set."
Now it`s time for coding. Asume that You working on a some business application that needs to retrieve a BLOB from the database by using clear ADO.NET. Code below is a simple C#  function which takes two parameters and returning a a new stream which contains BLOB data.


 private Stream ReadBlod(string blobCode, SqlConnection conn)
        {
            //SELECT from BLOB table
            string lSQLFileContent = "SELECT TOP 1 blob_File FROM blob_table WHERE blob_code = @code";
            //Stream for BLOB  object
            Stream lFileStream = Stream.Null;
            using (SqlCommand blobCmd = new SqlCommand(lSQLFileContent))
            {
                //Setting up command
                blobCmd.Connection = conn;
                blobCmd.Parameters.AddWithValue("@code", blobCode);


                //Test and open connection
                if (conn.State == ConnectionState.Closed)
                    conn.Open();


                //EXENTIAL Execution
                using (SqlDataReader reader = blobCmd.ExecuteReader(CommandBehavior.SequentialAccess))
                {
                    reader.Read();
                    long bytesize = reader.GetBytes(0, 0, null, 0, 0);
                    byte[] imageData = new byte[bytesize];
                    long bytesread = 0;
                    int curpos = 0;
                    while (bytesread < bytesize)
                    {
                        //Iteataion by 2kk bytes until EOF
                 bytesread += reader.GetBytes(0, curpos, imageData, curpos, 255);
                 curpos += 255;
                    }
                    //Creating stream from byte array
                    lFileStream = new MemoryStream(imageData);
                }
            }
            return lFileStream;
        }


Thank You.


Using list:

using System.Data.SqlClient;
using System.IO;


More info:

Popular posts from this blog

Full-Text Search with PDF in Microsoft SQL Server

Last week I get interesting task to develop. The task was to search input text in PDF file stored in database as FileStream. The task implementation took me some time so I decided to share it with other developers. Here we are going to use SQL Server 2008 R2 (x64 Developers Edition), external driver from Adobe, Full-Text Search technology and FileStream technology.Because this sems a little bit comlicated let`s make this topic clear and do it step by step. 1) Enable FileStream - this part is pretty easy, just check wheter You already have enabled filestream on Your SQL Server instance - if no simply enable it as in the picture below. Picture 1. Enable filestream in SQL Server instance. 2) Create SQL table to store files  - mainly ther will be PDF file stored but some others is also be allright. Out table DocumentFile will be created in dbo schema and contain one column primary key with default value as sequential GUID. Important this is out table contains FileStream

Playing with a .NET types definition

In the last few days I spent some time trying to unify structure of one of the project I`m currently working on. Most of the changes were about changing variable types because it`s were not used right way. That is why in this post I want to share my observations and practices with you. First of all we need to understand what ' variable definition ' is and how it`s different from ' variable initialization '. This part should be pretty straightforward:   variable definition  consist of data type and variable name only <data_type> <variable_name> ; for example int i ; . It`s important to understand how variable definition affects your code because it behaves differently depends weather you work with value or reference types. In the case of value types after defining variable it always has default value and it`s never null value. However after defined reference type variable without initializing it has null value by default. variable initialization  is

Persisting Enum in database with Entity Framework

Problem statement We all want to write clean code and follow best coding practices. This all engineers 'North Star' goal which in many cases can not be easily achievable because of many potential difficulties with converting our ideas/good practices into working solutions.  One of an example I recently came across was about using ASP.NET Core and Entity Framework 5 to store Enum values in a relational database (like Azure SQL). Why is this a problem you might ask... and my answer here is that you want to work with Enum types in your code but persist an integer in your databases. You can think about in that way. Why we use data types at all when everything could be just a string which is getting converted into a desirable type when needed. This 'all-string' approach is of course a huge anti-pattern and a bad practice for many reasons with few being: degraded performance, increased storage space, increased code duplication.  Pre-requirements 1. Status enum type definition