The Art of SQL Server FILESTREAM - Red Gate Software

Chapter 2: Getting Started with FILESTREAMLoading the content to the VARBINARY(MAX) variable is unnecessary in the aboveexample. This additional step was added to make the code easier to follow. Listing 2-19shows another version of the code that does not use a staging variable, but instead insertsthe data directly into the table.-- Insert the data to the tableINSERT INTO Items( ItemID ,ItemNumber ,ItemDescription ,ItemImage)SELECT NEWID() ,'MS1001' ,'Microsoft Mouse' ,CAST(bulkcolumn AS VARBINARY(MAX))FROM OPENROWSET(BULK 'C:\temp\MicrosoftMouse.jpg', SINGLE_BLOB) AS xListing 2-19:Loading a disk file directly into a FILESTREAM column.So, where did the data go? Well, the data we just loaded into the FILESTREAM columngoes to the FILESTREAM data container. The exact content of the source file is copiedto the correct location within the FILESTREAM data container; when SQL Server storesBLOB data in the FILESTREAM data container, an exact copy of the original binary chunkis stored in the file system. SQL Server does not change the content; nothing is added,modified, or removed. Also, there is a specific location for every FILESTREAM column inthe database. Listing 2-20 shows the file system map.C:\|-ArtOfFS\|-Demos\|-Chapter2\|-NorthPole_fs\-- Filestream Data Container|-$FSLOG\-- Log Folder|-filestream.hdr -- Metadata File|-5a032731…dfeff9\ -- Root folder for "Items" table|-e943c1e6…5fc1f5\ -- Folder for "ItemImage" columnListing 2-20:Sample FILESTREAM data container structure.75