So how exactly does the information inside a database within the area get upgraded just because a latest version from the software programs are being launched? To have an example, consider lookup data. Usually lookup data affiliates an ID (number) to some title (string) after which this ID is recommended in other tables rather than the the ID directly (i.e. stabilized). You will find other forms data that may be upgraded too.

In my opinion the response to this is "with difficulty". What are the tools that can help in creating data upgrade scripts? For instance, I personally use Toad's schema compare tool to create schema upgrade scripts but it doesn't perform the data. Would an ORM tool help here? The other ways exist to do this?

Red-colored Gate presently has an item for evaluating and implementing data changes. You are able to download a totally free, 14-day trial from -


Tom Harris

Red-colored Gate Software Ltd.

You'd update data by writing update statments inside a script. However, why you would like to update research data after which change existing records is beyond me. If you would like the worthiness to chance, then you definitely should correctly make use of a PK/FK design in which the id value is saved not the written text. Then you definitely only have to update the research table for the queries to mirror this. If you're storing the written text, that's normally for historic reasons and also you would wan to help keep that old value. For example syuppose we're speaking in regards to a parts list. A component known as a J2890 was purchased in 2008. This Year the part number for your part transformed to JS390, you wouldn't wish to alter the order detail table because that is not the part which was really shipped. That's the reason why you saved the title and never the id inteh to begin with.

I am presently evaluating Schema Compare for Oracle by Red-colored Gate although it isn't free and it is still at the begining of development.

If information is your only concern, I normally use stabilized SQL dumps (i.e., one line per row, sorted by primary key). I store them during my version control repository and that i may use any standard file compare tool to trace changes. It's most likely an ungly method however it has the benefit of its extreme simplicity :)

I personally use XSql. It compare both schema and data and convey scripts to synchronize your customer database. There additionally a free lite edition with a few limitation (it compare a maximum of 25 table, 40 sights etc.) that for me personally is enough. Anyway for those who have more objects to check it isn't to costly. Also I personally use XPO from DevExpress, witch can upgrade database schema from older version db, however i would rather begin to see the scripts I operate on my customer db, just to be certain which i don't accidentally remove important data.