1. Create a connection. This requires a connection string, which can be given declaratively or put in a well defined place like the .config files. Advantage of keeping in .config files is that it enables use of Connection Pooling by .Net framework, else even one small change in connection string will cause CLR to think it's not the same connection and will instantiate new connection for other request.
2. Open the connection and keep it open until done, typically done as using (con) { //use }
3. If using connected data model, create a SqlCommand object, decorate it with desired command, command type (stored procedure for eg), add any parameters and their values to the command, and then consume the command by using ExcuteReader or ExecuteScalar. In case of ExecuteReader, we will get back a handle to a fast-forward, read only pointer to the recordset. We can also decorate Command object with multiple recordsets in 2.0 and execute one by one (MARS - Multiple Active Record Sets)
4. If using disconnected data model, create a DataAdapter object, decorate it with desired SELECT, INSERT, UPDATE, DELETE commands, add parameters as necessary and then fill up a DataSet or DataTable using the DataAdapter. Subsequent SQL can be executed using insert, update, delete commands on the dataset.
1. Create a connection. This requires a connection string which can be given declaratively or put in a well defined place like the .config files. Advantage of keeping in .config files is that it enables use of Connection Pooling by .Net framework else even one small change in connection string will cause CLR to think it's not the same connection and will instantiate new connection for other request.
2. Open the connection and keep it open until done typically done as using (con) { //use }
3. If using connected data model create a SqlCommand object decorate it with desired command command type (stored procedure for eg) add any parameters and their values to the command and then consume the command by using ExcuteReader or ExecuteScalar. In case of ExecuteReader we will get back a handle to a fast-forward read only pointer to the recordset. We can also decorate Command object with multiple recordsets in 2.0 and execute one by one (MARS - Multiple Active Record Sets)
4. If using disconnected data model create a DataAdapter object decorate it with desired SELECT INSERT UPDATE DELETE commands add parameters as necessary and then fill up a DataSet or DataTable using the DataAdapter. Subsequent SQL can be executed using insert update delete commands on the dataset.
1. create a connection string. 2.open the connection. 3.pass a query through command object 4.raed the using datareader. 5.Display the data using any display control. 6.close the connection
step 1: first we have to add namespace using system.data.sqlclient; then connect to database by using this Base class library
step 2:if ur connecting with ur own system(PC) conect server as localhost sqlconnection con new sql connection("server localhost;uid sa;database northwind");
step 3:if u want to connect as connection oriented we have to give con.open();
step 4:then type a command sqlcommand cmd new sqlcommand (select * from products);
step 5:sqldatareader dr cmd.executereader(); while(dr.read()) { /*wat ever we want to execute we have to write in this loop } dr.close(); con.close();
1. Implements the base class for data access 2. Create a connection 3. Open that connection 4. Create a data reader and execute the data reader with proper sql statements You can get the values of the record using the methods GetString GetInt32 ....etc.
TO Connect to a DatabaseFirst we need to have a namespace like System.Data.Sqlclientthen connect to database as follows1.Create connection using SqlConnection Sqlconnection con new sqlconnection( Connectionstring )2.Open connection con.Open()3.Pass query using command object SqlCommand cmd new sqlCommand( Sqlquery con)4. Read the data using Datareader Datareader rd cmd.ExecuteReader()5. Dispaly the data using display control6. Close the connection con.Close()
4 
0