If you're tracking down a specific change un-check all but the object types you have not interest in seeing.
In the first step of the Diff Wizard select the Source and Destination connections.Create database connections to the DEV and TEST databases to be compared (highlighted in blue above).This feature was also tested in JDeveloper 12.2.1.2. Here SQL Developer Version 18.1.0 which is a the current version as of this writing (July 2018).
All schema artifacts will be compared (tables, indexes, procedures, packages, sequences and, functions). In the use case described here there are two Oracle database schemas compared, one in DEV and the other in TEST. This topic is not a comparison of SQL Developer/JDeveloper to schema migration tools like Liquibase and Flyway but instead, a quick tutorial on leveraging this widely adopted Oracle tool for the list of schema differences. SQL Developer/JDeveloper will do this quickly and effectively.
#ORACLE SQL DEVELOPER TUTORIAL EXAMPLES UPGRADE#
However, there are times when you simply want to list the differences between two schemas quickly, producing a "Diff Report" and optionally to create the SQL to show the alters necessary to upgrade the destination schema. Undoubtedly for large database schema installations commercial schema migration tools like Liquibase or Flyway makes sense. The tools provide a database agnostic means to do this and to perform schema rollbacks if necessary. The tools provide a very controlled means of migrating schema changes from DEV to TEST and to PROD, the goal to preserve the underlying data. Liquibase by Datica and Flyway by Boxfuse are two such commercial tools. There are a class of tools whose job it is to managed database schema changes and provide the ability through the tool's own change logs to implement the changes to higher environments.
0 kommentar(er)
