I’m putting together a WiFi application on a Pocket PC connecting to a
backend Sql Server2K. I’ve written a large percentage of the application but
would like some advice on a strategy for connecting and disconnecting to Sql
Server in view of the missing connection pools.
Opening and closing a connection after each stored procedure call is just to
time consuming, so I’d like to keep it open.
When to close the connection is the problem ? time-out etc

Split .NET exe file into many smaller ones
Block WM_MOUSEACTIVATE messages
Question on AppDomain and Thread
c# as operator
Managed C++ Mixed Assembly