This user story is to address the DB improvements identified in CPS-81:

"I’ve gone diagonally through the schema and beside minor optimizations that I would not bother with – do you need the dataspace in the fragment table? Looks like that’s inherited from the anchor. It would chop one column and one index on your biggest table at the price of a fully indexed join through a relatively small table. Same story with schema set if possible, if we really get stuck with query performance we push additional fields in the tables later.

Other than that  - LGTM, are you thinking already of partitioning the fragment table (a candidate would be anchor id)?"

• Determine concrete changes required based on above feedback in a 'Implementation Proposal'
• Agree changes with team
• Implement changes (update liquibase DB version?)