On Wed, 29 Jun 2011, V G wrote: > On Wed, Jun 29, 2011 at 6:42 PM, Tamas Rudnai wro= te: > >> Generally speaking one connection is always does better performance than >> opening new ones. However, if several clients are constantly opening new >> connections and never closing them, then you are exhausting the resource= s >> (you can set the max number of connections an SQL server can take). So t= hen >> it is advised to close connections and reopen them when needed. >> >> However, in modern SQL servers and clients you have a so called connecti= on >> pool, which takes care of keeping connections open as long as they can b= e, >> and give these opened connections to the clients when they need them. Th= at >> gives you an optimum performance with better resource handling, so yes, >> opening and closing is a good idea. >> >> Tamas >> >> > > Thanks! Open/close on an as-needed basis it will be, then. But at any rat= e, > it's a small project with only a few users (not more than two or three at > the same time) so I won't be exhausting any modern SQL server no matter h= ow > bad I code it. FAMOUS LAST WORDS! :-) Regards Sergio Masci --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .