>Connection pooling occurs on the client, not on SQL Server.

Ah. That's what I was assuming, but wasn't sure.

> it expires and is released.

So I'm guessing that on the SQL Server side, it sees the connection as "active" until the client releases it from the connection pool, so yeah, I can see that there's no way to tell whether it's a pooled or active connection from the server.

>Check out the topic Connection Pooling for the .NET Framework Data Provider for SQL Server in the .NET Framework SDK.

Thanks, Mike - I'll do that.