#Best Practice for promoting DataStore updates: How do we handle this

senthilar over 9 years ago

#Best Practice for promoting DataStore updates:

How do we handle this scenario -
we have a main CDT in our application. An Entity and DataStore are created for this CDT. Now, this CDT structure changes. We manually drop the tables and sequences (using SQL Developer) and then publish the DataStore again. This is fine for Dev environment.

Now, how do we promote this DataStore to QA? Do we have to manually drop all tables and sequences and then import DataStore and then Publish them? This will result in all data getting wiped out. Is there a way to do this more straight-forward?
...

Discussion posts and replies are publicly visible

0 siddharthg521 over 9 years ago

I am not sure why do you want to drop the entire table? If your CDT structure has changed - let's say changing the data type of one column, then you can execute the necessary SQL query to update that column data type in the database and once done, you go and re- publish your modified CDT to the same data store, it will verify the mappings successfully and you will be able to publish the change.

Therefore, now to move it to QA, before deploying the data store package, run the sql command successfully in the database and then inspect/import your package and your database and CDT will reflect the latest state and will be in sync without actually dropping the entire table.

If this does not answer your problem, could you please tell what exactly your use case is or what are you eaxtly changing in your CDT?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel