Schema Comparison Nusiances 11.6.1

Discussion:

chuckoneal99

2012-12-30 22:09:08 UTC

I'm in the middle of comparing ~25 schemas for first of 4 separate environments to a baseline for the first of many times and want to point out a few annoyances in 11.6.1.

1. Select source schema definition file, click in and define target, OK to return to Options and the source is blanked.
2. The ellipse always open User Files. Two days later I have the revelation of copying all of the SDXML files there, but it would be nice if it could remember the prior paths.

My goal is to make this a repeatable process using the Automation Designer. I'm thinking I need generic schema specific source/target.SDXML files vs. the default SID/timespamped file names. Same goes for the sync scripts and report files.

This is an incredibly powerful combination of tools I feel is somewhat under-advertised. Who doesn't, or better, who shouldn't be routinely comparing development/test environments to pre-established baselines.

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/toad/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/toad/join
(Yahoo! ID required)

<*> To change settings via email:
toad-***@yahoogroups.com
toad-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
toad-***@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

John Dorlon

2012-12-31 14:52:17 UTC

Permalink

Thanks Chuck. Both are fixed in the next beta.

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of chuckoneal99
Sent: Sunday, December 30, 2012 4:09 PM
To: ***@yahoogroups.com
Subject: [toad] Schema Comparison Nusiances 11.6.1

I'm in the middle of comparing ~25 schemas for first of 4 separate environments to a baseline for the first of many times and want to point out a few annoyances in 11.6.1.

1. Select source schema definition file, click in and define target, OK to return to Options and the source is blanked.
2. The ellipse always open User Files. Two days later I have the revelation of copying all of the SDXML files there, but it would be nice if it could remember the prior paths.

My goal is to make this a repeatable process using the Automation Designer. I'm thinking I need generic schema specific source/target.SDXML files vs. the default SID/timespamped file names. Same goes for the sync scripts and report files.

This is an incredibly powerful combination of tools I feel is somewhat under-advertised. Who doesn't, or better, who shouldn't be routinely comparing development/test environments to pre-established baselines.

chuckoneal99

2012-12-31 15:40:03 UTC

Permalink

I've noticed another one while changing sources and targets multiple times in the same schema comparison window. After a new source connection is defined the schema drop down does not refresh. It does refresh the schemas after picking the new connection again from the drop down list. Shouldn't the schema dropdown refresh when the connection is established? I'm not connecting as a schema owner if that matters.

Post by John Dorlon
Thanks Chuck. Both are fixed in the next beta.
Sent: Sunday, December 30, 2012 4:09 PM
Subject: [toad] Schema Comparison Nusiances 11.6.1
I'm in the middle of comparing ~25 schemas for first of 4 separate environments to a baseline for the first of many times and want to point out a few annoyances in 11.6.1.
1. Select source schema definition file, click in and define target, OK to return to Options and the source is blanked.
2. The ellipse always open User Files. Two days later I have the revelation of copying all of the SDXML files there, but it would be nice if it could remember the prior paths.
My goal is to make this a repeatable process using the Automation Designer. I'm thinking I need generic schema specific source/target.SDXML files vs. the default SID/timespamped file names. Same goes for the sync scripts and report files.
This is an incredibly powerful combination of tools I feel is somewhat under-advertised. Who doesn't, or better, who shouldn't be routinely comparing development/test environments to pre-established baselines.

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/toad/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/toad/join
(Yahoo! ID required)

<*> To change settings via email:
toad-***@yahoogroups.com
toad-***@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
toad-***@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

John Dorlon

2012-12-31 15:57:44 UTC

Permalink

I see that. Also fixed for next beta.

Thanks.

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of chuckoneal99
Sent: Monday, December 31, 2012 9:40 AM
To: ***@yahoogroups.com
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1

I've noticed another one while changing sources and targets multiple times in the same schema comparison window. After a new source connection is defined the schema drop down does not refresh. It does refresh the schemas after picking the new connection again from the drop down list. Shouldn't the schema dropdown refresh when the connection is established? I'm not connecting as a schema owner if that matters.

Thanks Chuck. Both are fixed in the next beta.
Sent: Sunday, December 30, 2012 4:09 PM
Subject: [toad] Schema Comparison Nusiances 11.6.1
I'm in the middle of comparing ~25 schemas for first of 4 separate environments to a baseline for the first of many times and want to point out a few annoyances in 11.6.1.
1. Select source schema definition file, click in and define target, OK to return to Options and the source is blanked.
2. The ellipse always open User Files. Two days later I have the revelation of copying all of the SDXML files there, but it would be nice if it could remember the prior paths.
My goal is to make this a repeatable process using the Automation Designer. I'm thinking I need generic schema specific source/target.SDXML files vs. the default SID/timespamped file names. Same goes for the sync scripts and report files.
This is an incredibly powerful combination of tools I feel is somewhat under-advertised. Who doesn't, or better, who shouldn't be routinely comparing development/test environments to pre-established baselines.

ss052111

2013-04-23 19:29:33 UTC

Permalink

Another Compare Schemas problem. I'm running v11.6.1.6.

I've done my compare, and I'd like to run the sync script. I see my script, but the buttons "Save", "Move Script to Editor", "Move Script to Editor and Run Now", and "Schedule Script" are all grayed out. It seems the only option I have is to print the script. If I try to select and copy the script, it does not go to the clipboard.

The only way I've had any success at all is to print the script to CutePDF, but even then the script has line numbers, headers, etc. which prevent it from being too much use.

I also tried setting the Sync Script output file on the "Define Target Schema and Output" window. I was excited to see my output file until I realized that Toad only wrote the header information, but none of the actual DDL.

Has anyone else seen this behavior?

Sean

Post by John Dorlon
I see that. Also fixed for next beta.
Thanks.
Sent: Monday, December 31, 2012 9:40 AM
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1
I've noticed another one while changing sources and targets multiple times in the same schema comparison window. After a new source connection is defined the schema drop down does not refresh. It does refresh the schemas after picking the new connection again from the drop down list. Shouldn't the schema dropdown refresh when the connection is established? I'm not connecting as a schema owner if that matters.

John Dorlon

2013-04-23 19:50:29 UTC

Permalink

These features are reserved for DBA module only.

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of ss052111
Sent: Tuesday, April 23, 2013 2:30 PM
To: ***@yahoogroups.com
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1

Another Compare Schemas problem. I'm running v11.6.1.6.

I've done my compare, and I'd like to run the sync script. I see my script, but the buttons "Save", "Move Script to Editor", "Move Script to Editor and Run Now", and "Schedule Script" are all grayed out. It seems the only option I have is to print the script. If I try to select and copy the script, it does not go to the clipboard.

The only way I've had any success at all is to print the script to CutePDF, but even then the script has line numbers, headers, etc. which prevent it from being too much use.

I also tried setting the Sync Script output file on the "Define Target Schema and Output" window. I was excited to see my output file until I realized that Toad only wrote the header information, but none of the actual DDL.

Has anyone else seen this behavior?

Sean

I see that. Also fixed for next beta.
Thanks.
Sent: Monday, December 31, 2012 9:40 AM
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1
I've noticed another one while changing sources and targets multiple times in the same schema comparison window. After a new source connection is defined the schema drop down does not refresh. It does refresh the schemas after picking the new connection again from the drop down list. Shouldn't the schema dropdown refresh when the connection is established? I'm not connecting as a schema owner if that matters.

John Dorlon

2013-04-23 19:55:15 UTC

Permalink

Oh, and I forgot to mention - in Toad 12, these features will also be available to Toad Expert Edition.

From: ***@yahoogroups.com [mailto:***@yahoogroups.com] On Behalf Of John Dorlon
Sent: Tuesday, April 23, 2013 2:50 PM
To: ***@yahoogroups.com
Subject: RE: [toad] Re: Schema Comparison Nusiances 11.6.1

These features are reserved for DBA module only.

From: ***@yahoogroups.com<mailto:***@yahoogroups.com> [mailto:***@yahoogroups.com] On Behalf Of ss052111
Sent: Tuesday, April 23, 2013 2:30 PM
To: ***@yahoogroups.com<mailto:***@yahoogroups.com>
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1

Another Compare Schemas problem. I'm running v11.6.1.6.

I've done my compare, and I'd like to run the sync script. I see my script, but the buttons "Save", "Move Script to Editor", "Move Script to Editor and Run Now", and "Schedule Script" are all grayed out. It seems the only option I have is to print the script. If I try to select and copy the script, it does not go to the clipboard.

The only way I've had any success at all is to print the script to CutePDF, but even then the script has line numbers, headers, etc. which prevent it from being too much use.

I also tried setting the Sync Script output file on the "Define Target Schema and Output" window. I was excited to see my output file until I realized that Toad only wrote the header information, but none of the actual DDL.

Has anyone else seen this behavior?

Sean

ss052111

2013-04-23 20:22:27 UTC

Permalink

Well, bummer. That isn't immediately apparent when using the app. Sounds like a missed marketing opportunity.

Post by John Dorlon
These features are reserved for DBA module only.
Sent: Tuesday, April 23, 2013 2:30 PM
Subject: [toad] Re: Schema Comparison Nusiances 11.6.1
Another Compare Schemas problem. I'm running v11.6.1.6.
I've done my compare, and I'd like to run the sync script. I see my script, but the buttons "Save", "Move Script to Editor", "Move Script to Editor and Run Now", and "Schedule Script" are all grayed out. It seems the only option I have is to print the script. If I try to select and copy the script, it does not go to the clipboard.
The only way I've had any success at all is to print the script to CutePDF, but even then the script has line numbers, headers, etc. which prevent it from being too much use.
I also tried setting the Sync Script output file on the "Define Target Schema and Output" window. I was excited to see my output file until I realized that Toad only wrote the header information, but none of the actual DDL.
Has anyone else seen this behavior?
Sean