ADO.NET

a) SQLCommand is used to execute all kind of SQL queries like DML(Insert, update,Delete) & DDL like(Create table, drop table etc)

b)SQLCommandBuilder object is used to build & execute SQL (DML) queries like select, insert, update & delete.

.net doesn't support the mutiple inheritance, perhaps you may talk about multi-level inheritance.

In the later case, if a class is inherited from another class, at the time of creating instance, it will obviously give a call to its base class constructor (ie bottom - top approach). Like wise the constructor execution is takes place in top down approach (ie. base class constructor is executed and the derived class constructor is executed).

So for GC, it will collect only when an object does not have any reference. As we see previously, the derived is constructed based on base class. There is a reference is set to be. Obviously GC cannot be collected.

First Excute Sql Quries in Query Analzer,see How much time 2 take Excute , if Less then the ur desired Time, then it will Optimize query

it is possible

DataSet ds;

sqlAdap.Fill(ds);

Datatable dt = ds.Tables[0].copy();

//now the structure and data are copied into 'dt'

ds.Tables.remove(ds.Table[0]);

//now the source is removed from the 'ds'

executescalar()

executereader()

executenonquery()

these comes with Begin and End like Beginexecutescalr() Endexecutescalar().......

by using these command we can achieve asynch comm in ado.net

A DataSet can be Typed or Untyped. The difference between the two lies in the fact that a Typed DataSet has a schema and an Untyped DataSet does not have one. It should be noted that the Typed Datasets have more support in Visual studio.

By Using the Transactions we can check the Exact Numbers of the rows to be updated and if the updation fails then the Transaction will be rollbacked.

data reader can hold data from multiple tables and datareader can hold more than one table.

string query="select * from employee; select * from student";

sqlcommand cmd=new sqlcommand(query, connection);

sqldatareader dr=cmd.executeReader();

if(dr.hasrows)

{

dr.read();

gridview1.DataSource=dr;

gridview1.Databind();

if(dr.nextresult)

{

gridview2.datasource=dr;

gridview2.databind();

}

}

dr.colse();

connection.close();

DO.NET Command Object - The Command object is similar to the old ADO command object.

It is used to store SQL statements that need to be executed against a data source.

The Command object can execute SELECT statements, INSERT, UPDATE, or DELETE statements, stored procedures, or any other statement understood by the database.

all heavy controls like grid view,datagrid or datalist,repeater controls cantains the chield controls like button or link button, when we click this button then the event will be raised, that events are handled by parant controls,that is called event bubbling,means event is bubbled from bottom(chield)to up(parant).

we have to use a dataset because on using datareader forward only paging can be achieved.

Suppose if you are at 1000 page and you want to go back to 999th page, if you use datareader it cannot be achieved, since it does not support backward navigation.

Dataset supports forward and backward navigation

Data Access layer is actually a part of Architecture layer. It has 2 tier,3 tier or N tier Layer. Generally we use 3 tier Layer 1) Presentation layer,Business Logic layer and then Data Access Layer. Data Access layer is a medium to talk between database and Business Logic layer.

It helps to maintain flexibility,resuablity and even secuity also. In security SQL Injection can be stopped with 3 iter Archietcture.

Datareader and Dataset are the two fundamental objects in ADO.NET

we use dispose

Ado.net uses no Dataprovider by default and this is absulotely correct answere. there is no other choice for this question

The provider name is oledb and the namespace is system.data.oledb

The term ACID conveys the role transactions play in mission-critical applications. Coined by transaction processing pioneers, ACID stands for atomicity, consistency, isolation, and durability.

These properties ensure predictable behavior, reinforcing the role of transactions as all-or-none propositions designed to reduce the management load when there are many variables.

A transaction is a unit of work in which a series of operations occur between the BEGIN TRANSACTION and END TRANSACTION statements of an application. A transaction executes exactly once and is atomic ?

all the work is done or none of it is.

Operations associated with a transaction usually share a common intent and are interdependent.

By performing only a subset of these operations, the system could compromise the overall intent of the

transaction. Atomicity eliminates the chance of processing a subset of operations.