Contents
Package Explorer

Source Code Control When Working With Individual Files in the Editor

Source code control (SCC) features are available when working on package scripts as explained in the section titled With Source Code Control in Code Packages, or when working with individual files that are not related to packages. In order to work with individual files under SCC, you must first make sure that a parent folder in the local file system is mapped to another parent folder in the SCC provider. This will allow you to check in and check out files from anywhere under those parent folders.

To map a folder in the local file system to a folder in the SCC server, go to Tools → Options, and enter the folders information in the Folder Mapping dialog. Then, you should be able to use the source control buttons and features to check in all local files that are saved anywhere under your local folder. Similarly, you can now check out files from anywhere under the SCC parent folder.

Note: The SCC status of each script in the SQL editor window is presented at the bottom of each window.

For your reference, below are the icons used in Combine to indicate the source control status of each script:

   Item added to package and not yet available in source control
   Package item is checked out to me
   Package item is checked out to another user
   Package item is checked in
   Package item is missing from the source control server (after item is deleted from SCS)


The exclamation mark is added to any of the above icons when the package item is missing from the local file system, for example:

   Item added to package but then deleted from local file system
   Package item is checked in but is not found on my local file system




© 2001-2017 JNetDirect, Inc. All Rights Reserved.