1. ASP.NET Introduction 2. Comp of .Net Framework 3.5 3. Sys.Req for VS 2008 4. ASP.NET Envrmnt Setup 5. VS2010 Ultimate Sys.Req 6. Installing VS 2010 7. VS 2012 Sys.Req 8. Installing VS Exp 2012 9. Start the VS 2008 10. Application Life Cycle 11. Page Life Cycle 12. Page Life Cycle Events 13. ASP.NET Example 14. Event Handling 15. Default Events 16. Server Side 17. Request Object 18. Response Object 19. Server Controls 20. Server Controls Properties 21. Server Controls Methods 22. HTML Server Controls 23. Client Side 24. ASP.NET Basic Controls 25. TextBox Control 26. CheckBox Controls 27. RadioButton Controls 28. ListBox Control 29. HyperLink Control 30. Image Control 31. BulletedList Control 32. ASP.NET Directives 33. Implements Directive 34. Master Type Directive 35. Page Directive 36. PreviousPage Type 37. Managing State 38. Control State 39. Cookies 40. Query Strings 41. Server-Side State 42. Session State 43. Validation Controls 44. Required FieldValidator 45. Range Validator 46. Compare Validator 47. RegularExpressionValidator 48. Custom Validator 49. Validation Summary 50. Data Source Control 51. AdRotator Control 52. Calendar Control 53. Calendar Control Example 54. Panel Control 55. Panel Control Example 56. Multi Views Control 57. MultiView & View controls 58. MultiView Control Example 59. FileUpload Control 60. FileUpload Control Eg 61. AJAX Control 62. UpdatePanel control 63. UpdateProgress Control 64. Custom Controls 65. Custom Control Eg 66. Personalization 67. Create Simple Profile 68. ADO.NET 69. ADO.NET Objects 70. DataTable 71. DataRow 72. DataColumn 73. Object Example 74. Error Handling 75. Tracing Errors 76. Debugger 77. Security 78. Authentication 79. Authorization 80. LINQ 81. LINQ Query Operators 82. LINQ Example 83. Caching 84. Data Caching 85. Output Caching 86. Object Caching 87. Web Services 88. Create Web Services Eg 89. Web & Machine.config 90. Settings Schema 91. ASP.NET Deployment 92. XCopy Deployment 93. Web Setup Project 94. ASP Interview Part 1 95. ASP Interview Part 2 96. ASP Interview Part 3 97. ASP Interview Part 4 98. ASP Interview Part 5 99. ASP Interview Part 6
Pr.Pg Next Pg

ADO.NET Objects tutorials

The SqlConnection Object

  • The first component of ADO.NET is the Connection object. The connection object opens a connection to your data source.

  • All of the configurable aspects of a database connection are represented in the Connection object, which includes ConnectionString and ConnectionTimeout.

  • Connection object helps in accessing and manipulating a database. Database transactions are also dependent upon the Connection object.

  • In ADO.NET the type of the Connection is depended on what Database system you are working with. The following are the commonly using the connections in the ADO.NET 

    1. OleDbConnection

    2. SqlConnection

    3. OdbcConnection


The SqlCommand Object

  • The Command object is used to perform action on the data source. Command object can execute stored procedures and T-SQL commands.

  • You can execute SQL queries to return data in a DataSet or a DataReader object. Command object performs the standard Select, Insert, Delete and Update T-SQL operations.


The SqlDataReader Object

  • ADO.NET introduces the DataReader object to provide you with an easy method to quickly Pull an uneditable chunk of data out of your database.

  • Unlike the DataAdapterís connection to your database, the DataReader utilizes a server-side cursor. The way that the DataReader connects to a database and deals with your data request differs greatly from the DataSetís usage.

  • To connect to the database, the DataReader does not use the DataAdapter object.

  • You also do not use a DataSet in your code to store the retrieved data in. The DataReader uses a Connection object to talk to the database and a Command object to execute the query that pulls back the needed data. The DataReaderís Read method allows you to step forward through the databaseís table one record at a time.


The SqlDataAdapter Object

  • Sometimes the data you work with is primarily read-only and you rarely need to make changes to the underlying data source some situations also call for caching data in memory to minimize the number of database calls for data that does not change.

  • The data adapter makes it easy for you to accomplish these things by helping to manage data in a disconnected mode.

  • The data adapter fills a DataSet object when reading the data and writes in a single batch when persisting changes back to the database.

  • A data adapter contains a reference to the connection object and opens and closes the connection automatically when reading from or writing to the database. Additionally, the data adapter contains command object references for SELECT, INSERT, UPDATE, and DELETE operations on the data. You will have a data adapter defined for each table in a DataSet and it will take care of all communication with the database for you. All you need to do is tell the data adapter when to load from or write to the database.


The DataSet Object

  • DataSet objects are in-memory representations of data. They contain multiple Datatable objects, which contain columns and rows, just like normal database tables. You can even define relations between tables to create parent-child relationships.

  • The DataSet is specifically designed to help manage data in memory and to support disconnected operations on data, when such a scenario make sense.

  • The DataSet is an object that is used by all of the Data Providers, which is why it does not have a Data Provider specific prefix.

Pr.Pg border                                              Next Pg