consider looking for ways to reduce the size of your table. food for thought:
- in database design, normalization adds reduces duplication and adds integration checks. I've found that large tables can be reduced to many smaller tables through normalization techniques.
- similar to nested conditionals, consider if statement literals before your large decision table.
I've been able to load a DMN with 100k decision rows a few years ago. attempt to load 100k, and 200k etc. until hit a limit. it is possible you can have 4 DMNs with 100k each, chained together.
When I see DMNs that big I start asking, does this data belong in a database.