Your Recommendation - Refreshing Database When Using Toad v12.1 Team Coding with MS Team Foundation Server

Toad for Oracle & DevOps Toolkit
1

Hi,

We have a question for a Toad Team Coding expert. What is your recommendation for managing the Team Coding / TFS functionality when “refreshing” the Oracle database that Team Coding is controlling?

We have come up with two possible options, but would like your recommendation.

Scenario: We are using Team Coding / TFS to control database source code objects in the development database. The application is highly configurable so a large number of the database objects define the configuration of the application and are controlled by Team Coding / TFS. We “refresh” the development database from production periodically to have an up-to-date version of the data. We expect the “refresh” will overwrite the objects under Team Coding / TFS control.

How will this impact the Team Coding functionality? Which of the following two options should we use to keep the Team Coding / TFS functionality working correctly?

Option 1: Disable Team Coding and Version Control. Refresh the database from Prod. Enable Team Coding and Version Control (TFS) again. Synchronize all objects controlled by Team Coding within the database with the VCS.

Option 2: Do nothing. Refresh the database from Prod. Team Coding and Version Control (TFS) will continue to work fine.

We look forward to your reply!

Kind regards,

Cindy

Senior Project Manager

Canada WCBU FDC Consolidation Project

Phone: 403-532-5326

2

Hello Cindy,

I don’t not think there is a right or wrong answer here, but my preference would be to Synchronize the objects in Team Coding as a best practice. From the two options you describe here are my thoughts:

Option 1 - Synchronize All Objects

This will do an update to the VCS Version o from the Database only with objects that have changed in the Database. The Option to ‘Compare and Sync. VCS with DB’ will produce an list of all the modified objects and then perform the synch. The advantage here is you get a listing of descrepancies from the Database to the VCS. Alternatively you can just performs ‘Create new revision in VCS’. Depending on the options you select, this will create or force a new revision for all objects. The nice thing about this approach is that you have a history record in the VCS corresponding with all database objects for the ‘Refresh’ milestone.

Option 2 – Do nothing.

While Team Coding will continue to function, in all probability you have objects in the Database that are not in sync with the VCS. As the users check objects out from Team Coding, they will get a dialog asking them to select the version of the object to check out, database or VCS. This may be irritating. A second potential issue is that the user may select to check out the VCS version instead of the database version, which from my understanding of your scenario is not what you want.

I hope this is helpful

Stephen

3

Hi Stephen,

Thank you for an excellent answer! We will adopt option 1, which is your preference.

Your team is great to deal with and exceptionally responsive.

Have a great weekend!

Cindy

From: Stephen Beausang [mailto:bounce-StephenBeausang_734@toadworld.com]
Sent: Friday, October 18, 2013 6:33 AM
To: toadoracle@toadworld.com
Subject: [EXTERNAL]RE: [Toad for Oracle - Discussion Forum] Your Recommendation - Refreshing Database When Using Toad v12.1 Team Coding with MS Team Foundation Server

RE: Your Recommendation - Refreshing Database When Using Toad v12.1 Team Coding with MS Team Foundation Server

Reply by Stephen Beausang

Hello Cindy,

I don’t not think there is a right or wrong answer here, but my preference would be to Synchronize the objects in Team Coding as a best practice. From the two options you describe here are my thoughts:

Option 1 - Synchronize All Objects

This will do an update to the VCS Version o from the Database only with objects that have changed in the Database. The Option to ‘Compare and Sync. VCS with DB’ will produce an list of all the modified objects and then perform the synch. The advantage here is you get a listing of descrepancies from the Database to the VCS. Alternatively you can just performs ‘Create new revision in VCS’. Depending on the options you select, this will create or force a new revision for all objects. The nice thing about this approach is that you have a history record in the VCS corresponding with all database objects for the ‘Refresh’ milestone.

Option 2 – Do nothing.

While Team Coding will continue to function, in all probability you have objects in the Database that are not in sync with the VCS. As the users check objects out from Team Coding, they will get a dialog asking them to select the version of the object to check out, database or VCS. This may be irritating. A second potential issue is that the user may select to check out the VCS version instead of the database version, which from my understanding of your scenario is not what you want.

I hope this is helpful

Stephen

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.