data-access approach

microsoft.public.dotnet.framework.adonet

9 May 2007 1:27 PM

Ofer

Hi,

Your opinion is welcome on choosing a DAL strategy for our .Net web project.
We want a single unified DAL approach, but which one?

Our new modules (40% of the code) use the DAL created by the XSD designer
for calling SQLs and SPs.
Our old modules (60% of the code) connect directly to the DB.

The query-designer has good dev speed and automation but it has limits (?):
1) doesn't support returning multiple tables from a SP
2) doesn't supoprty (?) BL-level transactions (such as select, update and an
update based on the last update's result).

It seems that using the DAAB involves manual coding that takes more time and
more bug-risk than the automatic code generated by the XSD query designer.
Is it worth the time to replace the direct DB access in our old code with
DAAB code?

Do you know a good SQL code-generation tool?
Can it create automatic runtime update SQLs for optimistic-lock checks of
all field values?

So what do YOU experts think?
Which DAL approach and tools do you recommend based on your experience?

Thanks for any input,
Ofer