Advertisement
Published in:
2002 | OriginalPaper | Chapter
ADO.NET—Getting Connected
Authors : William R. Vaughn, Peter Blackburn
Published in: ADO.NET Examples and Best Practices for C# Programmers
Publisher: Apress
Included in: Professional Book Archive
Activate our intelligent search to find suitable subject content or patents.
Select sections of text to find matching patents with Artificial Intelligence. powered by
Select sections of text to find additional relevant content using AI-assisted search. powered by
While it’s possible to create stand-alone data structures using ADO.NET without the benefit of a back-end data source—such as SQL Server, Access, Oracle, or other DBMS data sources—most developers must depend on ADO.NET and a database engine to construct objects reflecting the data and its schema. This chapter discusses how to establish a connection in .NET using three different .NET Data Providers as well as the “traditional” ADOc Connection object: 1.Via the ADO.NET OleDb .NET Data Provider—System.Data.OleDb.2.Via the ADO.NET Tabular Data Stream (TDS) or SglClient .NET Data Provider—System. Data. SglClient.3.Via the ADO.NET Odbc .NET Data Provider—Microsoft.Data.Odbc4.Via ADOc. (Remember that ADOc refers to traditional COM-based ADO.)