Connection pooling for a rich client accessing a database directly -

I have a legacy app WinForms that connects directly to the SQL Server 2005 database.

The client applications are open at the same time (hundreds of), so I want to reduce the number of connections from the database.

I can issue connections quickly and often, and keep the timeout values ​​low.

Do other things need to be considered?

Try to use the same connection string when you create a new connection, so Net is a connection Will use the pool.

Settle your connection as soon as possible.

You can set the maximum pool size in the connection string to determine the maximum number of active connections.