How To Put Stored Procedures Under Source Control in Visual InterDev

MORE INFORMATION

There are two distinct configurations for placing stored procedures under source control.

• VSS database is installed on the same computer as SQL Server.
• VSS is installed on a remote computer from SQL Server.
  
  For additional information about using a remote VSS database, click the article number below to view the article in the Microsoft Knowledge Base:

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

Installing Visual SourceSafe onto the SQL Server Computer

Install Visual SourceSafe on the SQL Server computer. Visual SourceSafe is located on disk 2 of Visual Studio. Run the Setup.exe file that is located in the \VSS_SS directory.

Change the MSSQLServer (or SQLExecutive on SQL Server 6.5) service to run under a user account that has access to the Visual SourceSafe directory and is also a user in Visual SourceSafe. Make sure that the user and password have been entered in the Visual SourceSafe Administration tool for the Visual SourceSafe database on SQL Server. SQL Server uses this account to check files in and out of Visual SourceSafe.

Install the Visual InterDev Server Components on the SQL Server computer. You can find the Visual InterDev Server Components on disk 2 of Visual Studio. Run the Setup.exe file that is located in the \VID_SS directory. On the client, open Visual InterDev to the project that has the database connection and follow these steps:

1. In Data View, click the plus sign (+) to expand the database name to open the connection to the database.
2. Right-click the database name, and then click Add to Source Control.
3. In the Enable Source Control dialog box, type the local path (relative to SQL Server) to the Srcsafe.ini file that is located on the SQL Server computer.
4. Type the name of the source control project that you want to create, and then click OK.
5. Type a valid Visual SourceSafe user ID and password, and then click OK. This user ID and password must be a valid Visual SourceSafe user account. Make sure that the user and password have been entered in the Visual SourceSafe Administration tool for the Visual SourceSafe database on SQL Server.

Stored procedures that are successfully placed under source control display a lock icon.