Geeks With Blogs

Scott Kuhl Warning: I may have no idea what I am talking about!

Developing performance-oriented .NET applications is not easy. The .NET standard includes only basic guidelines and interface definitions to help programmers develop .NET applications. In addition, .NET data providers do not throw exceptions to say that your code is running too slowly.

Designing a .NET application is a complex process, in part because the code can be very data provider-specific. If you are working with several databases, you will find differences in the programming concepts between the data providers. You will need much more database knowledge to design your application to run efficiently.

This article contains guidelines compiled by examining the .NET implementations of shipping .NET applications and analyzing the common performance mistakes that we found. The guidelines discuss selecting .NET objects and methods, designing .NET applications, retrieving data, and updating data.

This full TheServerSide.NET article covers the following topics:

  • Choosing Between a DataSet and a DataReader
  • Avoiding the CommandBuilder Object
  • Using Parameter Markers as Arguments to Stored Procedures
  • Using Connection Pooling
  • Opening and Closing Connections
  • Managing Commits in Transactions
  • Choosing the Right Transaction Model
  • Using Commands that Retrieve Little or No Data
  • Using Commands Multiple Times
  • Using Native Managed Providers
  • Retrieving Long Data
  • Reducing the Size of Data Retrieved
  • Choosing the Right Data Type
  • Synchronizing Changes Back to the Data Source
Posted on Wednesday, August 31, 2005 1:32 PM .NET | Back to top

Comments on this post: Optimized ADO.NET

No comments posted yet.
Your comment:
 (will show your gravatar)

Copyright © Scott Kuhl | Powered by: