Best practice for very large linked data view

I am creating a linked data view, where the mapping file if translated gives:
“SQ074: Line 853: SP031: SPARQL: Internal error: The length of generated SQL text has exceeded 10000 lines of code”

Splitting up the mapping file into smaller parts would be nice, so I don’t mind this error per se.
I already made the creation of IRI and literal classes into separate calls, so that these are defined before my mega large "CREATE QUAD STORAGE " statement (which is mega because 96 tables are being mapped, see UniParc-sql-to-linked-data-view.sql · GitHub).

How should I use the alter quad storage command so that they are additive?

@jerven

Yes, the “SQ074: Line 853: SP031: SPARQL: Internal error: The length of generated SQL text has exceeded 10000 lines of code” error is the result of a know 10K limit on the size of SQL text.

Have you review this 16.5.12. Split Linked Data View which details how to use the alter quad storage command to split RDFViews across many tables ?

BTW, it seems you have 2 accounts on this forum as your previous posts were made as @JervenBolleman