Does CLR suffer from the same serialization performance overhead that
extended stored procedures do? Which is likely to execute faster? Thanks."Neil W" <neilw@.netlib.com> wrote in message
news:O3OeWyhmGHA.3880@.TK2MSFTNGP02.phx.gbl...
> Does CLR suffer from the same serialization performance overhead that
> extended stored procedures do? Which is likely to execute faster?
> Thanks.
What do you mean by "serialization performance overhead"?
David
Thursday, March 8, 2012
CLR performance
Labels:
clr,
database,
execute,
microsoft,
mysql,
oracle,
overhead,
performance,
procedures,
serialization,
server,
sql,
stored,
suffer,
thatextended
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment