2.0

Web Applications
Web Architecture
Web Services
XML Integration
Business Forms
E-Commerce
Content Controls
News and About

BROWSE E-CHAPTERS

         using System.Data; using System.Data.OleDb; // for Access using System.Data.SqlClient; // for SQL server C# programmers may use an alias for any namespace, e.g. using SQL=System.Data.SqlClient

Application performance will always be faster when you use native data providers rather then generic providers.
.NET comes with native providers for SQL server and Oracle and Access. A large numer of Enterprise Resource (ERP) Applications use one of these four methods to access data.








The three connected tasks in the above table use a server-side cursor A client-side cursor read all the records and "dumps" them down to the client from the Server. A server-side cursor step through each record on the server and involves a lot more server-side processing.

Stored procedures will also produce faster performace than any explicit SQL embedded in your preferred .NET language.

Often CRM, EDI, CRM, ERP, EDMS and general B2B systems involve a mix of different backend database engines such as SQL Server, Sybase, Infomix, AS400, Oracle, Ingress, Progress, Interbase and IBM DB2
ADO.NET can utilise a number of data providers to ensure Web Applicarions allow organisations to tie together disparate data stores with ease. Connection strings helper.

Task	ADO.NET
Connected, read a single value	ExecuteScalar()
Connected, read-only	ExecuteReader()
Connected, write-only	ExecuteNonQuery()
Disconnected, read/write	DataSets

&

 

To view please select a title from the list below