Sql Connection...

[ayuba asia]

I need a suggestion on opening SQL Connection Is it better for me to open and close the connection on each form that accces the data or i create i static connection that last thourgh to application run time, then close it.. I got a few feedback saying.. some say if i open and close connection each it may effect the performance and some say that if i open and static connection it will cause memory problem.. for ur info currently i doing with 1 static connection.. please give me an explanation on this issue thanks

[Christian Graus]

Open and close the connection, .NET maintains it's own connection pool. Christian Graus - Microsoft MVP - C++

[flicktom]

I was just boning up on the subject last night, and most DBMSs (if not the .NET itself) maintain a connection pool. This way, it can create how ever many connections it will dole out ahead of time, and assign them as needed, instead of performing the resource consuming actions to create them on the fly. Think of it like an old fashioned hotel switchboard operator's console.. they've got a certain number of outside connections all ready to go, but nothing directly connected to the rooms... When you call the operator, they just plug you in when you request an outside line. This is just the reason you "don't" want to use a static connection. Too many applications holding the line when they don't need it could lock up your DBMS for those that do. Flicktom

[ayuba asia]

thanks for the reply