.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
satyapriyanayak
SP
Sambanthamoorthy
Swati Kadam
Ashutosh Jha

Home >> Articles >> DataBase >> Post New Resource Bookmark and Share   

 Subscribe to Articles

Monitoring Connection Pooling

Posted By:Shashi Ray       Posted Date: November 24, 2009    Points: 25    Category: DataBase    URL:   
 

Monitoring Connection Pooling

To monitor your application's use of connection pooling, you can use the Profiler tool that ships with SQL Server, or the Performance Monitor tool that ships with the Microsoft Windows® 2000 operating system.

To monitor connection pooling with SQL Server Profiler

    1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Profiler to start Profiler.
    2. On the File menu, point to New, and then click Trace.
    3. Supply connection details, and then click OK.
    4. In the Trace Properties dialog box, click the Events tab.
    5. In the Selected event classes list, ensure that the Audit Login and Audit Logout events are shown beneath Security Audit. To make the trace clearer, remove all other events from the list.
    6. Click Run to start the trace. You will see Audit Login events when connections are established and Audit Logout events when connections are closed.

 

To monitor connection pooling with Performance Monitor

    1. Click Start, point to Programs, point to Administrative Tools, and then click Performance to start Performance Monitor.
    2. Right-click the graph background, and then click Add Counters.
    3. In the Performance object drop-down list, click SQL Server: General Statistics.
    4. In the list that appears, click User Connections.
    5. Click Add, and then click Close.

 

Managing Security

Although database connection pooling improves the overall scalability of your application, it means you can no longer manage security at the database. This is because to support connection pooling, the connection strings must be identical. If you need to track database operations on a per user basis, consider adding a parameter through which you can pass the user identity and manually log user actions in the database. You need to add this parameter to each operation.

 

 

 

Shashi Ray

 


 Subscribe to Articles

     

Further Readings:

Responses

No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend