[Expand]General Information
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]What's Installed
 [Expand]Common Concepts
 [Expand]ASP.NET WebForms Controls
 [Collapse]ASP.NET MVC Extensions
  [Expand]Product Information
  [Expand]Getting Started
  [Expand]Common Concepts
  [Expand]Grid View
  [Expand]Tree List
  [Expand]Card View
  [Expand]Pivot Grid
   Rich Text Editor
  [Expand]Site Navigation and Layout
  [Expand]HTML Editor
  [Collapse]Vertical Grid
    Main Features
    [Collapse]Binding to Data
      Binding to Data via Entity Framework (Code First)
      Binding to Data via Entity Framework or LINQ to SQL (Database First)
      Binding to Large Data (Database Server Mode)
     [Expand]Custom Data Binding
    [Expand]Data Representation Basics
    [Expand]Data Editing and Validation
    [Expand]Focus and Navigation
  [Expand]Data Editors
  [Expand]Docking and Popups
  [Expand]File Management
  [Expand]Data and Image Navigation
  [Expand]Multi-Use Site Extensions
  [Expand]Spell Checker
  [Expand]Query Builder
 [Expand]Redistribution and Deployment
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Report and Dashboard Server
[Expand]eXpressApp Framework
[Expand]eXpress Persistent Objects
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

Binding to Large Data (Database Server Mode)

Expanded Database Server Mode Overview

The MVC VerticalGrid extension supports a specific binding mode designed to work with large datasets. Within this binding mode, data-aware operations (sorting, grouping, etc.) are performed on the database server side, which is why this mode is called database server mode.

In database server mode, the MVC VerticalGrid is bound to a queryable source using the VerticalGridExtension.BindToLINQ method, which allows the VerticalGrid to load data from the queryable source on demand.

When an end-user performs data operations (sorting, grouping, etc.), the VerticalGrid generates smart queries to receive only those records that must be displayed on screen. These requests are passed to the associated queryable source. The queryable source translates these requests into the required queries and executes them. This ensures a quick response and improved performance for large data sources.

For end-users, the MVC VerticalGrid functions identically in regular and server modes. In database server mode, end-users can use an automatic filtering feature to access a specific data range, sort, group and filter data, calculate summaries, etc.

Expanded Binding to Data

Perform the following steps to bind the VerticalGrid to a data source in database server mode.

  1. Add the VerticalGrid to your project

    Add the VerticalGrid to your project, and bind it to a data source in regular mode using the Code First development approach or Database First development approach.

  2. Change the View code

    In the VerticalGrid's View code, use the VerticalGridExtension.BindToLINQ method to bind the VerticalGrid to a data source. This enables binding to data in database server mode.

    Partial View code ("_VerticalGridPartial.cshtml"):


    Enable the VerticalGridSettings.EnableRecordsCache option to reduce the number of calls to a bound data source when the VerticalGrid functions in Database Server Mode. When the VerticalGrid extension functions in regular data binding mode, the VerticalGridSettings.EnableRecordsCache option should be disabled.

Expanded Server mode limitations

In server mode, the MVC VerticalGrid does not have simultaneous access to bound data in its entirety. This imposes some limitations on the VerticalGrid's features that are still available in regular binding mode. see the table below for information on features that have limitations in server mode.

Is this topic helpful?​​​​​​​