Take the community feedback survey now.

Per Magne Skuseth
Jul 30, 2015
  4729
(6 votes)

Updates to EPiCode.SqlBlobProvider

Version 1.3 of EPiCode.SqlBlobProvider is now available in the EPiServer NuGet feed.

In addition to some minor performance improvements, there are a couple of new features:

Cache blobs on disk
If you have a slow database connection or a vast amount of blobs, it would probably be faster to serve the blobs from disk rather than directly from the database. By setting loadFromDisk=”true”, you can do exactly this. This works by automatically caching files on disk when a blob has been requested for the first time. Performance wise, it should be equal to the standard FileBlobProvider. The simplicity and distributional benefits of the provider are still the same.

Files are by default stored in [appDataPath]\\sqlProviderBlobs, but can be configured:

<blob defaultProvider="sqlBlobProvider">
  <providers>
    <add loadFromDisk="true" path="c:\my_custom_location" name="sqlBlobProvider" type="EPiCode.SqlBlobProvider.SqlBlobProvider, EPiCode.SqlBlobProvider" />
  </providers>
</blob>

 

Export SQL blobs
A scheduled job for exporting all existing SQL blobs has been added. The files will be exported to the default (or configured) path.

Jul 30, 2015

Comments

Henrik Fransas
Henrik Fransas Jul 30, 2015 02:16 PM

Great news!

thanks!

Per Magne Skuseth
Per Magne Skuseth Jul 30, 2015 02:29 PM

Kudos to Lee Crowe who came up with the whole caching idea :-)

K Khan
K Khan Jul 30, 2015 03:46 PM

Will this improve bandwidth usage also?

/K

Jul 30, 2015 03:49 PM

Thanks for the Kudos Per ;).  It's good to see that this request has finally made it into the provider.

Per Magne Skuseth
Per Magne Skuseth Jul 30, 2015 04:01 PM

Yeah, sorry it took so long. I've been busy - pushing a stroller instead of pushing code.

Per Magne Skuseth
Per Magne Skuseth Jul 30, 2015 04:06 PM

It should improve bandwidth as well, since it is using a FileStream and not a MemoryStream

Justin Le
Justin Le Jul 31, 2015 04:59 AM

Oh well, fantastic news! Many thanks for the Kudos Per :)

Vincent
Vincent Aug 3, 2015 07:41 AM

Is there any facility that we can use to flush out the cache file?

Per Magne Skuseth
Per Magne Skuseth Aug 3, 2015 11:59 AM

Files wil be deleted when content is deleted, but other than that there is no built flush functionallity. You could delete the main folder on disk though. 
I might add a scheduled job that can do this.

Johan Book
Johan Book Aug 13, 2015 11:50 AM

When I upgraded to latest version, the blob declaration in Episerverframework.config was removed. Is this a known issue?

Per Magne Skuseth
Per Magne Skuseth Aug 20, 2015 11:41 AM

Johan, this is because the episerver.framework files has been moved into a section in web.config.

Per Magne Skuseth
Per Magne Skuseth Aug 24, 2015 10:33 AM

File, not files.

Please login to comment.
Latest blogs
Running Optimizely CMS 12 on .NET 10 in Azure

Upgrade your Optimizely CMS website to .NET 10!

Tomas Hensrud Gulla | Nov 21, 2025 |

Experimentation Evolution with AI (Masterclass Recap)

If you think you are not using AI in your experimentation program you are probably wrong. Ever asked an AI to rephrase a hypothesis or brainstorm a...

Polly Walton | Nov 21, 2025

Effortlessly Configurable Custom Fields for Scheduled Jobs in Optimizely with PlugInProperty

Optimizely CMS lets developers add job parameters—such as textboxes and checkboxes—directly to the scheduled job admin UI using PlugInProperty. Wit...

Ravindra S. Rathore | Nov 21, 2025 |

Optimizely Package Explorer: Now With Extra Superpowers

If you’ve ever opened a .episerverdata file and asked “What is in here?” (guilty as charged) — then this is your moment. We’ve given our open-sourc...

Allan Thraen | Nov 20, 2025 |