Within Oracle, you would no doubt simply use an MV for this purpose. Looked at another way, the data synchronization process, especially if incorporated into a scheduled task, is a poor man’s way of implementing materialized views. In the example below, the comparison is between the same table, with the “2” version missing a row present in the source.Ĭonsidering only Oracle, what does this process sound like? Materialized view should come to mind. Select a source, select a target, select what it is you want to compare (i.e., table to table), and view the results. No calls to an otherwise busy DBA are needed. For someone with lesser knowledge of SQL syntax, the point and click interface offered by TDA has an immediate return on enhancing the user’s productivity. In pure SQL, it is likely to be a trivial task to do a minus between the tables. Suppose a user suspects that a table is missing some data, and the user knows he has a good source elsewhere. Not only can you compare data, but you can synchronize as well (with the exception of Excel). Any database system TDA can connect to is eligible for use as a source or target when it comes to data comparison. Again, it is not just tables within the same database or schema, but between many database systems. Follow the steps within the easy to use Data Compare Wizard, and just like that, you have a means of detecting changes between tables. Open a table, right-click it and select Data Compare from the context sensitive menu.

A simple means of comparing data can not only be automated, but also reported upon. So now that we can easily automate reports, pretty much anything you can use reporting for is at your disposal. TDA also allows you to use templates (think re-usable code), add exception handling, and change logging levels within the automation design process.

How to use toad for oracle