>>Why not? Open, Execute, Close. Do it however many times are required. I don't think you will find the overhead to be as high as you fear.
>
>Well, if I need to do 20 SQL commands, it is must better to only have one open and one close.

That's true if you are actually opening and closing a connection each time. In practice you're not - you're just grabbing an existing connection from the pool. If you keep a connection open then it is likely that the pool will actually be forced to open additional *real* connections to handle other requests.

Regards,
Viv