지금 지원 담당자와 채팅
지원 담당자와 채팅

SQL Navigator for Oracle 8.0 - 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

More about Git and SQL Navigator

A git client for Windows must be installed. Git 1.8.3 mysygit.0 was tested.

Additional documentation is provided at https://support.quest.com/ and on ToadWorld.com.

When you are working with Git:

  • SQL Navigator checks files in and out of the local repository residing on the client desktop.
  • Changes are posted back to the local repository immediately.
  • Updates to any centralized repository are handled outside of SQL Navigator.

 

Related Topics

Version Control Systems

More about Rational ClearCase and SQL Navigator

Note: Limitations

  • Tested on IBM Rational ClearCase Version 7.1 for Windows.
  • Tested using Dynamic Views mounted on the default ClearCase MVFS mapped drive (M:\)
  • SQL Navigator requires that all configuration is managed by ClearCase tools. ClearCase is a complex environment, which typically requires a ClearCase System Administrator.
  • Quest Software provides no support for ClearCase administration questions.

 

More about Perforce and SQL Navigator

Additional documentation is provided at https://support.quest.com/ and on ToadWorld.com.

Note: You can switch off the option to load workspaces from the Perforce Server.

By only loading workspace details for the currently active workspace, the workspace load also has been significantly optimized,.

There is a configuration option to enable/disable "Automatically Load P4 Workspaces from P4 Server."

If Automatic load option is not checked, logging on to Perforce will only load workspaces that have been saved to the client ini file during a previous session.

There is al manual 'Reload from Perforce' option, to load all workspaces from the Perforce server.

You can enter all workspace information manually, or load the information from the Perforce server.

 

Version Control Systems

More about Team Foundation Server and SQL Navigator

In order to use SQL Navigator’s Team Foundation Server support, you need to have Team Foundation Server (TFS) installed on your network. Please review Microsoft's documentation for instructions on installing and configuring TFS.

Additional requirements are needed to work with TFS work items.

Team Coding includes two methods for interfacing directly with TFS: an internal client and an external client. Although they have identical TFS functionality in SQL Navigator, each client has its own unique advantages and disadvantages. See your TFS administrator before configuring it in SQL Navigator.

Internal TFS Client

Uses Microsoft’s Web Services API to directly communicate with Team Foundation Server.

Advantages:

Improved speed (over the external client)

No need to install additional software on the client machine

Disadvantages:

Does not include support for Check-in Policy items

Certain administrative tasks, like deleting workspaces are not supported

External TFS Client

Uses Microsoft’s command-line Team Foundation client to communicate with Team Foundation Server. This command-line client is included with Microsoft Team Explorer, and should remain consistent throughout versions.

Advantages:

Expected compatibility with future versions of Team Foundation Server

Supports all features of Team Foundation Server, including Check-in Policies

Disadvantages:

Much slower than the internal client since an instance of the external client is launched for each TFS command issued to the server

Requires the installation of Microsoft Team Explorer

 

TFS Work Items

Team Coding check-in includes the ability to link one or more TFS work items to the check-in change set.

The following system requirements must be met:

  • You have the necessary Microsoft Client Access License (CAL) to update work items in Team Foundation Server.
  • .Net framework 4.0 installed.
  • Team Explorer or Microsoft Visual Studio 10.0 or 11.0 (VS 2010 or VS1012)
  • SQL Navigator installs a required DLL (TFSWorkItemLink32.dll or TFSWorkItemLink64.dll depending on the version) in the SQL Navigator program directory
  • SQL Navigator registers the DLL with the required .Net assembly (.Net Regasm.exe).

To set up Work Items

  1. Go to View | Options | Source Control.
  2. With TFS selected as your provider, click Settings.
  3. On the Check in / out tab, select Associate Work items with Change Set.
  4. Click OK in the confirmation.

To Use Work Items

  1. Check out a Team Coding controlled object.
  2. Make a change and check it back in.
  3. Open the Work Items tab in the check-in dialog and enter or select one or more work items.
  4. Click OK to check in the item.

This change set will now be linked to the selected work items.

 

Version Control Systems

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택