Automatic EA database schema "upgrades" / "downgrades"

[mtamme]

Hi!

We have around 30 EA installations which are connected to a shared PostgreSQL EA repository. Occasionally we experience some kind of database schema "upgrades" / "downgrades" when the "Version" property in the usys_system table changes from 4.01 to 7.0 or the other way around.

My questions are now as follows:

1) What's the reason for these version changes?
2) Why is only the version changed and not the "VersionDate" too?
2) How can this be fixed?
3) Are there also other changes happening in the database which we are not aware of?

Thanks,
Martin

[Geert Bellekens]

Martin,

Can you also explain how/why this is a problem for you?

Geert

[mtamme]

Hi Geert,

we just recognized the issue since we check the 'Version' property before we execute some SQL scripts via the EA Automation Interface. With this check we just want to ensure compatibility with the current EA database schema. Since we only checked for version 4.01, which is (what we experienced) the default for EA 9.3 till 13.5 we had a problem when suddenly version 7.0 appeared in the usys-system table. But after a while version 7.0 disappeared and version 4.01 was back again.

We didn't experience any problems right now, except that our compatibility check failed. My main question is, if there are some other changes going on inside the database during these "upgrades" / "downgrades" which we are not aware of or is there generally another way to check compatibility with the EA database schema?

Thanks,
Martin

[Eve]

From memory, enabling auditing upgrades the version to 7.0 to that versions of EA prior to version 7 know they shouldn't use it.

Disabling auditing either gives you the option of going back to 4.01 or does it automatically.

In a similar way, if you set a minimum EA version in the model options, it changes the version to something that old versions of EA that don't know about the option just set won't open.

[mtamme]

This was the answer I was looking for.

Thank you Simon!