Project Transfer - Out of memory

[metasprite]

Hi,

I am trying to transfer data from MySQL to SQL Server (on different virtual servers), however keep getting an EA error that says:

An error has occured:
Microsoft Cursor Engine [-2147024882]
Out of memory.
Press OK to continue table upgrade (this record will be lost),
Cancel to abort

I am using the Project Transfer option under EA -> Tools -> Data Management (DBMS to DBMS) on our virtual server running EA 7.5 Build 850. I am trying to send our MySQL data to our SQL Server database, which will be used by the latest version of EA.

The virtual server that is being used to run the Project Transfer is running Windows Server 2008 R2 Standard, 64-bit.

The log files of each attempt get up to varying stages of the process, the furtherest being Copying project information for: t_snapshot.

Any help on this would be great!

Cheers, Donna.
[original message]

[F Cantoni@localhost Paolo F Cantoni]

Hi Donna,

Firstly, make sure there are NO internal problems with your repository by performing a Tools |Data Management >Project Integrity Check... [Shift+F9]

If that doesn't fix anything, try transferring to an intermediate EAP file.

HTH,
Paolo
[original message]

[qwerty]

t_snapshot contains the auditing and might be quite large.

q.
[original message]

[metasprite]

@Paulo - thanks for your suggestions. I cleaned up the data integrity and tried again, but same error as before. I tried to transfer to an intermediate EAP file, but again, got the same error as before.

@qwerty - thanks for that suggestion. I completely emptied the source t_snapshot table, but again the same error.

Any more suggestions would be great!! Keep them coming...
[original message]

[Bellekens@localhost Geert Bellekens]

Just a thought; are you sure you're sql server database has enough allocated space (and/or is set on auto-grow)?

Geert
[original message]

[F Cantoni@localhost Paolo F Cantoni]

Well, Donna, I didn't notice you were running EA 7.5.  Download a trial of 9.3 and see if that fixes the problem.  Then at least you'll have something for Sparx Support.

BTW: you should frequently check the integrity of the repository as all sorts of wierdness can happen.  In particular, Sparx have occasionally improved the integrity checking so do it again using 9.3 before attempting the transfer.

Paolo
[original message]

[qwerty]

Here's another straw: try exporting the whole repository as XML. Additionally export the reference data. Vice versa import reference data and XMI in a blank model.

You might loose some information (IIRC images are not re-connected correctly on ex-/import, diagram references might be lost and probably a few more quirks). But at least you will be able to create a copy of the most important things.

q.
[original message]

[metasprite]

Hi all,
Many thanks for your help with this. I managed to get this to work by:
- Clear audit data from t_snapshot
- Set Source Database MySQL ODBC to: Don't cache results of forward-only cursors, and Force use of forward-only cursors
- Turned off WIFI so only LAN was used
- Transferred in a two-step process: (i) From MySQL local to SQL Server local, (ii) From SQL Server local to SQL Server at data centre.
Thanks again y'all!
Cheers, Donna.
[original message]