RE: RE: Scripting for change with Team Coding

Hi Norman,

Thanks for this information.  I do not have the DBA option, so will look into getting this.  It would appear this would make things much easier.  I may be able to get DBA access to QA for the compare only rights so will check into that.  We use subversion for our source control here with our non-database code projects.  When I setup Team Coding recently, I integrated it with Subversion so the objects are checked into subversion and I can do comparisons there.  It seems to be a big task at the end of a development cycle to verify any script for changes before promoting to QA.  I am sure if I figure out a best way and get in the groove, it will not be so bad.
Thanks for your help.

Best Regards

Timothy Bryan
We are what we repeatedly do.  Excellence, therefore, is not an act but a habit.
Aristotle

From: [email protected] [mailto:[email protected]] On Behalf Of Norman Dunbar
Sent: Monday, January 09, 2012 10:25 AM
To: [email protected]
Subject: Re: [toad] RE: Scripting for change with Team Coding



Hi Timothy,

> When you say "DBA Option", what are you referring to?
Help->About. That lists all the add-ons that your license for Toad
covers. The DBA option has the ability in it to create a script from the
output of Schama Compare. Without the DBA option all you can do is look
at the differences and try to manually resolve them.

Mine says "Add-ons: DB Admin Module, SQL Optimizer".

> We do not have the ability to run anything against QA or Production,
only dev.
That makes sense to be honest. But it will make running the schema
compare difficult if you are not able to access production. :-(

> It is our
> responsibility to manage the change in Dev and then schedule a
> deployment along with an appropriate script to execute in QA or
> Production via the DBA team. What I need to be able to do is find all
> changes within the Dev database since a given version / revision in the
> repository and create a script to give the DBA's for execution to QA and
> later to Production.
I understand. You mentioned that you use Subversion as well as team
Coding (or are you using Subversion as your Legacy team Coding system?).

I would think about looking at your Subversion logs to see what changed
"recently" and maybe, the "svn diff" command will enable you to do some
scripting work?

It's a bit difficult to find out exactly what has changed between fixes
if you don't have a schema still at the base level to compare it with.

--
Cheers,
Norm. [TeamT]


----------------------------------------------------------------------
Waste Management recycles enough paper every year to save 41 million trees. Please recycle any printed emails.