DB transfer long times

[Bill McCracken]

Has anyone found tips/techniques to speed up DB transfers?  

I'm uploading to a Production Oracle DB farm (many servers) and the duration of the local model (.EAP) to the Oracle repository is well over 2 hours.  This seems unreasonable.  The model is about medium size and not overly complex.  Is there any tuning that can be done besides the obvious backend dropping / rebuilding of index.  BTW, I couldn't if I wanted to due to Oracle permission issues with the DBAs who won't let this happen.

t_objects table alone is taking well over an hour to 2 hours.

Ideas?

Thanks,
B

[qwerty]

Once I measured transfer times MS SQL Server <-> EAP. I found that SQL->EAP was 7 times faster than EAP->SQL. A bit funny I thought since the SQL Server should be a lot faster than a toy MS Access DB. Well, I was proven to be wrong. I have not investigated the reasons since I was no DBA and did not care too much. I guess the reason is simply the right tuning. Probably the DBA had "tuned" the server...

q.

[Sunshine]

Have you done any analysis on where the bottleneck is?

EAP File to Oracle suggests the following areas to investigate
a) Reading of EAP file from disk
b) Network data transfer rate
c) Writing to Oracle DB

One thing you could try is putting the EAP file on a SSD so that should improve reading the EAP file  but if its not the bottleneck then it won't help. But it may help isolate the cause.

When you say "medium size" what are the metrics i.e. File size of EAP file. numbers of objects and relationships. Maybe others can share their metrics for you to compare.

[Geert Bellekens]

Bill,

The project transfer feature is something that wasn't designed to be used on a regular basis, so I can imagine that speed wasn't the one of the priorities.

For me the question is why you need to to this on a regular basis. I suspect that there are other ways of achieving your requirements without using the db transfer.

Geert