Many design considerations must be addressed when building Web-based applications, especially Web applications that need to handle a large number of users and promise great scalability. Deciding how to use a technical design feature such as "connection pooling" can make the difference between a slow and clunky Web app or a fast and sleek Web app. Connection pooling deals with how the database connections are utilized (used and reused) to enhance the overall efficiency of the whole system. In fact, this one little feature translates directly into being able to support a much larger number of users with minimum performance impact. Ah, the promise is fulfilled.
Basically, the Microsoft .NET Framework has taken the approach (the commitment) of using connection pooling as the default. In other words, connection pooling will always be "true" unless you specifically disable it. This allows you to utilize the internal connection-pooling capabilities of the .NET data providers, such as the SQL Server .NET data provider and the OLE DB data provider, to achieve much more efficient and scalable applications without lifting a finger.
In this hour, you will learn about the following topics:
An overview of connection pooling
How to create connection pools in ASP.NET
Connection pools and transaction enlisting
Controlling connection pools with the connection string