Work with existing Shared Script
Learn how to work with existing shared scripts in SQL Manager 2011 for DB2
When using TFS:
1. After you create a shared script you need save changes made to it and 
add it to version control. Users connected to the same repository now can see this script and work with it.
2. If you need to edit a shared script you need to 
check it out. This locks file for other users till you finish working with it.
3. When you finished working with a script file and want changes to be added to the repository use the 
Check In operation. This operation adds changes made locally to the repository copy of this script and unlocks the file for other users.
4. To access the up-to-date list of scripts and their state use the 
Get Latest Version option. Applied to a single file it gets the copy of this file from the repository and replaces the local copy with it, or merges these two copies (depends on TFS settings). When applied to shared script folder/branche it gets the list of files and replaces or merges local copies with ones from VCS repository.
5. To delete script use the 
Drop Script option. If the script is added to version control you need to use check in for shared script DB Explorer branch to remove the script copy from the VCS repository too.
When using CVS:
1. After you create a shared script you need save changes made to it and add it to version control. Users connected to the same repository now can see this script and work with it.
2. To get latest changes of a script use the 
Update from Version Control option. Applied to script folder/branch it will display new script files added by other users (if any) and the deleted ones. Use this option before changing script to avoid conflicts.
3. If you need to save to VCS repository local changes you made to shared script use the 
Commit to Version Control option.
4. To delete script use the Drop Script option. If the script is added to version control you need to use the commit to version control option for shared script DB Explorer branch to remove the script copy from the VCS repository too.
When using VSS:
1. After you create a shared script you need save changes made to it and add it to version control. Users connected to the same repository now can see this script and work with it.
2. If you need to edit a shared script you need to check it out. This locks file for other users till you finish working with it.
3. When you finished working with a script file and want changes to be added to the repository use the Check In operation. This operation adds changes made locally to the repository copy of this script and unlocks the file for other users.
4. To access the up-to-date list of scripts and their state use the Get Latest Version option. Applied to a single file it gets the copy of this file from the repository and replaces the local copy with it. When applied to shared script folder/branche it gets the list of files and replaces or merges local copies with ones from VCS repository.
5. To delete script use the Drop Script option. If the script is added to version control you need to use check in for shared script DB Explorer branch to remove the script copy from the VCS repository too.
Note: All the operations under scripts are available in the DB Explorer context menu and in the SQL Script Editor navigation bar.