smithsson68@gmail.com
Jun 9, 2010
visibility 11964
star star star star star
(2 votes)

Best (and fastest) ways to load items from the Dynamic Data Store

There are essentially 4 ways to load items from the Dynamic Data Store, depending upon what information you have and what you want back in response. Below I am going to detail the methods in (probable) speed order. Note the speed order depends how many items are fetched from the store.

Load

Usage Scenario: Load a single item using its id.

If you have the Identity of an item (or at least it’s Guid part) then this should be by far the fastest way to load a single item.

Example:

Identity id = ObtainId();
DynamicDataStore store = DynamicDataStoreFactory.Instance.GetStore(typeof(MyType));

if (store != null)
{
    MyType obj = store.Load<MyType>(id);
}

If the item is already in the DDS cache then then no database hit is required at all.

Find

Usage Scenario: Load one or more items that directly match one or more name/value pairs, without paging.

Example 1: Single match criteria

DynamicDataStore store = DynamicDataStoreFactory.Instance.GetStore(typeof(MyType));

if (store != null)
{
    IEnumerable<MyType> items = store.Find<MyType>("MyIntProperty", 34);
}

The ids of the matching items will be read from the database and then each item either read from the DDS cache or from the database. This is faster than using Linq because expressions are not used and a direct SQL statement can be generated and executed.

Example 2: Multi match criteria

DynamicDataStore store = DynamicDataStoreFactory.Instance.GetStore(typeof(MyType));

if (store != null)
{
    IEnumerable<MyType> items = store.Find<MyType>
    (
        new Dictionary<string, object>()
        {                    
            {"MyIntProperty", 34},
            {"MyStringProperty", "SomeValue"}
        }
    );
}

Linq (Items)

Usage Scenario: Load one or more items with complex parameter matching and paging. Items can also be projected into new types.

Example:

DynamicDataStore store = DynamicDataStoreFactory.Instance.GetStore(typeof(MyType));

if (store != null)
{
    var query = from item in store.Items<MyType>()
                where item.MyIntProperty > 33 &&
                item.MyStringProperty.Contains("omeval")
                select item;

    IEnumerable<MyType> items = query.Skip(100).Take(25).ToList();
}

The ids of the matching items will be read from the database and then each item either read from the DDS cache or from the database.

LoadAll

Usage Scenario: Load all items from a store without paging

Example:

DynamicDataStore store = DynamicDataStoreFactory.Instance.GetStore(typeof(MyType));

if (store != null)
{
    IEnumerable<MyType> items = store.LoadAll<MyType>();
}

The ids of the matching items will be read from the database and then each item either read from the DDS cache or from the database. If all items are required from a store then this should be marginally faster than using the Linq (Items) methods as LoadAll does not use expressions and a direct SQL statement can be generated and executed.

For loading items back as PropertyBag or types other than the type that was saved see my blog post about Data Container Indifference

Feedback and comments are as always very welcome.

Jun 09, 2010

Comments

Sep 21, 2010 10:33 AM

Very nice to see the different methods.
Is there a way to see all the different datastores that exists?

If you don't want to hardcode the property names like this
store.Find("MyIntProperty", 34);
you could use
store.Find(MembersOf(s=>s.MyIntProperty), 34);

public static class MembersOf
{
public static string GetName(Expression> expr)
{
var node = expr.Body as MemberExpression;
if (object.ReferenceEquals(null, node))
throw new InvalidOperationException("Expression must be of member access");
return node.Member.Name;
}
}

/ Anders Hattestad

Sep 21, 2010 10:33 AM

MembersOf.GetName(s=>s.MyIntProperty)
/ Anders Hattestad

Frederik Vig
Frederik Vig Sep 21, 2010 10:33 AM

@Anders: EPiServer.Data.Dynamic.StoreDefinition.GetAll();

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |