09-07-2011, 11:50 PM
(This post was last modified: 09-09-2011, 12:23 AM by MikeHenery9.)
.NET is the technology that .NET applications use to interact with a database.
Although it’s technically possible to organize data into tables and store it on the hard drive in one or more files (perhaps using a standard like XML), this approach wouldn’t be very flexible. Instead, a web application needs a full relational database management system (RDBMS), such as SQL Server. The RDBMS handles the data infrastructure, ensuring optimum performance and reliability. For example, the RDBMS takes the responsibility of providing data to multiple users simultaneously, disallowing invalid data, and committing groups of actions at once using transactions.
In most ASP.NET applications, you’ll need to use a database for some tasks. Here are some basic examples of data at work in a web application:
• E-commerce sites (like Amazon) use detailed databases to store product catalogs. They also track orders, customers, shipment records, and inventory information in a huge arrangement of related tables.
• Search engines (like Google) use databases to store indexes of page URLs, links, and keywords.
• Knowledge bases (like Microsoft Support) use less structured databases that store vast quantities of information or links to various documents and resources.
• Media sites (like The New York Times) store their articles in databases.
You probably won’t have any trouble thinking about where you need to use database technology in an ASP.NET application. Even a simple e-mail address submission form that uses a back-end database to store a list of potential customers or contacts. This is where ADO.NET comes into the picture. ADO.NET is a technology designed to let an ASP.NET program (or any other .NET program, for that matter) access data.
ADO.NET
ADO stands for ActiveX Data Object.
ADO .NET concept mainly used to connect and transact with the DB Systems.
ADO .Net provides a data access model with the following objects.
Objects: (a)Consumer objects,(b)Provider Objects
Provider object are known as connected objects, Some of the provider objects in ado .net varies
based on the type of DB system.
Provider objects :
SQL server: SqlConnection, SqlDataReader, SqlCommand, SqlDataAdapter.
Oracle: OracleConnection, OracleCommand, OracleDataReader, OracleDataAdapter
(Open DB Connectivity):
ODBC: OdbcConnection, OdbcCommand, OdbcDataReader, OdbcDataAdapter
(Object Linking and DB Embedding):
OLEDB: OledbConnection, OledbCommand, OledbDataReader, OledbDataAdapter.
OLEDB & ODBC mainly used to connect any type of DB systems like
• SQL Server
• Oracle
• DB2
• MS Access
ODBC is a 3rd party control or tool installed within OS.
OLEDB is built-in within the .NET Framework.
OLEDB is secure & faster compare to ODBC.
Visit Us At: www.cegonsoft.com
Cegonsoft
Although it’s technically possible to organize data into tables and store it on the hard drive in one or more files (perhaps using a standard like XML), this approach wouldn’t be very flexible. Instead, a web application needs a full relational database management system (RDBMS), such as SQL Server. The RDBMS handles the data infrastructure, ensuring optimum performance and reliability. For example, the RDBMS takes the responsibility of providing data to multiple users simultaneously, disallowing invalid data, and committing groups of actions at once using transactions.
In most ASP.NET applications, you’ll need to use a database for some tasks. Here are some basic examples of data at work in a web application:
• E-commerce sites (like Amazon) use detailed databases to store product catalogs. They also track orders, customers, shipment records, and inventory information in a huge arrangement of related tables.
• Search engines (like Google) use databases to store indexes of page URLs, links, and keywords.
• Knowledge bases (like Microsoft Support) use less structured databases that store vast quantities of information or links to various documents and resources.
• Media sites (like The New York Times) store their articles in databases.
You probably won’t have any trouble thinking about where you need to use database technology in an ASP.NET application. Even a simple e-mail address submission form that uses a back-end database to store a list of potential customers or contacts. This is where ADO.NET comes into the picture. ADO.NET is a technology designed to let an ASP.NET program (or any other .NET program, for that matter) access data.
ADO.NET
ADO stands for ActiveX Data Object.
ADO .NET concept mainly used to connect and transact with the DB Systems.
ADO .Net provides a data access model with the following objects.
Objects: (a)Consumer objects,(b)Provider Objects
Provider object are known as connected objects, Some of the provider objects in ado .net varies
based on the type of DB system.
Provider objects :
SQL server: SqlConnection, SqlDataReader, SqlCommand, SqlDataAdapter.
Oracle: OracleConnection, OracleCommand, OracleDataReader, OracleDataAdapter
(Open DB Connectivity):
ODBC: OdbcConnection, OdbcCommand, OdbcDataReader, OdbcDataAdapter
(Object Linking and DB Embedding):
OLEDB: OledbConnection, OledbCommand, OledbDataReader, OledbDataAdapter.
OLEDB & ODBC mainly used to connect any type of DB systems like
• SQL Server
• Oracle
• DB2
• MS Access
ODBC is a 3rd party control or tool installed within OS.
OLEDB is built-in within the .NET Framework.
OLEDB is secure & faster compare to ODBC.
Visit Us At: www.cegonsoft.com
Cegonsoft
