Hi!

Many connection handles have little impact on the memory, unless you're using asynchronous connection and fetching for remote views (when view does not download all records at once, but just first 100 records, and the rest - on demand, as soon as user try to use another chunk of records). In such case data queried are stored somewhere for each such connection, that, of course take memory (on SQL Server).

Really, I do not know other details, just because I'm not ODBC programer and do not know details. Probably MS have a page somewhere that describe technical limitations/things for ODBC connections. Or just make the questions somewhere in the ODBC-related forum or newsgroups.

However, there is another thing related to many connections - licensing. For SQL Server, for example, license price is depended on the number of simultaneous connections. When you reach limit in number of connections, you just cannot connect. As a result, it is better to make application with only one connection to allow as many users connected to SQL Server from network as you have allowed by license, and never reach the limit. There is also per-user licensing, that is different. You can read more about this on the MS site.

>Hi Vlad:
>
>How are the criterials to define how much connections we must to use in a database (performance, memory, )? What's the difference in to use a same handle to several views and to use different's handle to the views???
>
>Thanks for your kindly answer.