Windows NT 4.0 Workstation or Server (SP6+), Windows 2000 Professional or Server (SP1)
These utilities require trusted security so are not intended for use with Windows 95/98 operating systems.
Microsoft SQL Server 7.0 (SP2) or 2000
The dmo scripting code does not seem to function properly on a SQL Server 7.0 database once the SQL Server 2000 client utilities are installed on the server. While the code supports both 7 and 2000 instances, this scripting limitation says that on a per machine basis, the tool set works with 7.0 when installed as a single instance, or with 2000 where ever installed. On servers with an instance of SQL 7 and one or more instances of SQL 2000 all scripting request must originate from a SQL 2000 engine and the SQL 7 instance must be a valid project node in the SQL 2000 dbChangeControl database.
Microsoft Visual SourceSafe 6.0
SourceSafe Configuration recommendations:
Users/Change Password/Add a good alpha-numeric password for Admin.
- Tools/Options/Project Security/enabled
- Tools/Options/Project Security/Read as only default right
- Tools/Options/General/Use network name for automatic user log enabled
- Users/Add User/Add network login account names. Include all developers, testers, and DBAs. Provide only the user name, not the domain name.
- Leave all user passwords blank. (The risk here is really that someone could execute a command line module and be able to <Hit Enter> past the password prompt if a valid SourceSafe username were provided. In reality, if a non-authorized user acquires the ability to execute any command, the system is already seriously compromised.)
Share SourceSafe on the network to the appropriate users. SourceSafe Creates a "SourceSafeUsers" local group within the Windows 2000 Domain. Consider granting shared folder access to members of that group and give the SourceSafe Administrator the ability to add existing and visible accounts or global groups to that account.
Install Microsoft SQL Server 7 or 2000 on a Windows NT or 2000 PC on all servers or workstations that will enroll in dbChangeControl
Install Visual SourceSafe 6.0 on the network. Verify that each SQL Server, using the login account assigned to the Environment Administrator or Developer that owns the dbChangeControl node, can 'see' the SourceSafe network Share. Do this by browsing to the share using Explorer or by using xp_cmdshell to execute a 'dir' of the share. It may be necessary to do this last test from the SQL Agent Job Scheduler in order to use the account as the Environment Administrator. Nothing will work if the SQL Servers cannot talk to SourceSafe.
Use SourceSafes NETSETUP to install the SourceSafe client where needed. A SourceSafe client is only required where the SourceSafe GUI is required. In general, only the developer workstations will require a SourceSafe client.
Each node must have a copy of the dbChangeControl meta-database. Refer to the configuration document for node set-up procedures.
In the examples below the dbChangeControl was installed on a Windows 2000 server (SP1) network name \\BILLSRV with the source safe database installed on the same machine and shared on the network as \\BILLSRV\MySourceSafe. The local working folders were placed at C:\VSS\.
Also note that the scripts listed below are linked to script files that will create the referenced object.
Add new Job Category
exec msdb.dbo.sp_add_category 'Job', 'Local', 'Change Control'
Create the control database
create database Admin
Build the control schema by executing the script dbChangeControlSchema.sql
Create procedures from script files:
Return to the dbChangeControl index page.