V16 Beta on V15 Production Database

[BJTim]

It's hard for me to test the use cases with V16 in a completly separated test environment.
So I'd like to use the current beta with a V15 production database.
What is the risk within this scenario?
That it needs V16 to use features of V16 is clear.
Will V15 features used by V16 be corrupted? May the database become invalid and unusable?
I know, it's not recommended, but if you want early and profound feedback, the time I may invent in special tests is limited.

Greetings from Bruchsal, Germany
Bernd 

[qwerty]

Well, like with all beta SW on a production the risk will be a corrupt database and complete data loss. Sparx will for sure not promise anything else. It's rather unlikely, so if you're a daredevil: go on. If you have a "real" production environement then you also have a "real" test environment. If not, oure juggling with hot coals. Good luck.

q.

[Geert Bellekens]

I would probably risk it. Just make sure you have a proper backup schedule just in case something does go wrong.

Geert

[Sunshine]

Probably worth checking you've got the latest schema too before using V16
https://sparxsystems.com/resources/repositories/index.html#table_script_sqlsvr