Project transfer problems

[Luigi2021]

Hi,

I am using EA (15.2.1559.26) together with a MSSQL 2008 Database and I have issues with transfering from a file to the MSSQL database. The source file I use is the output of a transfer from MSSQL to the file. This is the error I get:

Code: [Select]

An error has occurred: DAO.Field[0x0000bdb]
Insufficient system resources (translated from Dutch)
[Select * from t_document]
Field: bincontent

Press OK to continue to the next row (this record will be lost). Cancel to abort.

The log file looks like this:

Code: [Select]

  ERROR: *** t_document - record no: 738 Key: docid={5C162AA6-69C8-438c-BD1C-00C5AEE1E12B}
  ERROR: *** t_document - record no: 739 Key: docid={5C313952-2F63-4618-8D5A-9C4B41C16C70}

Opening the eapx file with Access I noticed that most of the docid where from baselines, but not all of them.  After removing the baselines manually in Access (Couldn't remove it from within EA because of errors) the project transfer worked with some errors. Before removing the baselines from the EAPX the file transfer never finished and stopped somewhere when processing t_document.

How can I transfer the EAPX to MSSQL with all data, including baselines?

Thanks in advance!

[Geert Bellekens]

How can I transfer the EAPX to MSSQL with all data, including baselines?

You probably can't. Insufficient system resources probably means a limit has been reached on the memory usage.

There is a small chance it works with the new v16 64 bit edition, and that may be able to use more memory than the 32 bit edition.

But on the other hand, do you really need those (probably huge) baselines?
Are you really going to use them ever?
If they are that big, they are probably useless anyway.

Geert

[Luigi2021]

Hi Geert,

Not all of the missing t_document records are baselines, some of them are linked documents  I think it's kind of tricky that you can transfer it one way but not back.
I am going to try if your 64 bit suggestion works.

Note:
I just transfered an MSSQL to MSSQL (2008) with huge baselines without any problems so I looks like the MSSQL part can deal with large baselines both reading and writing. The transfer from MSSQL to eapx succeeded so I still don't understand why EAPX->MSSQL can't work.

[Geert Bellekens]

Yeah, the transfer from MMSQL->eapx and eapx->MSSQL is very much assymetrical.

MMSQL->eapx usually takes only a few minutes, wheras for the same model eapx->MSSQL takes hours (or days)
I haven't figured out why there is such a big difference.

Geert

[Guillaume]

Hi,

Have you tried using the Native XML project transfer ?
You can export your EAPx to local XML files, and then run an import on your empty SQL Server (with EA tables) to see it if sorts the issue out.
Note: if your linked docs are no longer required, you could even remove the t_document*.xml files from your folder before running the import.

[Luigi2021]

I finally got it working. I have downloaded the EA 16 RC and migrated the old eapx file  (which was complete afaik) to the new file format after this I transferred the new file to the MSSQL DB.

Thanks for all the support!