I do experiment with LINQ since some time. Typical method to enumerate through a collection and change some of its properties in my code would look like:
ATDataContext dc = new ATDataContext(Settings.connection_string); int[] col = ListViewClass.getListViewSelectedPositionTags(listView); try { foreach (var item in col) { var ctx = (from r in dc.MailingLists where r.ID == item select r).Single(); ctx.Excluded = 'Y'; ctx.ExcludedComments = reason; } dc.SubmitChanges(); }
Some time a have got an advice to do this by... seems like much smarter way:
var ctx = from r in dc.MailingLists where col.Contains(r.ID) select r; foreach (var item in ctx) { item.Excluded = 'Y'; item.ExcludedComments = reason; } dc.SubmitChanges();
Iit makes sense on so many levels and I love this solution. It’s smart and faster than the first one.
I have used this solution in a production environment for some time.
What was my surprise after few weeks when searching an application log files and see this:
"The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RCP request. The maximum is 2100."
The LINQ to SQL converts where col.Contains(r.ID)
to IN
clause looking something like:
WHERE ID IN (@p1, @p1, @p2 … )
The col
collection reached (in my case) more than 2100 elements and the query failed to perform. I have done some research on the problem and what I ended up is:
“… Maximum number of parameters in the sql query is 2100. There is more limitations, like the fact that the whole query string cannot be longer than 8044 characters.”
I have loved the second solution so much. I am so disappointed with these hard-coded limitations of the SQL Server.
Did I miss something? Is there anything I can do to be able to use the “where col.Contains(r.ID)” version?
Regards Mariusz
ps. (I use Win XP, C# with LINQ and SQL 2005 Express).
Show activity on this post. According to MSDN, SQL Server limits the number of parameters per stored procedure to 2,100.
Yes, there is a limit, but Microsoft only specifies that it lies "in the thousands": Explicitly including an extremely large number of values (many thousands of values separated by commas) within the parentheses, in an IN clause can consume resources and return errors 8623 or 8632.
A stored procedure can have a maximum of 2100 parameters specified. Each parameter is assigned a name, a data type, and direction like Input, Output, or Return. If a direction is not specified, then by default, it is Input. You can specify a default value for the parameters.
The limits are hard-coded:
I wrote some code before that split the Contains
query into batches and combined the results... see here for more.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With