Abstract
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.Odbc
-
4.
Via ADOc. (Remember that ADOc refers to traditional COM-based ADO.)
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2002 Apress
About this chapter
Cite this chapter
Vaughn, W.R., Blackburn, P. (2002). ADO.NET—Getting Connected. In: ADO.NET Examples and Best Practices for C# Programmers. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-1099-3_2
Download citation
DOI: https://doi.org/10.1007/978-1-4302-1099-3_2
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-59059-012-6
Online ISBN: 978-1-4302-1099-3
eBook Packages: Springer Book Archive