-
Notifications
You must be signed in to change notification settings - Fork 3.3k
[release/10.0] Fix parameter limit (because of sp_executesql). #37334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
cc @artl93 |
artl93
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cincuranet - I remember we took something similar recently. Is this related to a similar issue? I also note that this is customer reported - is this related to another issue? The one that's linked is opened by you. Thanks!
|
Ahh... I see it now, related to the other PR up for approval - this all relates back to #37185. |
|
Yes. |
artl93
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Customer reported, part of complete fixes related to #37185. Regression fix. Approved.
|
Approved via email. |
Fixes #37336.
Description
This change fixes an incorrect maximum limit for SQL Server parameters. Although usually the error states 2100, SqlClient uses
sp_executesqlwhich takes 2 parameters and hence the count needs to be adjusted.Customer impact
Query fails to execute when collection with 2099 or 2100 parameters (exactly) is present in the query.
How found
Customer reported on 10.0.
Regression
Yes.
Testing
Tests added.
Risk
Low. Quirk added.