Oracle PL/SQL Developer Integrated TFS for Team script file versioning

For the traditional large-scale software products using relational database, the continuous development and maintenance of the background database can produce a large number of script files, how to make versioning more convenient for these script files, and how to quickly manage the permissions between the teams. The level of integration between the different database products and the corresponding client management tools and different product version management tools may be subject to different physical examination and reception.

This article implements a version management model for database scripting by documenting TFS, PL/SQL, and the corresponding plug-in installation, configuration, and operation.

1, Environment and plugins

Implementing version management integration for PL/SQL tools and TFS requires the following plug-ins

PL/SQL Developer plugin,:

Http://www.allroundautomations.com/download/vcs124.zip

TFS MssCi Tools,:

Http://visualstudiogallery.msdn.microsoft.com/06c8e056-7f77-4a5c-9b8b-49318c143df8

Teamexplorer tool (if you have installed VS2013 and subsequent versions, ignore):

http://www.microsoft.com/en-us/download/details.aspx?id=39314

2, TFS parameter Configuration in PL/SQL

The above installation package is very simple, easy to click a few steps, after the installation of the above software, open the PL/SQL tool, you can see on the toolbar to add the VCs menu. Click VCs, Open Project appears as in the TFS Parameters Configuration dialog box.

650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171350148-1001496029. PNG "style=" border:0px; "/>

Click the Open Folder button in the Project entry box, select the TFS Server and project and specify the local working directory

650) this.width=650; "Src=" Http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171358960-25003405.png " Style= "border:0px;"/>

3, in PL/SQL, script file check in, check out, etc.

To create a new script file, the file must be placed under the local workspace directory that you set up in the previous step.

650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171411273-1132974718. PNG "style=" border:0px; "/>

Click CVS, add, check the newly added files and check in to the TFS code base.

650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171420851-2136924061. PNG "style=" border:0px; "/>

You can see the code you just checked in in TFS Portal

650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171428398-403704153.png "Style=" border:0px; "/>

Other operations, such as checkout code, historical version comparison, etc., are not listed, these functions are out-of-the-box functionality.

4, File Rights Management instructions

Multi-person teams may involve the need for rights management, such as the need to reasonably resolve different roles of different groups of people have different permissions on the file.

I think in addition to the knowledge rights protection, data security defense, project risk avoidance and other starting points, as far as possible not to waste team members of the rights management this thing.

Rights management, combined with the region, folder, file itself, account, and permission terms in TFS, can satisfy an absolute majority of permission scenarios, applying permissions to the least granular management object. is a file permission configuration interface.

650) this.width=650; "Src=" http://images2015.cnblogs.com/blog/28076/201702/28076-20170221171443741-2098009648. PNG "style=" border:0px; "/>

Oracle PL/SQL Developer Integrated TFS for Team script file versioning