Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 76 views

    Database Hierarchy (Dealing With Data Adapter,: Using System - Data.Oledb

    Uploaded by

    api-3831765
    ADO.NET provides consistent access to data sources and allows applications to connect to data sources and retrieve, manipulate, and update data. ADO.NET cleanly separates data access from manipulation into components that can be used separately or together. It includes data providers to connect to databases and execute commands and retrieve results, which can then be processed or placed in a DataSet.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    Database Hierarchy (Dealing With Data Adapter,: Using System - Data.Oledb

    Uploaded by

    api-3831765
    76 views3 pages
    ADO.NET provides consistent access to data sources and allows applications to connect to data sources and retrieve, manipulate, and update data. ADO.NET cleanly separates data access from manipulation into components that can be used separately or together. It includes data providers to connect to databases and execute commands and retrieve results, which can then be processed or placed in a DataSet.

    Original Title

    Ado

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    ADO.NET provides consistent access to data sources and allows applications to connect to data sources and retrieve, manipulate, and update data. ADO.NET cleanly separates data access from manipulation into components that can be used separately or together. It includes data providers to connect to databases and execute commands and retrieve results, which can then be processed or placed in a DataSet.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    76 views3 pages

    Database Hierarchy (Dealing With Data Adapter,: Using System - Data.Oledb

    Uploaded by

    api-3831765
    ADO.NET provides consistent access to data sources and allows applications to connect to data sources and retrieve, manipulate, and update data. ADO.NET cleanly separates data access from manipulation into components that can be used separately or together. It includes data providers to connect to databases and execute commands and retrieve results, which can then be processed or placed in a DataSet.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 3

    Database Hierarchy (dealing with data adapter,

    datasets by using ADO.NET)


    Overview of ADO.NET
    ADO.NET provides consistent access to data sources such as Microsoft SQL Server, as well as data
    sources exposed through OLE DB and XML. Data-sharing consumer applications can use ADO.NET to
    connect to these data sources and retrieve, manipulate, and update data.

    ADO.NET cleanly factors data access from data manipulation into discrete components that can be
    used separately or in tandem. ADO.NET includes .NET Framework data providers for connecting to a
    database, executing commands, and retrieving results. Those results are either processed directly,
    or placed in an ADO.NET DataSet object in order to be exposed to the user in an ad-hoc manner,
    combined with data from multiple sources, or remoted between tiers. The ADO.NET DataSet object
    can also be used independently of a .NET Framework data provider to manage data local to the
    application or sourced from XML.

    The ADO.NET classes are found in System.Data.dll, and are integrated with the XML classes found in
    System.Xml.dll. When compiling code that uses the System.Data namespace

    ASP.NET - Database Connection


    ADO.NET is also a part of the .NET Framework. ADO.NET is used to handle data access.

    What is ADO.NET?

    • ADO.NET is a part of the .NET Framework


    • ADO.NET consists of a set of classes used to handle data access
    • ADO.NET is entirely based on XML
    • ADO.NET has, unlike ADO, no Recordset object

    Create a Database Connection

    We are going to use the Northwind database in our examples.

    First, import the "System.Data.OleDb" namespace. We need this namespace to work with Microsoft
    Access and other OLE DB database providers. We will create the connection to the database in the
    Page_Load subroutine. We create a dbconn variable as a new OleDbConnection class with a
    connection string which identifies the OLE DB provider and the location of the database. Then we
    open the database connection:

    To specify the records to retrieve from the database, we will create a dbcomm variable as a new
    OleDbCommand class. The OleDbCommand class is for issuing SQL queries against database tables:

    Create a DataReader

    The OleDbDataReader class is used to read a stream of records from a data source. A DataReader is
    created by calling the ExecuteReader method of the OleDbCommand object:

    Using System.Data.OleDb;
    sub Page_Load

    // Create a Database Command


    dim dbconn,sql,dbcomm
    dbconn=New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;
    data source=" & server.mappath("northwind.mdb"))
    dbconn.Open()

    // Create a Database Command


    sql="SELECT * FROM customers"
    dbcomm=New OleDbCommand(sql,dbconn)
    dbread=dbcomm.ExecuteReader()

    end sub

    Close the Database Connection

    Always close both the DataReader and database connection after access to the database is no
    longer required:

    dbread.Close()
    dbconn.Close()

    Structure

    How to Catch SQL Exceptions and log them


    SqlConnection conn = new SqlConnection("Data Source=localhost;Initial Catalog=Northwind;");

    try
    {
    conn.Open();
    }
    catch (SqlException e)
    {
    System.Diagnostics.EventLog log = new System.Diagnostics.EventLog();
    log.Source = "My Application";
    log.WriteEntry(e.ToString());

    if (conn.State != ConnectionState.Open)
    Console.WriteLine("Connection was not opened.");
    }
    finally
    {
    conn.Close();
    }

    Keep Exception Information Private

    Attackers often use information from an exception, such as the name of your server, database, or
    table to mount a specific attack on your system

    You might also like