The ODBC driver doesn’t support to set the Minimum Connection Pool Size and Maximum Connection Pool Size, but other drivers like ‘SQL Anywhere Native Driver’ can support to set the Minimum Connection Pool Size and Maximum Connection Pool Size.

Appeon product adopts the way “connection pool + short connection” to handle the database connection, for the other drivers like ‘SQL Anywhere Native Driver’ the Appeon server would create N (Minimum Connection Pool Size) connections in the connection cache pool on the basis of the configuration. Each client would get one connection from the connection cache pool when it performs the database operation, and then immediately free up this connection after executing one transaction. The next time when the client performs the database operation again it would go to the connection cache pool to get one connection (this one may be different from the previous one). Consequently, some clients may use the same connection separately, and the Appeon server will create new connection only when N connections are not enough. 

While for the ODBC driver, the Appeon server would initially create only one connection and more connections would be created only when the connections are not enough.