Very Computer

by **David Taylo** » Fri, 07 Nov 2003 18:30:11

I am writing a VB.NET program that runs an X-ray analyzer from a PC embedded
in the analyzer. The program records results of the analysis every 2-3
minutes into a SQL Server database. In some cases, the SQL Server will be
MSDE on the embedded PC, in other cases it may be another SQL Server on the
LAN. The analyzers run 24x7. My question is, given this scenario, what
would you consider "best practice" for handling the SQLConnection object?
Should it be opened continuously? or opened & closed for each write to the
database?

Thanks for any comments/suggestions....

Dave Taylor

by **David Brown** » Fri, 07 Nov 2003 18:49:25

Quote:> I am writing a VB.NET program that runs an X-ray analyzer from a PC
embedded
> in the analyzer. The program records results of the analysis every 2-3
> minutes into a SQL Server database. In some cases, the SQL Server will be
> MSDE on the embedded PC, in other cases it may be another SQL Server on
the
> LAN. The analyzers run 24x7. My question is, given this scenario, what
> would you consider "best practice" for handling the SQLConnection object?
> Should it be opened continuously? or opened & closed for each write to the
> database?

If you only need the connection every 2-3 minutes, I would open and close it
each time.
Remember to really close the connection you must supress connection pooling
in the connection string ("Pooling=false").

David

Very Computer

"Best practices" for SQL connections

"Best practices" for SQL connections

"Best practices" for SQL connections