When you select the Working Set mode, a working set of persistent objects in the transaction currently being replicated is maintained in one or more files not related to the map files defined in the production database.
The Working Set mode consumes the least amount of disk storage capacity but does not support extract data functions, query applications, or takeover from the RPS node.
For historical tables, Binary Large Object (blob), String Large Object (slob), and StringUtf8 Large Object (slobutf8) values are NULL when the object is updated.
Mapping methods and virtual properties executed in Working Set mode raise an exception if they access any persistent objects that are not in the current transaction.
Mapping methods from a subschema copy class in Working Set mode raise an exception during extraction on the primary node.
You can neither create nor use a working set database from or with an encrypted primary.