Team Coding controls the following database object types:
Use the Team Coding Administration page to install, set up, and manage the Team Coding environment. On this page a Team Coding Administrator can:
Only a Team Coding Administrator can administer the Team Coding environment. The Team Coding Administrator must have the role of TC_ADMIN_ROLE or an equivalent. For more information, see Team Coding Roles.
To open Team Coding Administration
Enable or disable Team Coding on this database. This icon works as a toggle to enable or disable Team Coding in the connected database. Team Coding must be installed on the database before you can enable it. For more information, see Install Team Coding.
Install or uninstall Team Coding. Team Coding is installed when the Team Coding database objects are installed in the database. For more information, see Install Team Coding.
Administer Team Projects. Additional icons on the toolbar are active only when the Team Projects Tab is active and at least one non-default project exists. See: Team Projects.
Set up a version-control system for use with Team Coding and set global rules for the Team Coding workflow. For more information, see Team Coding Settings.
Create and administer Team Projects. At least one Team Project must exist to define which objects are controlled through Team Coding. For more information, see Team Projects.
A Team Coding Administrator must prepare the database and configure Team Coding before users can begin using it. This process includes:
To install Team Coding
|Team Coding Installation
Into Current Schema
Install the Team Coding database objects into the connected schema. If you select the connected schema, it must be publicly accessible and have DBA privileges.
Into Toad Schema
Many DBAs select the TOAD schema to keep their Toad objects organized in one place, but otherwise there is no difference between selecting the TOAD schema or another schema. If the schema does not exist, you are prompted to create it.
Select or enter the administrator role for Team Coding. It is strongly recommended that you accept the default, TC_ADMIN_ROLE. See Team Coding Roles.
Tablespaces in which to create objects
Select a tablespace for the Team Coding objects. The default is the default tablespace of the installation schema that you selected.
Migrate Team Coding Settings
(Upgrades) If Team Coding was installed previously, you are prompted to migrate the previous Team Coding settings. Select this option to migrate the previous settings.
Clicking Finish runs the script that installs Team Coding.When prompted, log in to the database to execute the creation script and complete the installation of Team Coding.
Click in the toolbar of the Administration dialog to enable Team Coding in the database.
Note: This icon works as a toggle. When it is shown as depressed, Team Coding is active. At any time, a Team Coding Administrator can click this icon to disable Team Coding but leave the Team Coding database objects installed. When Team Coding is disabled, users will not be able to view anything in the VCS Browser or Team Projects Browser in the Team Coding Manager. You can enable and disable Team Coding as often as needed.
To configure Team Coding
The Team Coding Administration dialog is displayed after the script that installs Team Coding executes. If this dialog is not displayed, select Team Coding | Administer.
You can use this dialog at any time in the future to change Team Coding settings.
The Team Coding global settings control the Team Coding environment at the database level. These settings apply to all Team Coding users.
To work with these settings go to Team Coding | Administer, then select the Settings tab.
(Optional) Select a VCS to use for Team Coding. Then, click to set VCS settings.
Force check-in comment
Require users to enter a comment when checking in an object.
Force check-out comment
Require users to enter a comment when checking out an object.
Force new revision on check-in
Force the VCS to create a new revision record when checking in an object, even if the object source is unchanged. Note: Some version-control systems do not support this feature and will not create a new revision for unchanged objects.
Remove source from VCS when deleting an object
When an object that is controlled by a Team Project is deleted in SQL Navigator, delete the object from the VCS.
Select Prompt before removing to prompt users before removing the object.
When differences in source versions exist...
When you open an object or script, Team Coding compares it with the latest revision in the version control system (VCS) repository (unless it is checked out, in which case SQL Navigator opens a read-only version of the file). If the database object or script differs from the version saved in the VCS, SQL Navigator notifies you. Differences in objects could be due to a number of factors. For example, another tool or a script may have been used to edit the object, or the archive in the VCS may have been updated by some means other than Team Coding.
You can choose one of the following options to resolve the difference:
Open Database Version: Always load the database version in read-only mode.
Open VCS Version: Always update the database with the version from the VCS repository and load it in read-only mode. Caution: Opening the version from the repository will cause the object in the database to be updated.
Prompt User: Prompt the user to choose between opening the database version or the VCS version.
© ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center