Tuesday, December 13, 2005
I was reading this article on sourcesafe best practice and found out that I should have been running analyze.exe once a week (at least monthly)....hmmmm....how about never...
so now I'm thinking I really should analyze my vss db.
So I ran analyze in analyze-only mode (i.e. not fix) and I have quite a few "potentially serious errors or inconsistencies".
Now the question is...should I run analyze and let it fix those inconsistencies. Given that no-one has reported any problems am I going to introduce a whole bunch of problems by fixing the inconsistencies.
This article has some useful info on backing up the database as well as analyzing it. For instance, not analyzing over a UNC share.
Anyway, I think the key is to backup the database first and then run analyze on the backup to work out what the damage might be...I think this is a task for next week...its waited this long...so another week won't hurt. Will it?....
Friday, December 02, 2005
Thursday, December 01, 2005
One thing I would like to do with this blog, is to provide a means to access source code for some of the handy (simple but handy) utilities that end up getting developed over the years. You know the kind of thing that doesn’t take too long to code, but saves a lot of time.
I haven’t figured out the best way to do this yet. I guess hosting the source code somewhere and linking to it, but what about licensing and legal disclaimers etc. I want everything to be free but don’t want any responsibility for the code. I always wanted to write an article for http://www.codeproject.com but never seem to have the time. I guess http://www.opensource.org is a good place to start for licensing info….