When I profile my application using SQL Server Profiler, I am seeing lots of *Audit Login* and *Audit Logout* messages for connections to the same database. I am wondering, does this indicate that something is wrong with my connection pooling? The reason I ask, is because I found this in the MSDN documentation in regards to connection pooling:

> 
> Login and logout events will not be
>  raised on the server when a connection
>  is fetched from or returned to the
>  connection pool. This is because the
>  connection is not actually closed when
>  it is returned to the connection pool.
>  For more information, see Audit Login
>  Event Class and Audit Logout Event
>  Class in SQL Server Books Online.
> 
> 
> 

<http://msdn.microsoft.com/en-us/library/8xx3tyca.aspx>

Also, does anyone have any tips for determining how effective the connection pooling is for a given SQL server? I have lots of databases on a single server and I know this can have a huge impact, but I am wondering if there is an easy way to obtain metrics on the effectiveness of my connection pooling. Thanks in advance!