How safe is your source?

[MMock]

I've been with the company where I now currently work for three months. I am the only developer. There is no source code control system. There are only backups. I do my own quick and dirty backup usually the end of the day and zip up my website and copy it to a flash drive. I could install VS's Source Safe probably, but I'd have to justify how long it will take. Does anyone know if it takes long? Just using it sometimes in my last job, like creating a new project, was problematic at times. But once set up, I liked using it and knowing my source was safe. But I guess my machine would still need to get backed up to have it be really safe (if both SS and my code were on my hard drive what good would that do in the event of a crash?). I also like being able to back out of code changes easily by getting the last version. Any opinions? And how do you back up your stored procedures - just by backup up your db? Can you put stored procs in SS so you can fall back to a previous version? If not, how else? Thanks.

[Kasracer]

You can create stored procs in database projects in Visual Studio and save to Visual Source Safe. You can also do it manually.

A version control system is essential. What happens if you want to fix a critical bug in version 1.4 of your software where the latest version is at 3.0? Good luck digging through your backups but with source control you can get the latest back then, apply the security fix and you're good to go.

While I never liked Visual Source Safe, it's better than nothing. I think Subversion is supposed to be one of the better ones though I am enjoying TFS as of late. Also, make sure whatever source control you use is backed up daily as well to another location just in case a hard drive fails (as you mentioned).

[Shaggy Hiker]

One item from personal experience that I might note: I've lost more to hardware theft than to data crashes.

That presents a special case that should be considered. My last boss was all proud of his use of an external hard drive, and thought himself safe. He didn't quite see the point that an external hard drive isn't in any way secure against theft. I currently save all my home projects, and any other significant files on a UPS-backed terrabyte RAID NAS located in a secret compartement in my house. It should be secure against everything except fire.

[Jenner]

It should be secure against everything except fire.

This is what I use: ioSafe

Be sure to check out the Las Vegas fire video.

[Shaggy Hiker]

Waaaaaay out of my price range.

[RobDog888]

VSS only takes a couple of minutes to install and once installed your VB projects can be added easily too. If you consider the time you are spending each day to make a manual zip and backup you will quickly surpass that time savings quickly.

Version control is essential at any level as the reasons already mentioned. I have been saved by rolling bac code changes many times and the comparisons between versions in VSS is a great help. Go with VSS IMO.

[mendhak]

SVN, VSS, Merant, whatever you want. As your work continues and grows in complexity over time, you will be more prone to errors and the need for previous versions of a file. While your current solution of backups may make sense to you, if you spontaneously combusted one day and another developer had to take over, he will struggle to understand what was there in the past.

Install your source control software on another machine, preferably a more secure one. If a server is unavailable then attempt to justify the cost of this purchase to your managers. If they don't agree, then clutch at straws, but install it somewhere. In the long run, it'll be helpful to everyone working in that company. You might even convince them by mentioning that they can store their documents in source control for versioning.

[RobDog888]

Yea you can store ANY file in VSS. Also, it doesnt "have to be" installed on a server. Just any workstation that will always be on and you can also locate the vss db anywhere, even on another system.

[szlamany]

We keep VSS on a server in our office. But all the developer workstations, laptops and such do a regular "get latest version" of most everything. I believe in multiple copies...

We keep all our SPROCS in VSS as well. Save them as .SQL text files from whatever query tool you use.

Having SPROCS as text files allow for searching (we developed a silly little RTB search tool). It also allows for easy automation of SPROC updates at client sites.

The versioning and comparing aspect of a source-control product is what I find the most beneficial.

We also burn CD's of the VSS data folder tree - keep them off site (my kitchen!).

[RobDog888]

You keep your backup cd's in your kitchen? I hope they are not in your oven
Probably in the freezer would be the safest place in case of fire.

[Shaggy Hiker]

Actually, if you are keeping backup CD's, there are probably some fire secure options that won't break the bank. I have a couple fireproof filing cabinet type things (lock boxes, but not really safes) that will keep paper from burning. I don't actually know what would happen to a CD in such a thing. Would it be destroyed by the heat, even though the temp didn't get hot enough to damage paper? Not sure. Those can be a cheap and easy solution for CD storage, though.

[MMock]

While your current solution of backups may make sense to you,

I don't know if it makes sense to me, it's just what I do out of desperation.

Anyway, there's a difference between source code control and version control. I think absolutely if you are in production and making changes you want version control so you can fall back one whole version (or more). I'm still developing and I don't really need to "fall back" because my requirements aren't changing. So now I am more concerned about having my source safe; I guess later I will want my versions safe!

Thanks!

[MMock]

If you consider the time you are spending each day to make a manual zip and backup you will quickly surpass that time savings quickly

That point is well taken. Thanks.

Go with VSS IMO

I probably will, and I know who to ask if I get stuck!

[Kasracer]

Anyway, there's a difference between source code control and version control.

No there isn't. Source control stores copies of your source at different versions. Version control stories copies of your source at different versions.

VSS, TFS, SVN, etc are all called both.

[szlamany]

I find the ability to review differences beneficial regardless of the stage of development. I like to check-in every day and check-out every morning.

[RobDog888]

Anything that copies your code in backup scenerios (like a daily backup) "could" be called source control while version control is more specific to the versioning, history and differences between check-ins.

[Shaggy Hiker]

I like to check-in every day and check-out every morning.

That's funny, I do the exact opposite