Author Topic: various releases - 16.1 + 15.0 with dbms scheme - 1558 ?  (Read 2038 times)

martas

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
various releases - 16.1 + 15.0 with dbms scheme - 1558 ?
« on: January 07, 2023, 02:02:38 am »
Hi,

we have recently used version 15.0 , now we have upgraded 3 pcs to 16.1 (but most  - about 30 stays at 15.0).
But when I choose help-about, I see the latest dbms schema, which seems to me weird .
It says:
Connection /DBMS:OLEDB -MS SQL Server
Database Schema Version:1558

Any knowledge about this ?

Can there be any issues ?









Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13387
  • Karma: +566/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: various releases - 16.1 + 15.0 with dbms scheme - 1558 ?
« Reply #1 on: January 07, 2023, 04:13:34 am »
The database is at the schema it is. That is not related to the version of the EA client.

Geert

martas

  • EA Novice
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: various releases - 16.1 + 15.0 with dbms scheme - 1558 ?
« Reply #2 on: January 09, 2023, 07:34:19 pm »
The database is at the schema it is. That is not related to the version of the EA client.

Geert

So isn't there absolutely no impact of the database schema to the functionality of the client ?
And not problems if the schema is at version which came later than the client ?


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13387
  • Karma: +566/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: various releases - 16.1 + 15.0 with dbms scheme - 1558 ?
« Reply #3 on: January 09, 2023, 07:54:56 pm »
The database is at the schema it is. That is not related to the version of the EA client.

Geert

So isn't there absolutely no impact of the database schema to the functionality of the client ?
And not problems if the schema is at version which came later than the client ?
In most cases that is not a problem. Sometimes they publish an update to the schema that is not backwards compatible, but that ususally gets a warning.
They recently did that for the t_images table. If you apply that update you can't use the model with versions before 15.

Geert