Book a Demo

Author Topic: SQL Server 2014 compatibility ?  (Read 4986 times)

erlandi

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
SQL Server 2014 compatibility ?
« on: February 15, 2017, 02:24:36 am »
We are in the process of upgrading SparxEA from 12.1 to 13.

We are using SQL Server 2014 currently and when doing the upgrade we also planned to do the database schema upgrade from verison 851 to 1220.

However, when applying the EASchema_Alter851to1220_SQLServer.sql script on the database we get some problems. After the upgrade it seems like the textual contents in all "Text" elements in the model has disappeared and it's also not possible to set the contents in existing or new Text elements. The problems looks kind of similar to what's described in the following thread:
http://sparxsystems.com/forums/smf/index.php/topic,36058.msg231908.html#msg231908

We have the same issue also if we try to upgrade the database and use it with SparxEA 12.1.

Does anyone know if SparxEA 13 is supposed to support SQL Server 2014 ?

The information on the script download page says "SQL Server 2000/2005/2008/2012/Express and Azure"
http://www.sparxsystems.com/resources/corporate/#update-dbms

Is there any way to troubleshoot this to see if the issue is related to SQL Server 2014 or something else ?

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: SQL Server 2014 compatibility ?
« Reply #1 on: February 15, 2017, 03:02:01 am »
It might be related to the way you are connecting to the database.
Are you using the SQL Server OLE DB connector or a generic ODBC connector?

I'm pretty sure the version of the server is not the problem, although I have never tested it myself.

Geert

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: SQL Server 2014 compatibility ?
« Reply #2 on: February 15, 2017, 09:00:31 am »
As Geert suggests, the linked issue was caused by using the ODBC driver for SQL Server instead of the OLE driver as recommended.