Book a Demo

Author Topic: Migration Repository  (Read 3414 times)

Alain PERSIN

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Migration Repository
« on: November 12, 2020, 07:25:57 pm »
Hello !
I am using EA and my repository is hosted on a SQL Server 2008 R2 database.
I need to move this database to a SQL Server 2014 instance.
How can I do ?
Should I create an empty database on the target instance and do a repository transfer?
Will there be a compatibility issue if I upgrade from 2008 to 2014 SQL Server Instance?
Thanks for your feedback.
Regards.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Migration Repository
« Reply #1 on: November 12, 2020, 07:39:59 pm »
Should be no issue. Use the DB creation scheme from Sparx and then trigger a Configure/Model/Transfer or where ever that in your current EA version might lurk) in EA from the old to the new DB.

q.

horszasz

  • EA User
  • **
  • Posts: 22
  • Karma: +6/-0
  • My name is Gergely :)
    • View Profile
Re: Migration Repository
« Reply #2 on: November 12, 2020, 07:47:03 pm »
Hi,

Should I create an empty database on the target instance and do a repository transfer?
Definitely yes.

Will there be a compatibility issue if I upgrade from 2008 to 2014 SQL Server Instance?
No, if you are using the most current database stucture in your 2008 DB , you do not need to calculate with any comptibility issue.

Regards,
Gergely

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Migration Repository
« Reply #3 on: November 12, 2020, 07:52:21 pm »
No, you can simply restore the backup from SQL 2008 on your SQL 2014
That is much much faster.

You may want to look at updating your schema to the latest if you have not already done that. (check the SQL server schema file downloads), but that is not strictly related to the SQL server upgrade.

After restoring the database you can set the compatibility level to SQL 2014 (I had some issues with performance when the compatibility level was set to 2005)

Geert