It is possible to migrate the self service model to a different database?

Table only, no stored procedures used.

It looks like once I choose the DB it doesn't want me to switch without starting a new project(I can understand this databases are different). Do I have to redo all the changes I made to my existing project, for a new DB?

My derived entities shouldn't have a problem should they?

This is for a small project 30 tables, we don't need the extra control/hours of work that the adapter offers. (We are happy with self service, it is called lazy for a reason right. )

I'm sure it is possible, but is it easy? Are there things I should do to make this easier if I ever need to do this?

Short answer please I don't want to waste your time with this.

Thank You,

Gabe Nodland

Different database as in: another catalog / schema or you want to move from oracle to sqlserver for example?

I was thinking identical table structrue, SQL to Oracle.

GabeNodland wrote:

I was thinking identical table structrue, SQL to Oracle.

That's not that easily converted, I'm afraid as in: flip a switch and it works. Best you can do is re-generate a new project on the oracle db.

Adapter is equipped for this, selfservicing is a bit cumbersome in this area.