Best way to manage SQL connection
We've been having SQL connection problem with our development VB & SQL.
We would like EE appreciation on this topic.
Most apps we develop with a connection stay open until exiting.
Please advice
We would like EE appreciation on this topic.
Most apps we develop with a connection stay open until exiting.
Please advice
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
we use all 3, VBA, VB6 and VB.NET, but 99% of the development is under VB.NET. If we had to choose on which we would like an opinion, it would be on VB.NET.
Can you elaborate on 'Connection pooling'?
Can you elaborate on 'Connection pooling'?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanx
ASKER
Our business environment if more toward financials. That is, doing invoices, doing checks, reports, II guess the normal daily operation of an ERP solution. At any one time, there may from 2 to 3 users running the module, but not 2 or 3 working with apps. I mean that there can be 2 or more accessing Sales module, but only one doing invoices.
I think most of our apps is as in method 3 (the worst):
- Open Your Application
- Open SQL connection
- Run you Program
- Close SQL connection while closing the application
I think the best method is #1:
- Open your SQL connection
- Run your function
- Close your SQL connection
We're willing to change all apps to point to this type of SQL connection/Access.
Some colleagues and programmers we have spoken with are more inclined on the #3; so our doubt on which to use.
We know that it's difficult for EE to give an accurate recommendation, specifically with little data at hand, but based on our description on how we use our programs, will method #1 tax our SQL database or instance?
Please advice.