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

Concurrent Version Systems (CVS) Requirements

To use Concurrent Version Systems (CVS) with Team Coding, you need to have a CVS command-line client installed on your system. The following minimum versions are recommended:

  • CVS client version 1.11.9 or later
  • CVSNT client version 2.08 or later

Team Coding has been tested with the following clients:

  • CVS clients 1.11.9 and 1.11.17 with the pserver authentication
  • CVS client 1.11.12 with pserver and ssh authentication
  • CVSNT clients 2.0.8 and 2.0.41a with the pserver authentication
  • CVSNT clients 2.0.11, 2.0.26, 2.0.34, and 2.0.41 with sserver, pserver, and sspi authentications
  • CVSNT client 2.0.14 with sserver, pserver, sspi, ssh, ext, and local authentications

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

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating