RE: Controlling changes to database - Team Coding

In the Code Collections dialog there are two options that can help with this..

If the database revision is correct - you can use 'Create new revision' which creates a new revision in SVN of all database objects

'Compile latest revision' compiles all objects from the source in SVN.


Stephen

From: [email protected] [mailto:[email protected]] On Behalf Of Bryan, Timothy
Sent: Wednesday, January 11, 2012 12:59 PM
To: [email protected]
Subject: RE: [toad] Controlling changes to database - Team Coding


If my svn repository is no longer in synch with the database objects, what is the best way to correct this?  I have Code Collection Groups setup in TC.

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 Stephen Beausang
Sent: Wednesday, January 11, 2012 11:37 AM
To: [email protected]
Subject: RE: [toad] Controlling changes to database - Team Coding


Timothy,

I'd like to chime in here if I may. 'Not cut and dry ..' is apt .  First Please see my comments below to your original post .

Some General Stuff :

Toad makes a distinction between Team Coding and File Based Source Control.  See the help under  Use Source Control - About Source Control, which gives a very useful breakdown of the options and advantages / disadvantages of each system. It also helps to outline how each works .

File based source control does not require any server side objects, and simply interfaces with the VCS Provider to manages source files.

Team Coding manages objects centrally in Toad and requires that you install the Team Coding Server Side Objects for each database that you wish to control. In addition Team Coding performs a 'lock' on controlled objects in the database.  In reality it is keeping a local copy of  the source for each object and using SVN (in your case) to manage version history and locking source locking centrally. There is also Server Side Table, usually in the Toad Schema ,which manages  the locking of objects.  The source is controlled in the SVN repository, and each user checks out a local copy of the source when he checks out the object (e.g in the Schema Browser).  When the user has an object 'checked out' Toad automatically opens the local copy of the object for editing.

In your case I would also read up on the help for Mirroring in Team Coding. This enables each user to create Sandbox in his own schema without effecting the production object. Toad manages locking  etc.  I'm not sure if this is appropriate for you dev environment or not.

I hope this helps
Stephen

________________________________

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