Re: CRUD in SP or Dynamic SQL

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yeah that's gonna happen regardless, but I wouldn't have to change the
update/insert/read stored procs as well as the code.
MattC
"The Crow" <q> wrote in message
news:#UAqjQGYFHA.3132@xxxxxxxxxxxxxxxxxxxxxxx
> "MattC" <m@xxxxx> wrote in message
> news:eWfzCGGYFHA.3760@xxxxxxxxxxxxxxxxxxxxxxx
> > Hi,
> >
> > I'm implementing a new Business Layer in one of our applications. I'm
> > toying with the idea of placing all the Create, Read, Update and Delete
> > SQL
> > in the object in question and build a dynamic SQL string using a class
> > builder.
> >
> > The pros I can see are:
> > It reduces the number of stored procs to admin.
> > Changes to the underlying table schema does not require massive changes
to
> > large numbers of storeprocs
> >
>
> Wouldnt database schema change affect the way you build dynamic sql in ur
> code? and it requires compilation.
>
>


.

Quantcast