Microsoft KB Archive/199204

= How To Put Stored Procedures Under Remote Source Control in Visual InterDev 6.0 =

Article ID: 199204

Article Last Modified on 7/2/2004

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q199204



SUMMARY
This article describes how to put SQL Server stored procedures under Visual InterDev 6.0 source control when Microsoft Visual SourceSafe is not on the SQL Server computer.



MORE INFORMATION
There are two distinct configurations for placing stored procedures under source control:  The Visual SourceSafe database is installed on the same computer as SQL Server. For this configuration, see the following article in the Microsoft Knowledge Base:

201240 How To Put Stored Procedures Under Source Control in Visual InterDev

 Visual SourceSafe is installed on a computer remote from SQL Server, as shown in the following procedure.

Stored Procedures Under Source Control with Visual SourceSafe on a Remote Computer
 Install the SourceSafe client components on the SQL Server computer. You can do this by running Netsetup.exe from the directory of the computer that has the Visual SourceSafe database installed on it. Change the MSSQLServer (SQLExecutive on SQL Server 6.5) service to run under a user account that has access to the remote computer and is a user on Visual SourceSafe. SQL Server uses this account to log on to the remote server in order to check files in and out of Visual SourceSafe. Install the Visual InterDev Server Components on the SQL Server computer. These are found on CD-ROM 2 of Visual Studio by running the Setup.exe file in the \VID_SS folder. On the client, open Visual InterDev to your project that has the database connection and follow these steps:

<ol style="list-style-type: lower-alpha;"> In Data View, open the connection to the database by clicking on the plus sign next to the database name.</li> Right-click the database name and select Add to Source Control. The Enable Source Control dialog box appears.</li> Type the local path (relative to SQL Server) to the Srcsafe.ini file located on the SQL Server computer. You can also enter a universal naming convention (UNC) path if the database is different from the one where you ran Netsetup.</li> Type the name of the source control project that you want to create and click OK. (NOTE: This should not include the "$/" because Visual InterDev will put that in for you.)</li> Enter a valid SourceSafe logon ID and password and then click OK. This user ID and password must be for a valid Visual SourceSafe user account. Ensure that the user and password have been entered in the Visual SourceSafe Administration tool for the database on the remote computer.</li></ol>

Stored procedures successfully placed under source control display a lock icon.</li></ol>

<div class="references_section">