Realizing the backup and version control of database objects such as Procedure, View, Table, which is always a problem. However, in the nearest project, often encounter a few people to modify a package, not I overwritten The code of others is that someone else covers me. The most serious time, wasted me a whole night. This problem has had to solve it. Sqlnavigator has a Team Coding function. Probably read some documents ( Document organization is not very good, too scattered), preliminary use, discover quite easy to use. Not only has access control, but also save SQL scripts to VSS. 1. SQL Navigator 4.2 / 4.4 as an example, First install Server Side Objects on Instance. (Tool -> Server Side Installation Wizard). You will create a Sqlnav user in the installation. This user is admin. 2. Open SQL Navigator to enter. VIEW -> preference -> Team code. Inside the Connection, "User CONTROL Group", "User 3rd Party Version Control" Select VSS, remove "Apply Team Coding to All Objects" (this only controls behind Code Control Those DB Objects defined in Group 3. Define Code Control Group (CCG): In "CODE Control Group" under the Team Coding menu, create a group, select a VSS project (the script will be stored in this project), finally Select which Schema is controlled. OK. Log in with a normal account will pop up the VSS login box. You can pick IN, check out. (When check out, you will automatically import the script into VSS)
