You deploy a number of ASP.NET Web applications to a single server. The applications connect to Microsoft SQL Server databases and rely on connection pooling to minimize the cost of opening connections. You find that after a period of several days, pool fragmentation begins to consume excessive memory. You must fix the problem without affecting connection pool creation.

What should you do?

 Posted by Rajkatie on 8/31/2012 | Category: ADO.NET Interview questions | Views: 1211 | Points: 40
Select from following answers:
  1. Periodically call SqlConnection.ClearAllPools from an administrative application.
  2. Call SqlConnection.ClearPool each time you close the connection.
  3. Apply a short Connection Timeout setting to the connection strings.
  4. All Above

Show Correct Answer

Source: | | Alert Moderator 

Comments or Responses

Login to post response