Large Dataset Query

RE: Large Dataset Query

Chris — Mon, 03 Oct 2022 19:46:34 GMT

Agree with Mike - by filtering under a!queryEntity() you should only need to retrieve 1 or 0 rows to determine if the item is present (and get the details on it). Aside from [most often] not being necessary, retrieving 50,000 rows in batches of < 1 MB, during each scan, would be a nightmare for performance.

We have one MSSQL table with 7 million rows which is queried 2,000+ times a day for a subset of 0 to ~10 rows each time, runs like a champ.

RE: Large Dataset Query

Mike Schmitt — Mon, 03 Oct 2022 19:31:00 GMT

These sound like standard use cases for a!queryEntity() - the only time you'd have issues is if you're trying to retrieve several thousand rows of data all at once, but the use cases you list here don't seem to indicate a need to do that.

For instance, querying an item from a 50,000 row DB to match a single scanned bar code, I would not expect to be any sort of difficult thing for a normal query filtering by, for example, a barcode number field.