Table-Valued Parameters support
TVP support for stored procedures
Daniel Kress commented
This would be nice and useful if supported in L2E queries. We got some places where we process potentially big lists in multiple steps and in the end do some result select for the collected Guids.
Guid bigIDList = ...; // Usually around 50 but sometimes more than 100,000 IDs
return ctx.Addresses.Where(x => bigIDList.Contains(x.ID)).ToList();
I need that! release it as quick as possible
this will help in Bulk insert/update/delete
you have my vote as it will deal with batch crud too - as it does with odp.net
Maxime Lebel commented
You have my vote.
Ervin Czimskey commented
If you are counting votes, I'd like to see this feature in EF too.
I think this will be a value add...
abel lopez commented
It would be great if sql server table bear the type within the parameters of a procedure as it would have much use.
Example I have to do a procedure you need to pass a set of parameters and would be great if encapsulated in a class.
There are other applications of this functionality but the most important thing is to use the user-defined types anywhere in the code. If you have increased the treatment of the model layer. To do procedures that can be written in C # I think the final touch would be to put the data types abstract classes as parameters of procedures.
I hope they understand our needs at the time of giving solutions to practical problems and complicated business rules and to make object-oriented programming tool that helps us to really set in stored procedures in SQL Server
Shiv Kumar commented
Its time EF supports this feature in 2012.
Various times we require this , not every time could we use xml or other types . Please help us out !!!!!
Venkata Rao Venkamsetty commented
I am surprised to know that Linq to SQL does not support Table Valued Parameters. will this be fixed? or it is decided not to address this?
John Saunders commented
Ironically, I just found a need for this yesterday. I have what would have been a simple join (find information on a set of people) except that the set of people comes from a stored procedure from a different database running on a different server. I'm already using LINQ to Objects to join these two sets of data, so if I could pass the first set as a parameter to the SP that produces the second set, that would be great.
Catalin Adler commented
This is a very usefull feature. We are all trying to squeeze max perf from sql, so we dont loop and call sql code, we accumultate the arguments intro xml/table type and call sql only once.
This would be a very usefull feature.
This will support batched updates