Stream: implementers
Topic: HAPI FHIR on MSSQL - 2100 SP parameter limit
Veliyan Georgiev (Feb 04 2019 at 16:28):
Hello all. I posted this in the google group as well but I figured I'll pick your brains here too.
we are testing HAPI on top of MSSQL in Azure in order to get a benchmark on the performance for large deployment and it seems like we hit a limit.
Our server has 50K patients so far and 8 000 000 observations total.
The following query works on the public FHIR server
http://hapi.fhir.org/baseDstu3/Patient?_has:Condition:subject:code=http://snomed.info/ct|73211009
but on ours it errors out like this
{
"resourceType": "OperationOutcome",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.</pre></td>\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t</tr>\n\t\t</table>\n\t</div>"
},
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request."
}
]
}
It looks like it has something to do with the 2100 parameter limit per stored procedure described here
Any thoughts on how to get around it?
Grahame Grieve (Feb 04 2019 at 19:46):
@James Agnew
Last updated: Apr 12 2022 at 19:14 UTC
