System.Data Namespaces


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

The System.Data namespaces contain classes for accessing and managing data from diverse sources. The top-level namespace and a number of the child namespaces together form the ADO.NET architecture and ADO.NET data providers. For example, providers are available for SQL Server, Oracle, ODBC, and OleDB. Other child namespaces contain classes used by the ADO.NET Entity Data Model (EDM) and by WCF Data Services.


The System.Data namespace provides access to classes that represent the ADO.NET architecture. ADO.NET lets you build components that efficiently manage data from multiple data sources.


The System.Data.Common namespace contains classes shared by the .NET Framework data providers.


The System.Data.Common.CommandTrees namespace provides classes to build expressions that make up a command tree.


The System.Data.Common.CommandTrees.ExpressionBuilder namespace provides a command tree API.


The System.Data.Common.CommandTrees.ExpressionBuilder.Spatial namespace contains a class that represent the Entity Data Model (EDM) functions of a spatial.


The System.Data.Common.EntitySql namespace includes the EntitySqlParser class and other support classes. These classes enable you to parse an Entity SQL query string and create a command tree query.


The System.Data.Design namespace contains classes that can be used to generate a custom typed-dataset.


The System.Data.Entity.Design namespace contains classes to generate Entity Data Model (EDM) files and object source code.


The System.Data.Entity.Design.AspNet namespace contains the Entity Data Model (EDM) build providers for the ASP.NET build environment.


The T:System.Data.Entity.Design.PluralizationServices namespace provides classes for changing words from singular to plural form, and vice versa.


The System.Data.EntityClient namespace is the .NET Framework Data Provider for the Entity Framework.


The System.Data.Linq namespace contains classes that support interaction with relational databases in LINQ to SQL applications.


The System.Data.Linq.Mapping namespace contains classes that are used to generate a LINQ to SQL object model that represents the structure and content of a relational database.


This API supports the product infrastructure and is not intended to be used directly from your code. The System.Data.Linq.SqlClient namespace contains provider classes for communicating with SQL Server and classes that contain query helper methods.


This API supports the product infrastructure and is not intended to be used directly from your code. The System.Data.Linq.SqlClient.Implementation namespace contains types that are used for the internal implementation details of a SQL Server provider.


The System.Data.Mapping namespace provides access to the MappingItemCollection and StorageMappingItemCollection classes.


The System.Data.Metadata.Edm namespace contains a set of types that represent concepts throughout the models used by the Entity Framework and a set of classes that help applications to work with metadata. 


The System.Data.Objects namespace includes classes that provide access to the core functionality of Object Services. These classes enable you to query, insert, update, and delete data by working with strongly typed CLR objects that are instances of entity types. Object Services supports both Language-Integrated Query (LINQ) and Entity SQL queries against types that are defined in an Entity Data Model (EDM). Object Services materializes the returned data as objects and propagates object changes back to the data source. It also provides facilities for tracking changes, binding objects to controls, and handling concurrency. For more information, see Object Services Overview (Entity Framework).


The System.Data.Objects.DataClasses namespace includes classes that are base classes for types that are defined in an Entity Data Model (EDM), base classes for the types that are returned by navigation properties, and classes that define attributes that map common language runtime (CLR) objects to types in the conceptual model.


The System.Data.Objects.SqlClient namespace provides the SqlFunctions class, which contains common language runtime (CLR) methods that translate to database functions. Methods in the SqlFunctions class can only be used in LINQ to Entities queries.


The System.Data.Odbc namespace is the .NET Framework Data Provider for ODBC.


The System.Data.OleDb namespace is the.NET Framework Data Provider for OLE DB.


The System.Data.OracleClient namespace is the .NET Framework Data Provider for Oracle.


Provides access to classes used to build WCF Data Services.


Classes in this namespace generate C# or Visual Basic code for a WCF Data Services client application based on the metadata returned by the data service.


Represents the .NET Framework client library that applications can use to interact with WCF Data Services.


Implements functionality common to both WCF Data Services client and server runtimes.


This namespace provides configuration settings for WCF data services features.


Used by the code generation command line tools and tools in Visual Studio to generate strongly-typed client side objects for communicating with data services.


This class is not for public use and is used internally by the system to implement support for queries with eager loading of related entities.


Provides a series of interfaces that are implemented to define a custom data service provider for WCF Data Services. 


The System.Data.Spatial namespace that contains classes of spatial database functionality.


The System.Data.Sql namespace contains classes that support SQL Server-specific functionality.


The System.Data.SqlClient namespace is the.NET Framework Data Provider for SQL Server.


The System.Data.SqlTypes namespace provides classes for native data types in SQL Server. These classes provide a safer, faster alternative to the data types provided by the .NET Framework common language runtime (CLR). Using the classes in this namespace helps prevent type conversion errors caused by loss of precision. Because other data types are converted to and from SqlTypes behind the scenes, explicitly creating and using objects within this namespace also yields faster code.

Return to top