M
MattC
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
The cons are probably I can se are:
the potential for malicious code to be generated would be higher.
The slight loss in performance do to no execution plan being available to
cache.
I would appreciate any ideas, opinions URL links etc
TIA
MattC
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
The cons are probably I can se are:
the potential for malicious code to be generated would be higher.
The slight loss in performance do to no execution plan being available to
cache.
I would appreciate any ideas, opinions URL links etc
TIA
MattC