Chat now with support
Chat with Support

SQL Navigator for Oracle 8.1 - User Guide

Quick Overview Working With SQL Navigator Navigation Oracle Logon Code Editor Visual Object Editors Team Coding and Version Control Systems Modules, Windows And Dialogs
Analyze Tool Auto Describe Tool Benchmark Factory Bookmarks Dialog Capture Web Output Change Logon Password Dialog Code Analysis Code Assistant Code Road Map Code Templates Code Test Database Source Code Search Dialog DB Navigator Describe Difference Viewer Edit Data ER Diagram Explain Plan Tool Export Table Find and Replace Dialog Find objects Dialog Find Recycle Bin Objects Dialog Formatting Options HTML Viewer Import HTML as PL/SQL Import Table Java Manager Job Scheduler Locate In Tree Output Window PL/SQL Profiler Profile Manager Project Manager Publish Java to PL/SQL Quick Browse Rename Object Search Knowledge Xpert Select DB Object Dialog Server Output Server Side Installation Wizard Session Browser Source Preview SQL Modeler SQL Optimizer Task Manager Web Support Configuration Dialog Wrap Code
View | Preferences About Us

Configure Serena PVCS Version Manager

These configuration settings are specific to Serena PVCS Version Manager.

  1. From the Main Menu, click Team Coding | Configure.

  1. Select Serena PVCS Version Manager | Settings
Setting Description
PVCS Client Enter or browse to the PVCS client executable.
Automatically Login to Default Repository Log in to the PVCS repository when Team Coding starts.
Default Comment Set the default comment when code is checked in to PVCS. User-supplied comments override this default.

 

Configure Subversion

These configuration settings are specific to Subversion (SVN).

  1. From the Main Menu, click Team Coding | Configure.

  1. Select Subversion (SVN) | Settings

 

Client Tab

Setting Description

SVN Executable

Specify the Subversion executable file.

Global Options

Send Subversion global options across all Subversion commands. For more information, see the help information provided with the SVN client.

Note: The username and password global options are automatically included when necessary with server-based connections.

 

Server Defaults Tab

Setting Description

Default Connection Method

Set default values to connect to your SVN Repository. SQL Navigator uses these values to create the URL to the repository.

  • Select Local Connection if the server is installed on the same machine as the client.
  • Select WebDAV Connection if the server is to be accessed across the HTTP protocol.
  • Select SVN Server Connection if the server is on a remote machine and is to be accessed through the svn protocol.

 

OptionsTab

Setting Description

Use locking on check out / check in

Use locking when checking out files and to clear locks when checking in files.

Note: By default, Subversion does not use locks when working with files. This option allows you to override this default behavior

 

Configure Team Foundation Server

Note: Please see your Microsoft Azure DevOps Server (TFS) administrator before configuring any of these options.

These configuration settings are specific to Microsoft Team Foundation Server.

  1. From the Main Menu, click Team Coding | Configure.

  1. Select Microsoft Azure DevOps Server (TFS)| Settings

 

General Tab

Setting Description
Server Location Specify the name of the server where the Microsoft Azure DevOps Server (TFS) repository is installed and specify the Microsoft Azure DevOps Server (TFS) port number on that server. Optionally, you can specify that connections are SSL.
Client Specify whether to connect through the internal or external client. Each option has advantages and disadvantages. For more information, see More about Team Foundation Server and SQL Navigator.
Connection Connect automatically to the default Microsoft Azure DevOps Server (TFS) workspace when SQL Navigator starts.

 

Check In / Out Tab

Setting Description

Disable prompts when possible

Enable this option to suppress Microsoft Azure DevOps Server (TFS) prompts whenever possible during a check-in or check-out process.

Note: If check-in notes are required in the server configuration, SQL Navigator prompts you to enter these notes during a check-in process, regardless of this setting.

Validate before checking in Validate the code before it is checked in.

Default locking

Select a locking option:

  • Lock the code on check-in or check-out
  • Automatically determine the locking based on server settings
  • Require no locking.
Associate Work items with Change

Set Link one or more Microsoft Azure DevOps Server (TFS) work items to the check-in change set.

 

History Tab

Setting Description
Only show my changes Show only the code changes made in this SQL Navigator client when displaying history.
Stop after Stop maintaining revision history after the specified number of check-ins.

 

Advanced Tab

Setting Description

Default URL

Custom URL

Enter an alternate URL if your Team Project Collection has a non-standard URL that cannot be correctly built using SQL Navigator’s configuration settings.

When this value is set, SQL Navigator ignores all the other settings (Server, Port, Collection, Virtual Dir, etc.) and uses the Alternate URL to build Microsoft Azure DevOps Server (TFS) calls to the Team Project Collection on the server.

Note: It is recommended that this is only used in the very small number of cases where the URL to the Team Project Collection is not configurable from the normal SQL Navigator settings.

Collection

Specify the Microsoft Azure DevOps Server (TFS) Collection to connect to , if using Microsoft Azure DevOps Server (TFS) 2010 or later.

Virtual directory

Specify the path to the virtual directory, if using Microsoft Azure DevOps Server (TFS) 2010 or later.

Alternative URL

Specify an alternate URL for use if the primary URL is not available.

 

Microsoft Azure DevOps Services/ Visual Studio Team Services

Team Coding supports Azure DevOps Services (VSTS) online using Team Foundation Version Control.

Work item tracking is supported and will be visible when team members add or check in files.

Note: This provider supports only projects configured to use the Team Foundation Version Control backend. For hosted projects using the Git backend, please use SQL Navigator's Git provider.

To prepare your Azure DevOps Services account

  1. Make certain your team has an account with Microsoft. To find more information on creating an account, visit the Microsoft website: https://www.visualstudio.com/en-us/products/visual-studio-team-services-vs.aspx.

  1. You can use either a user name and password or a Personal Access Token to log in to Azure DevOps Services from Team Coding.

    • To use basic authentication, enter your username and password into Team Coding's login window when connecting.

    • To use a Personal Access Token, enter it into Team Coding's login window when connecting.

For more information about generating tokens, see https://docs.microsoft.com/en-us/vsts/integrate/get-started/authentication/pats.

To configure Team Coding for Azure DevOps Services

  1. Log in to the Team Coding database through SQL Navigator as a Team Coding Administrator.

  2. To enable support in SQL Navigator, a Team Coding Administrator must select Microsoft Azure DevOps Services (VSTS) from the VCS Provider drop-down menu in the Team Coding configuration window and then specify:

    • The Visual Studio account name

    • Whether or not SQL Navigator should automatically log in to the default repository

See Configure Team Coding Settings for more information.

Once the account name is specified, the repository appears in the login window. Enter your Visual Studio user name and password, then select a local working folder for the VCS files.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating