Why are table valued parameters to SQL Server stored procedures required to be input READONLY? -

Why are table valued parameters to SQL Server stored procedures required to be input READONLY? -

can explain design decision behind preventing table valued parameters beingness specified output parameters stored procedures?

i can't count number of times i've started building out info model hoping lock downwards tables external access (you know...implementation details), grant applications access database through stored procedures (you know... info interface) , communicate , forth tvps have ssms phone call me naughty having audacity think can utilize user-defined table type transfer object between info service , application.

so please provide me reason why tvps designed readonly input parameters.

in presentation on optimizing microsoft sql server 2008 applications using table valued parameters, xml, , merge michael rys says. (at 32:52)

note in sql server 2008 table valued parameters read only. notice require write readonly. means @ point in future maybe if please, please please plenty might able create them writable @ point. @ moment read only.

here connect item should utilize add together "please". relax restriction table parameters must readonly when sps phone call each other.

srini acharya made comment on connect item.

allowing table valued parameters read/write involves quite bit of work on sql engine side client protocols. due time/resource constraints other priorirites, not able take work part of sql server 2008 release. however, have investigated issue , have firmly in our radar address part of next release of sql server.

sql-server