Dapper will close the connection if it needed to open it. So if you're just doing 1 quick query - let Dapper handle it. If you're doing many, you should open (once) and close at the end, with all the queries in the middle...just from an efficiency standpoint.

Does dapper automatically close connection?

Dapper will automatically open closed connections, and it will automatically close connections that it auto-opened, but it will not automatically dispose of connections.

Does dapper use connection pooling?

1 Answer. Dapper doesn't include any such; dapper works on top of an open connection, so is beyond the point pooling applies. Your ado.net client may include pooling; SQL server (in ado.net) does, for example.