Migrate EA repository from Oracle to SQLServer

[pcmoon]

Hello, I am looking for information on the process of moving our EA repository from Oracle to SQLServer.  Is the following information that I know correct and are there additional steps I am missing.

First create the necessary infrastructure on SQLServer to host the EA repository.

Second use EA's  Project Transfer tool under Tools | Data Management.  This tool can be used to migrate repositories from Oracle to SQLServer

Third, done?

[qwerty]

Tools/Data Management/Transfer

q.

[pcmoon]

Tools/Data Management/Transfer

q.

So I have started this process.  I have used the transfer tool on the first three projects, with 20 more projects to go.  It appears that after every transfer, instead of a new project being added to SQL, the transfer instead writes over the previous project.

I'm obviously missing something here.  I'm looking to have all 23 projects transferred and not just overwriting the previous transfer.  Any help would be greatly appreciated.

One question that would shed light on this is do each of the 23 projects need their own repository on SQL, or can they use one repository?
Right now I would believe that each project needs its own repository separate from the other.

[qwerty]

Yes, it writes over the old one, replacing it with the transferred one. The reason is that you need the schema first. It does not create it on transfer. And when you transfer it overwrites the old contents.

q.

[pcmoon]

Yes, it writes over the old one, replacing it with the transferred one. The reason is that you need the schema first. It does not create it on transfer. And when you transfer it overwrites the old contents.

q.

I'm afraid I need a little more hand-holding.
I should flesh out experience level and needs first.
Experience with EA: None
Role with EA with organization: Administrator!
Experience with Oracle/SQLServer: None

After assuming the administrator role from a previous employee, I've managed to resolve missing credentials issues for EA (with your help).
Now our Architect want to move the 23 projects that are currently in Oracle DBMS to a SQL DBMS.  I haven't found information on the process of doing this (more than the information provided by you, and the help documents which mention the same process).
I've contacted my Oracle dba and he has told me has no knowledge on EA or its use/structure within his db, and he "isn't the person to ask".
Our comapany is hem-hawing about updating to the current version of EA, which would possibly allow me to more KB articles about this situation, but until they decide what they want to do I'm in a position of writing a wall of 'woes me'.

My SQL dba created an initial repository and used the install script provided by Sparx.
I can transfer one project to the repository.  Transferring more projects overwrites previous transfer (as stated by you, and the EA program when submitting transfer).
I'm not familiar with schemas, but if that allows one repository to hold multiple separate projects, I'm all over learning about it and how to do so.
If instead the SQL dba needs to create an additional 23 repositories in the same manner that he did the first but with names that reflect the project, then hey that was easy!

Thanks for your time, it is appreciated.

[qwerty]

Ok. Here are a few guys that have Oracle experience, but not me. If you get stuck there you're best served at SO or one of the more DB-related affiliates.

What you basically need is either a DB user or windoze authorization. You can go with both in EA. Start with a DB user and do that LDAP stuff later. Once you have the user, create the Oracle scheme from the scripts provided at Sparx resource page (look for sql, oracle, script, schema, EA on Google or try your best with the forum search since it has been linked here in other threads). Once you have the schema script create that. Now you can issue the transfer. EA will ask for the credentials and you can connect to the target scheme. Open the source and kick it off.

q.

[Geert Bellekens]

If instead the SQL dba needs to create an additional 23 repositories in the same manner that he did the first but with names that reflect the project, then hey that was easy!

Yes, that is exactly what he needs to do to replicate the setup you had on oracle.

On the other hand, 23 repositories is a lot. I don't know the size of your company, but judging from the fact that you have to figure out everything yourself I'm guessing it is not too large.
Are you sure you need 23 repositories?
If you want to add the contents of a repository to another repository you need to use xmi export/import.
If I were you I would try to end up with the smallest number of repositories possible (ideally only one for your production environment) as that greatly reduces maintenance overhead.

Geert

PS. You might want to consider hiring an EA consultant for a day or two to help you out with this mess and avoid disasters.