Performance considerations while architecting database access
- Turning on features that application only.
- N-Tier strategy gives maximum performance as opposed to a direct client-to-database connection.
- Use Optimal Managed Provider such as System.Data.SqlClient to gain performance.
- Stored Procedures usage where ever possible.
- Avoid Auto-Generated commands of data adapter. Gives better performance in critical applications.
- Prefer Data Reader, when you dont need to cache your data. using data reader can provide you with an enormous performance boost.
- Data Reader's CommandBehavior.Sequential Access can be used often as possible. If you dont need to work the whole object at once, will give you much better performance.
- Keep your Datasets lean.
- Particularly when designing for disconnected approach, make several connections in sequence rather than holding a single connection open for a long time.
Comments