MySQL DB migration problem

[Pawel Zubkiewicz]

Hi,

I've got repository on MySQL db and I need to move it on another computer.
I've exported whole DB using MySQL Workbench to SQL file (structure and data). Then, I imported it into new instance of MySQL db on another computer. Everything worked ok, there are tables, data etc.

When I try to connect to the repo from EA I get this error message "There does not appear to be a model in this repository".

What should I do? Any idea how should I export/import the database?

[Geert Bellekens]

Pawel,

Probably the easiest way is to create the structure of the database using the standard database creation script, and then use Project transfer to transfer the model to another database.

I often use a .eap file as an in-between step. This hardly seems to slow down the process, and at least you have an extra usable backup in case something goes wrong.
So MySQL(1)->.eap->MySQL(2)

The model transfer function can be found at Project|Data Management|Project Transfer

Geert

[Pawel Zubkiewicz]

Thank you Geert, we can always count on you :-)

[sdgasster]

Hi:
I followed the Sparx/EA instructions on setting up the DB (MS SQL), loading the initialization script and then importing my .EAP file.
I can see the model/project just fine.
I then gave users access to the DBMS and then created groups (users) and added users to the project and users group.
They can login to and get to the DB but once they connect they see the error message:
Error: There does not appear to be a model in this repository. Do you wish to transfer a model to the repository?

I'm pretty much stuck at this point.  For some reason the users can't see the model.
Suggestions welcomed.

Thanks.

-- Sam

[sdgasster]

I think I solved that problem - this was at the DBMS level - I needed to add read/write/edit permissions at the DB level.
Next problem seems to be that as admin I can get in fine but none of the users can get in with their user ID (we are using Windows authentication).  My regular user account isn't working.  Any lessons learned on that would be welcomed.