Prevent Narrative Cache update from exceeding the parameter limit in SQL Server #263
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale
The maximum number of parameters allowed by SQL Server is 2,100. When more than 2100 animal events are inserted (via the ETL process), the update fails with this error message:
Caused by: org.springframework.jdbc.UncategorizedSQLException: ExecutingSelector; uncategorized SQLException; SQL state [S0001]; error code [8003]; The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
Changes
This commit reduces the cutoff for the narrative cache to be truncated and reloaded from 10,000 to 2,000, which is less than the maximum of 2,100 parameters.