Re: Using Schema Diff in SQL Developer - fails to function

[Quoted] On Jun 5, 12:51 pm, sybra..._at_hccnet.nl wrote:
> On Tue, 05 Jun 2007 11:40:24 -0700, oaksong <oaks..._at_hotmail.com>
> wrote:
>
>
>
> >I'm trying to compare two database schemas with Schema Diff in Oracle
> >SQL Developer. It worked, once. I've not been able to get it to work
> >again. It reports no errors and it does nothing. That is, the feed
> >back bar pops up and slides across a couple times then puts me on the
> >output tab, which is empty.
>
> >Any suggestions would be appreciated.
>
> >Details:
> >I'm mapped to two versions of my database, development and production.
> >I'm trying to generate a script to update production to look like
> >development. The one time the Schema Diff ran and produced output I
> >got all of the necessary script to perform the changes.
>
> >The script was run, but generated quite a few errors. At this point it
> >would save a lot of time if I could get the Diff engine to produce a
> >script that I could review and run in pieces. While I can view the
> >schema components via the SQL Developer interface, the Diff engine
> >fails to perform.
>
> >tia
> >Chris
>
> According to my dictionary 'fail' can have multiple meanings. My
> crystall ball doesn't manage to see what failure you have.
> Also, do those Oracle databases by any chance have version numbers
> inscribed on their shirts?
> Care to share them?
>
> --
> Sybrand Bakker
> Senior Oracle DBA

[Quoted] Your crystal ball apparently doesn't come with glasses, since I clearly stated that no output was produced. That's a failure in my book. If you compare two things that you know have differences and the software doesn't display the differences, it's failed.

Version is irrelevant to this process. The process generates ddl and then looks at the ddl from the schemas and compares them. I could be comparing MS SQL to Oracle and I should still get output. As it happens the databases are both 10g2.

I've also just discovered that the script this tool produced was dropping many of the columns immediately after it was adding them, so I think the Oracle SQL Developer tool needs to go back to the shop for some work. It's behavior is somewhat less than logical. I don't like to be an un-notified Beta tester, which appears to be my current position vis-a-vis this product, but it wouldn't be the first time some major vendor has put out a badly tested tool. Received on Tue Jun 05 2007 - 21:11:18 CEST