Neglected SourceSafe setup

Tech-Archive recommends: Speed Up your PC by fixing your registry

Let me preface by saying I'm a novice when I comes to source safe.

I've just inherited a severely neglected, but extremely important setup. It
was running on XP pro on an old PC. The server had Vss 6.0. I migrated it to
a new server (real server!) last night. It is now running Vss 2005. The
original installation (not the one on XP) was probably sometime in 2000.
Judging by the date on analyze.log, no maintenance has been run since
9/1/03. I know enough to know that that is not good. There are 2 projects.
One is big, and one is pretty small. I let it run an analysis after the data
was moved. one took 7 minutes, one took 5 hours. Lots of errors found. Log
files were 40 kb and 12 mb respectively.

Is there anything special I need to do given the neglect, or just let it run
the analysis and repair that it prompts me too? The users aren't complaining
anything, but I know this maintenance needs to be done. Will users have to
be off it when this repair work is done? If so, can someone give me some
points to justify this to management? They like their programmers working
around the clock. Given the length of the analysis, is there a rough
estimate as to how long the repair would take?

Thanks in advance for any help you can provide.

-Matthew


.

Relevant Pages

  • Re: Active Directory restore with disimilar hardware
    ... > server boots up, several services are unable to start. ... > windows does not recognize the NIC cards. ... I have done the inplace repair on new ... Restart the computer from the installation ...
    (microsoft.public.windows.server.active_directory)
  • Re: SBS 2003 crashes on console login after power failure
    ... Windows 2003 and any hotfixes and security updates not included in them. ... Exchange, other databases, etc. is a must before attempting any repair. ... install is useless if you can't log in to administer the server and domain. ... The volume shadow copy operation can be retried. ...
    (microsoft.public.windows.server.sbs)
  • Re: computer rebooted all by itself
    ... repair, things are in a bit of a 'mixed state', as you'd need to reapply all ... >>> At least in my experience, it's strange for the server to have rebooted ... >>> a SCSI driver update required a reboot, ... I now have 3 devices without drivers: ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain Controller Stops Processing All Login Requests Randomly
    ... do the repair and theoretically it should majically reboot to it's good ... application, dnsmgmt.msc, while the server was zombied and it caused an ... > But you seem pretty competent and if you have checked all of the DCDiag ... They are both holding the same exact zone. ...
    (microsoft.public.windows.server.dns)
  • Re: Cannot clear ARP cache
    ... Les Connor [SBS MVP] ... > Watch out for Windows Server 2003 SP2 as it can cause slow network> issues. ... >> Tested NIC repair on a SBS server when I had access to it yesterday>> with ... What symptom causes you to repair your nics? ...
    (microsoft.public.windows.server.sbs)