Log In
[Expand]Welcome to DevExpress .NET Documentation
[Expand]WinForms Controls
[Collapse]ASP.NET Controls and MVC Extensions
 [Expand]What's Installed
 [Expand]Common Concepts
 [Collapse]ASP.NET WebForms Controls
   Getting Started
  [Expand]Chart Control
  [Collapse]Grid View
   [Expand]Product Information
    Getting Started
    [Collapse]Binding to Data
      Connecting ASPxGridView to a Data Source
     [Collapse]Binding to Large Data (Database Server Mode)
       Data Binding to Large Data via EF
       Data Binding to Large Data via LINQ
       Data Binding to Large Data via XPO
       Database Server Mode Limitations
      Built-in Row Caching
    [Expand]Data Representation Basics
    [Expand]Focus and Navigation
    [Expand]Data Editing
    [Expand]Data Shaping and Manipulation
    [Expand]Data Formatting
    [Expand]Master-Detail Relationship
     Appearance Customization
     Save and Restore Layout
    ASPxGridView Designer
   [Expand]Visual Elements
   [Expand]Member Tables
   [Expand]ASPxGridView - Animated Images
  [Expand]Card View
  [Expand]Vertical Grid
  [Expand]Rich Text Editor
  [Expand]Image and Data Browsing
  [Expand]Docking and Popups
  [Expand]Site Navigation and Layout
  [Expand]File Management
  [Expand]Multi-Use Site Controls
  [Expand]HTML Editor
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Data Editors
  [Expand]Spell Checker
  [Expand]Query Builder
 [Expand]ASP.NET MVC Extensions
 [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]Document Server
[Expand]Report Server
[Expand]eXpressApp Framework
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Data Binding to Large Data via XPO

The ASPxGridView supports binding to large data sets via the XpoDataSource component provided by the XPO ORM library. This component fully supports database server mode (i.e., it delegates all data processing to the DB server), and only loads the records to be displayed on screen. This allows you to dramatically increase performance when working with large datasets.

Expanded Binding to Data

To bind ASPxGridView to a dataset via XpoDataSource in server mode, do the following.

  1. Create and customize an XpoDataSource object. At design time, you can find this component in the Toolbox and add it to the page.


    To see an example, refer to Tutorial 5 - An ASP .NET Application for Data Editing in the XPO help documentation.

    For information on generating persistent objects for existing data tables, see the Generating Persistent Objects for Existing Data Tables topic in the XPO help documentation.

  2. Set the XpoDataSource component's XpoDataSource.ServerMode property to true. This enables database server mode.
  3. Bind ASPxGridView to XpoDataSource.
  4. Provide connection settings to the target data store.

In the following demo, you can see for yourself how fast the ASPxGridView control performs various operations (such as sorting, filtering, and grouping), and calculates summaries against 300,000 records in server mode: Data Binding to a Large Database via XPO

Expanded Data Stores Supported in Server Mode

In server mode, the ASPxGridView control uses methods provided by the eXpress Persistent Objects for .NET (XPO) to connect to a data store. It works with all the data stores supported by XPO. These are listed in the following table.

Database Engine Version(s) XPO Data Store Adapter .NET Standard 2.0 Support Database Provider Assembly
Advantage Advantage Database Server v9.1, Advantage Database Server v10.1, Advantage Database Server v11.1 AdvantageConnectionProvider   Advantage.Data.Provider.dll
ASA SQL Anywhere 16, SQL Anywhere 17 AsaConnectionProvider   iAnywhere.Data.SQLAnywhere.dll
ASE Sybase Adaptive Server 12, Sybase Adaptive Server 15.5, Sybase Adaptive Server 16 AseConnectionProvider   Sybase.Data.AseClient.dll
DB2 DB2 9.7.4 DB2ConnectionProvider   IBM.Data.DB2.dll
Firebird Firebird 1.5, Firebird 2.5.7 FirebirdConnectionProvider
MSAccess Microsoft Jet AccessConnectionProvider   System.Data.dll
MSSqlServer Microsoft SqlServer 7.0, Microsoft SqlServer 2000, MS SQL Server 2000 Desktop Engine (MSDE 2000), Microsoft SQL Server 2005,
SQL Server 2005 Express Edition, SQL Server 2008, SQL Azure™ Database, SQL Server 2008 R2, SQL Server 2008 R2 Express, SQL Server 2012, SQL Server 2012 Express (including LocalDB), SQL Server 2014, SQL Server 2014 Express (including LocalDB), SQL Server 2016, SQL Server 2016 Express (including LocalDB)
System.Data.SqlClient 4.4.0 (.NET Standard 2.0)
MSSqlServerCE Microsoft SqlServer 2005 Mobile, SQL Server 2005 Compact Edition (Microsoft SqlServer 2005 Everywhere Edition CTP), SQL Server Compact 3.5,
SQL Server Compact 4.0
MSSqlCEConnectionProvider   System.Data.SqlServerCe.dll 3.5.0
System.Data.SqlServerCe.dll 4.0.8482.1
MySql MySQL Server 4.1, MySQL Server 5.0, MySQL Server 5.1, MySQL Server 5.7 MySqlConnectionProvider
MySql.Data.dll (.NET Standard 2.0)
Oracle Oracle 9i, Oracle 10g, Oracle 11g, Oracle 12c OracleConnectionProvider
Pervasive Pervasive PSQL 9, Pervasive PSQL 10, Pervasive PSQL 11 PervasiveSqlConnectionProvider   Pervasive.Data.SqlClient.dll
PostgreSQL PostgreSQL 7, PostgreSQL 8, PostgreSQL 9, PostgreSQL 10 PostgreSqlConnectionProvider
Npgsql.dll (.NET Standard 2.0)
SQLite SQLite 3 SQLiteConnectionProvider
Microsoft.Data.SQLite 2.0.0 (.NET Standard 2.0)
VistaDB VistaDB 4, VistaDB 5 VistaDBConnectionProvider   VistaDB.4.dll

Note that the database provider assembly versions listed in the table above are the versions that have been tested with the current XPO version. Since XPO loads ADO.NET provider assemblies dynamically, you can use any specific version of the provider.


XPO does not support tables with multi-column (compound) keys or indexes in ASE databases. To avoid exceptions when connecting to ASE databases containing these tables, use one-column keys or indexes.



We do not recommend binding the ASPxGridView control to file-based databases (MS Access and VistaDB). These databases are slow, unlike the transaction speed, data security and integrity of server-based database engines (MSSqlServer).

Expanded Database Server Mode Limitations

In database server mode, ASPxGridView does not have simultaneous access to bound data in its entirety. This imposes some limitations on the grid's features, which are still available in regular binding mode. Please see the following topic for information on features that are not supported in server mode: Database Server Mode Limitations.

Expanded Task Based Help

Expanded See Also

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