Is This A Safe Practice (ADO.NET SqlConnection Management)?

[Jeff S]

I'm considering creating a static "helper" class that will be called by
practically all methods in my data access layer (DAL) class. Rather than
having every method in the DAL create its own connection object and then
open it, I was thinking it might be good to create a static method in the
helper class that returns an opened SqlConnection object to the calling DAL
methods. The calling DAL method would then be responsible for closing and
disposing of the SqlConnection when it's done using it.

Good? Bad? Ugly? Recommendations?

Thanks.

 

[David Browne]

I'm considering creating a static "helper" class that will be called by
practically all methods in my data access layer (DAL) class. Rather than
having every method in the DAL create its own connection object and then
open it, I was thinking it might be good to create a static method in the
helper class that returns an opened SqlConnection object to the calling DAL
methods. The calling DAL method would then be responsible for closing and
disposing of the SqlConnection when it's done using it.

Good? Bad? Ugly? Recommendations?

Good.

using (SqlConnection c = DALHelper.connect())
{
...

}

David