Connection pooling and connection parameters

[MCMartin]

The SQL Anywhere .NET Data Provider supports connection pooling. The documentation says: "...it checks the pool for an existing connection that uses the same connection parameters you have specified"
What means in this case same connection parameters, will the CON= parameter count too? If the application requests a new connection with a different CON parameter, but the rest is the same, will the pooled connection be reused and if so will the connection name change?
What about the APP parameter, it contains information about the executing thread will this be seen as different connection parameters, if just the calling thread is a different one?

[Former Member · Accepted solution]

I have confirmed with the Provider team that the connection string must match exactly in order for a pooled connection to get used. As a result, the con parameter counts.

[MCMartin]

Regarding the APP parameter Ian McHardy provided this usefull information:

The generated portion of the AppInfo string is ignored when determining if two connection strings are the same for connection pooling. If a user specified AppInfo parameter is specified, that is included in the comparison

[Former Member]

IMHO I think that CON parameter counts too.