Summary

for RuBoard

In this hour , you've seen how connection pools are orchestrated and that they are embedded in the individual .NET data providers themselves . This maximizes the strengths and individual characteristics of each data provider's implementation. In addition, you have learned about the connection keywords that are directly related to connection pooling and control its behavior. Because connection pooling is such a critical aspect of large applications and scalability, it is always a good idea to monitor how effectively the values you choose are being utilized over time. Adjust these as needed. You can use Performance Monitor to regularly get a good feel for how things are going.

The really good news to this whole story is that Microsoft has decided to make connection pooling the default approach from the start. You will find that most applications you will ever code will take full advantage of this decision.

for RuBoard