OLE DB Error in SQL Server Repository

[Kiwi Fernz]

Has anyone had any issues with OLE DB errors when using a SQL Server based repository?  We have just created a SQL Server 2008 respository and while we can connect ok we get an Arithmetic overflow error when trying to add processes to a Business Process diagram.

We are using EA 9.0905 on Windows 7 and SQL Server 2008.

Many thanks,

[lance]

We are getting the same error. Some diagrams are now missing, and when we attempt to get latest (from version control and synch with model), we get many dialog popups with "Arithmetic overflow error converting IDENTITY to data type int."

I have sent sparx support inquiry, but have not gotten any response back from them. This is a major problem for us.

[Geert Bellekens]

No,

We've been running on SQL Server for years (now SQL Server 2008) and we recently upgraded from 7.5.850 to 9.1.905 but we don't seem to have such an issue.

Have you applied the latest SQL patches to update the database schema?
(see registered users section)

Geert

[lance]

Yes, we applied patches when we created repository. Our DB size is about 100MB. Error started a few days ago, and is effecting diagram references (cannot see diagrams under certain packages).

When we attempt to Get All from version control....dialogs of error popup again.

[Geert Bellekens]

Things I would do to try and figure out whats going wrong:
- Project Integrity Check (Shift- F9)
- Upgrade to 9.1.909 and check if the problem persists (don't go to 9.1.910 as there is a serious performance issue with SQL Server)
- Check the contents of the dbError.txt in the %appdata%\Sparx Systems\EA
- Transfer the model to an eap file and see if you have the same problem
- Contact Sparx Support with your findings

Geert

[lance]

Hmmm... we are currently using 910 (as recommended by SPARX)...

we have alread contacted SPARX...still awaiting their response

[Kiwi Fernz]

Hi,  Sparx support have identified the problem which is caused by  Object_ID field of the t_objectproperties table reaching the upper limit of SQL Server's int datatype.

The fix is to run the reset ID's feature:

http://www.sparxsystems.com/enterprise_architect_user_guide/9.0/projects_and_teams/reset_table_auto_increment_or_.html

This should fix the issue however in our case t_objectproperties was not included in the list of tables to reset so we had to use the following command to set the value to the lowest integer value possible.

DBCC CHECKIDENT('t_objectproperties', RESEED, -2147483648)

[lance]

Thanks! That help solve our problem with missing SDs. In our case 't_objectproperties' was included in the list of tables.

With everything restored, another problem presented itself. Some diagrams restored with objects moved around randomly. Other SDs that were recovered, do not have this problem and restored fine. Seems random.

I sent SPARX and email inquiring about this. Still have not heard back from SPARX regarding this problem we just solved...