DAL...should the methods be static?

[H]

In my BusinessLogicLayer, there are many places where I call the
DataAccessLayer.

Is it better to have static methods in my DAL that are lock()'ed and
called directly from my BLL (thus the CLR takes care of concurrency)
or should I have public methods and create an instance of my DAL each
time it is used (thus let SQL Server take care of concurrency)?

adv-thanks-ance...

[Just Me]

The only reason you need to lock them is if they are making use of a static
variable which you should avoid at all costs.

I have used static methods extensively in my DAL without problems in a multi
user environment.
"H" <ha*********@gmail.comwrote in message
news:cf**********************************@8g2000hs e.googlegroups.com...

In my BusinessLogicLayer, there are many places where I call the
DataAccessLayer.

Is it better to have static methods in my DAL that are lock()'ed and
called directly from my BLL (thus the CLR takes care of concurrency)
or should I have public methods and create an instance of my DAL each
time it is used (thus let SQL Server take care of concurrency)?

adv-thanks-ance...

[HelloCode]

On 3ÔÂ22ÈÕ, ÏÂÎç8ʱ18·Ö, H <[e-mail]:

In my BusinessLogicLayer, there are many places where I call the
DataAccessLayer.

Is it better to have static methods in my DAL that are lock()'ed and
called directly from my BLL (thus the CLR takes care of concurrency)
or should I have public methods and create an instance of my DAL each
time it is used (thus let SQL Server take care of concurrency)?

adv-thanks-ance...

if you static methods use different connection is no problem.

[Mark Rae [MVP]]

"Just Me" <news.microsoft.comwrote in message
news:Ol**************@TK2MSFTNGP02.phx.gbl...

I have used static methods extensively in my DAL without problems in a
multi user environment.

Me too.
--
Mark Rae
ASP.NET MVP
http://www.markrae.net