March 20, 2007 at 4:44 am
The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
we are getting this error when sending the message with a prepared statement and passing the values as SQL parameters.
is there a different way to do this or is there a way to increase this limit in SQL 2005 STD version?
March 20, 2007 at 6:22 am
Do you mean that you've passed in more than 2100 parameters? If that's true, you might want to change your calls and send in XML that you can shred on the back end.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 20, 2007 at 6:30 am
we wanted to avoid the additional coding for the XML and also the overhead of the XML.
therefore we chose this solution. but obviously this doesnt work with MS SQL 2005.
March 20, 2007 at 6:41 am
There's no doubt that XML does add overhead, but from the sounds of things, you're probably well within the range that justifies it's use. What kind of functionality is it that requires passing in 2100+ parameters? Maybe there's another way to skin the cat.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 20, 2007 at 6:54 am
one of the scenarios we are dealing with is updating or inserting rates for flights for the next year. this has multiple different rates for business, economy, loyalty programs,... so thats summing up to over 2100 parameters pretty fast and we exceed this value.
this only occurres in a few cases as most of the inserts or updates will be way below 2100 parameters but still we would need this bigger updates too.
March 20, 2007 at 7:02 am
Oh yeah, I'd go with XML. It's a bit of a pain to code, but you can make it scream (except for the memory overhead) for performance. It directly supports the kind of requirements you're talking about here.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 20, 2007 at 7:13 am
thanks a lot for your help, we will go with XML then
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply