Project transfer from eapx to SQL Server 2017 extremely slow then fails

[Sunshine]

So I'm now in a different organization getting a central DB setup on SQL server and in meantime creating content in a eapx file whilst the DB server is being set up. Today I get a message saying the DB server is ready. I try and do a project transfer from eapx file to SQL server using a OLEDB connection and it takes forever (5+ hours) then flags an error and stops. The result is a partially filled DB. The objects are there but the diagrams aren't populated. Bah. Tried again and similar result.
The eapx file is around 80MB so not big at all. Network upload speed is 100Mb/s whilst not super fast should be good enough.
Had a similar issue in my last organisation and put it down to some qwerk in their environment but again I'm seeing slow performance with project transfer from eapx to SQL server. Didn't get to the bottom of the problem in my last organisation.
https://sparxsystems.com/forums/smf/index.php/topic,46306.msg271102.html#msg271102 
Just wondering if anyone has any thoughts/experience on getting data in an eapx file to a Sql Server other than what I've tried.
I'm thinking maybe doing blocks of xml export/import and ref data export/import for graphics, scripts etc. but pretty sure XML is slow too.
Or maybe transfer to feap file and then from that to SQL server. Anyone done that?

[Geert Bellekens]

80 MB eapx should transfer just fine.

Things I would try

- Run a project integrity check on the eapx file
- Delete all auditing and baselines you don't need anymore
- Compact the .eapx file
- Install SQL server locally and try a project transfer to your local database, then do a backup and restore the backup on the central server
- Transfer to another .eapx file and then from the fresh .eapx file to the SQL server
- Transfer with the new v16 64 bit edition

Transfer from .eap to SQL Server is a lot slower than from SQL Server to .eap, but it should finish in the end.

Geert

[Sunshine]

Thanks for those suggestions Geert. Done a few of those already but you've given me some more to consider which is was I was hoping for.
Integrity is good
Audit is not activated
Compacted
Installing SQL locally is not an option due to organisations policy of DB not being on client machine. Yeah I know pain in the a**.
V16 not allowed as not fully released yet.
which leaves the transfer to another eapx or feap file then to SQL.
Might try ODBC driver too if that doen't bear fruit.
Will give them ago tomorrow.

[Geert Bellekens]

Installing SQL locally is not an option due to organisations policy of DB not being on client machine. Yeah I know pain in the a**.
V16 not allowed as not fully released yet.

In some cases it helps if you ask for a virtual test machine in (Azure, or somthing), or remote desktop access to a server or the likes.
You don't even need access to the corpurate network. All you need is to be able to upload an .eap(x) file, and download an SQL server backup file.
After all this is only temporary until you have a succeeded in transferring the model to SQL server.
After the transfer they can delete your test machine

Geert
Geert

[Sunshine]

Thanks Geert might try that if the feap to sql server fails. Process is under way right now. Seems to be chewing through t_objectproperties at moment. Count 14,000 out of 17,000 so far after 1.5 hours. Worth noting this is using EA V15.1.

[Sunshine]

Okay transfering the eapx project to feap(which took 15min) then to SQL was successful however still pretty slow taking around 4 hours or so.

[Geert Bellekens]

Okay transfering the eapx project to feap(which took 15min) then to SQL was successful however still pretty slow taking around 4 hours or so.

Cool, I'm happy you got through it.

Geert