How to Create a Unique SRCSAFE.INI in Visual SourceSafe

If you maintain legacy Visual SourceSafe (VSS) environments, a unique SRCSAFE.INI lets you apply client- or workspace-specific settings without changing the shared default file. This guide shows the setup steps, the optional #INCLUDE pattern, and how to use SSDIR to point to the right database path.

Originally published on 2009-10-06; fully revised and updated.

Source reference: How To Create a Unique SRCSAFE.INI File?

What a unique SRCSAFE.INI is used for

In the original guidance, the goal is to create a dedicated SRCSAFE.INI file in a chosen location, then point SourceSafe to the intended database with an environment variable. This is useful when you need settings that differ from the default shared file.

• Keep a separate client-specific configuration.
• Optionally inherit values from the default configuration.
• Switch database context by setting SSDIR.

Default vs unique SRCSAFE.INI approaches

Step-by-step setup

1) Create a new SRCSAFE.INI file

Create a file named SRCSAFE.INI and place it in the location you want to use for this unique configuration.

2) Optionally include the default SRCSAFE.INI

If you want the unique copy to include the default configuration, add this line (as shown in the original post):

#INCLUDE <SS path>\SRCSAFE.INICode language: CSS (css)

3) Set the SSDIR environment variable

Set SSDIR to the Visual SourceSafe directory path. In cmd.exe, use:

SET SSDIR=\\MyServer\MyVSSdir
SET SSDIR

Note: keep the equals sign tight (SSDIR=value) when using SET in Command Prompt.

4) Open the database in SourceSafe

The original article notes that this can be done even with Visual SourceSafe 5.0, but may not be necessary for every case; you can also open the database from File > Open.

Configuration workflow

flowchart TD
    A[Choose location for custom SRCSAFE.INI] --> B[Create SRCSAFE.INI]
    B --> C{Use shared defaults}
    C -- Yes --> D[Add INCLUDE line]
    C -- No --> E[Keep standalone settings]
    D --> F[Set SSDIR path]
    E --> F
    F --> G[Open database in SourceSafe]
    G --> H[Verify expected behavior]

Troubleshooting quick checks

• Confirm the file name is exactly SRCSAFE.INI.
• Verify the SSDIR path points to the intended VSS database location.
• If using #INCLUDE, ensure the referenced path is reachable from the client machine.
• After changing environment variables, reopen the SourceSafe client session.

Best practices

• Document where each custom SRCSAFE.INI file is stored and who uses it.
• Use one consistent path style across the team to reduce path-resolution issues.
• Prefer minimal overrides when using #INCLUDE, so shared defaults remain authoritative.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.