Find Interview Questions for Top Companies
Ques:- VSS performance is extremely slow.
Asked In :-
Right Answer:
To improve VSS performance, consider the following steps:

1. Optimize the database by compacting it regularly.
2. Ensure that the network connection is stable and has sufficient bandwidth.
3. Limit the number of users accessing VSS simultaneously.
4. Archive old projects to reduce the database size.
5. Check for and resolve any hardware issues, such as slow disk drives.
6. Update to the latest version of VSS for performance improvements and bug fixes.
Ques:- How does CVS differ from RCS?
Asked In :- Method CRM,
Right Answer:
CVS (Concurrent Versions System) differs from RCS (Revision Control System) primarily in that CVS supports multiple developers working on the same project simultaneously, allowing for concurrent versioning, while RCS is designed for single-user version control, managing files one at a time. Additionally, CVS manages entire directories and supports branching and merging, whereas RCS focuses on individual files.
Ques:- What is CVS useful for?
Asked In :-
Right Answer:
CVS (Concurrent Versions System) is useful for version control, allowing multiple developers to work on the same project simultaneously, track changes, manage different versions of files, and collaborate effectively.
Ques:- Does VSS OLE Automation support administrative functions?
Asked In :-
Right Answer:
No, VSS OLE Automation does not support administrative functions.
Ques:- How can I backup a database?
Asked In :-
Right Answer:
To backup a database, you can use the database management system's built-in backup command or tool. For example, in MySQL, you can use the command `mysqldump -u username -p database_name > backup_file.sql`. In SQL Server, you can use the command `BACKUP DATABASE database_name TO DISK = 'backup_file.bak'`. Always ensure you have the necessary permissions and storage space for the backup.
Ques:- Are there any patches available for problems that occur when using VSS on a Novell share?
Asked In :-
Right Answer:
Yes, there are patches available for issues that occur when using Visual SourceSafe (VSS) on a Novell share. You should check the Microsoft support website for the latest updates and patches specific to your version of VSS.
Ques:- Is there a way to automatically increment/synchronize my project build number and my VSS label/version?
Asked In :-
Right Answer:
Yes, you can automate the incrementing of your project build number and synchronize it with your VSS label/version by using a build script or a continuous integration tool. You can configure the script to update the build number in your project files and apply the corresponding VSS label/version during the build process.
Ques:- Is there an API for VSS? Where can I get it?
Asked In :-
Right Answer:
Yes, there is an API for Visual SourceSafe (VSS). You can find it in the Visual SourceSafe SDK, which is included with the VSS installation.
Ques:- How can I automate database maintenance routines?
Asked In :-
Right Answer:
You can automate database maintenance routines by using scheduled jobs or scripts. For example, you can create SQL scripts for tasks like backups, index rebuilding, and statistics updates, and then schedule them using tools like cron jobs (for Linux) or Task Scheduler (for Windows). Additionally, many database management systems have built-in features for automation, such as SQL Server Agent for SQL Server or DBMS_SCHEDULER for Oracle.
Ques:- Microsoft VSS Best Practices
Asked In :-
Right Answer:
1. Use a consistent naming convention for projects and files.
2. Regularly back up the VSS database.
3. Limit access to the VSS database to authorized users only.
4. Use labels to mark stable versions of projects.
5. Avoid storing large binary files in VSS.
6. Regularly check in and check out files to maintain version history.
7. Document changes and maintain a change log.
8. Use branching and merging judiciously to manage parallel development.
9. Monitor and manage the size of the VSS database to prevent performance issues.
10. Train team members on VSS usage and best practices.
Ques:- How do I display a custom message box during Add Item, Check In, Ckeck Out, Undo Checkout, Branch, and Rename?
Asked In :-
Right Answer:
To display a custom message box during Add Item, Check In, Check Out, Undo Checkout, Branch, and Rename, you can implement event handlers for these specific actions in your version control system or project management tool. Use the appropriate API or scripting capabilities to intercept these events and trigger a message box with your custom message. Ensure that the message box is displayed at the right point in the workflow, typically before the action is finalized.
Ques:- The integration isn?t working between VSS and VB/VC. What can I do?
Asked In :-
Right Answer:
Check the following:

1. Ensure that Visual SourceSafe (VSS) is properly installed and configured.
2. Verify that the VSS database is accessible and not corrupted.
3. Confirm that the correct VSS project is selected in Visual Basic (VB) or Visual C++ (VC).
4. Check for any network issues that may be preventing connection to the VSS server.
5. Ensure that the user has the necessary permissions to access the VSS project.
6. Look for any updates or patches for both VSS and VB/VC that may resolve compatibility issues.
7. Restart both VSS and the development environment to refresh connections.
Ques:- What is CVS for? What does it do for me?
Asked In :-
Right Answer:
CVS (Concurrent Versions System) is a version control system that helps manage changes to source code over time. It allows multiple developers to work on the same project simultaneously, tracks revisions, and enables you to revert to previous versions of files if needed.
Ques:- How does CVS differ from SCCS?
Asked In :-
Right Answer:
CVS (Concurrent Versions System) differs from SCCS (Source Code Control System) primarily in that CVS supports multiple developers working on the same project concurrently, allowing for branching and merging, while SCCS is designed for single-user access and does not handle concurrent modifications well. Additionally, CVS manages entire directories of files, whereas SCCS operates on a file-by-file basis.
Ques:- Are the any windows shell extensions for SourceSafe?
Asked In :-
Right Answer:
Yes, there are Windows shell extensions for SourceSafe that allow integration with the Windows Explorer, enabling users to perform SourceSafe operations directly from the file system interface.
Ques:- What reporting packages are available for SoucreSafe?
Asked In :- Method CRM,
Right Answer:
The reporting packages available for SourceSafe include Microsoft Visual SourceSafe Reports, SourceSafe Explorer, and third-party tools like VSS Database Analyzer and VSS Report Generator.
Ques:- How can I put revision history information in the source files each time I check in a file?
Asked In :-
Right Answer:
You can include revision history information in the source files by using version control system hooks or commit messages. For example, in Git, you can use a pre-commit hook to automatically append revision details to a specific section of your source files each time you commit. Alternatively, you can manually add comments in the code with the revision number and date during each check-in.
Ques:- Where can I find a list of known bugs in VSS?
Asked In :-
Right Answer:
You can find a list of known bugs in Visual SourceSafe (VSS) on the official Microsoft support website or in the release notes/documentation for VSS.
Ques:- How do I recover from a lost administration password?
Asked In :-
Right Answer:
To recover from a lost administration password, you can reset it by following these steps:

1. **Boot into Recovery Mode**: Restart the system and access the recovery mode or safe mode.
2. **Access Command Line**: Open a command line interface or terminal.
3. **Reset Password**: Use the appropriate command to reset the password (e.g., `passwd username` for Linux or use the built-in password reset tools for Windows).
4. **Reboot**: Restart the system and log in with the new password.

If applicable, consult the specific documentation for your operating system for detailed steps.


Release Management is a critical discipline within the fields of software development and IT operations. It is the systematic process of managing, planning, scheduling, and controlling the build, test, and deployment of software releases. The core purpose of this function is to ensure that all changes to a live software environment are delivered in a controlled, predictable manner that minimizes disruption to services and reduces the risk of failure. It acts as the bridge between development and operations teams, ensuring that a new version of software is not only ready but also deployed effectively.

The responsibilities of a Release Manager are comprehensive and span several key phases:

  • Planning and Coordination: A release manager works with development, quality assurance (QA), and operations teams to define the scope of an upcoming release. This includes setting clear release schedules, defining the criteria for a successful release (go/no-go decisions), and identifying all necessary resources.
  • Build and Verification: Once the code is complete, the Release Management process oversees the creation of a deployable software package, known as a “build.” This phase involves rigorous testing to ensure the build is stable, free of critical defects, and meets all quality standards.
  • Deployment: The Release Manager is responsible for executing the deployment plan, which can range from a simple script execution to a complex, multi-environment rollout. This phase includes careful monitoring and communication to all stakeholders, ensuring transparency and managing expectations.
  • Post-Deployment Activities: After a release is deployed, the Release Manager verifies that it is functioning as expected. They are also responsible for documenting the process and, in the event of a critical failure, overseeing the rollback procedure to restore the service to a previous, stable version.

Effective Release Management offers significant benefits, including reducing the risk of deployment failures and service interruptions, improving operational efficiency by standardizing processes, and ensuring compliance with organizational policies and regulatory requirements. It is a strategic function that transforms a complex and potentially chaotic process into a predictable and reliable part of a company’s software delivery pipeline.

AmbitionBox Logo

What makes Takluu valuable for interview preparation?

1 Lakh+
Companies
6 Lakh+
Interview Questions
50K+
Job Profiles
20K+
Users