This content has been marked as final. Show 2 replies
IIRC CAS 3.0 Record Store only supports random access via one or more record IDs, and these are unlikely to be your join key to your database. You also can't do a filtered-scan of the whole store.1 person found this helpful
There's a couple of ways you could tackle this, depending on how often you need to refresh, the number of records you are refreshing etc. Assuming your Record Store is large, it may not be practical to read it all and build the hash for the join-key. Instead, you could read the entire Record Store, and for each record perform the lookup to your database (which should have an index on those columns), returning zero rows if the record does not require update. This approach will be least attractive if the Record Store takes a very long time to scan-read, and there is a very small number of records to update.
Thanks Brett, this could be a one time operation so I will use your suggestion of reading entire recordstore and do a lookup.