Tracking Server changes... what do all you do?

[mlchris2]

I want to start keeping track of all changes made to production servers. I thought about a spreadsheet or access db as cheap and easy solutions. Each has it own ups/downs. I am also trying to find some sort of cheap software package i can use to log and report changes, etc.

what are you all using?

Mark C.

 

[Mmitchell57]

I'm just using a xls spread sheet for now. I could imagine using a access DB to maintain all this info.

 

[mlchris2]

I use to use a XLS spreadsheet, then moved to ASP application using a SQL database. the problem I face is my developers add/delete/change things and do not update the tracking log.

i dont have much of a budget for this project... looks like i might need to do some Permission analysis and manage all changes on servers myself(which is how it should be).





Mark C.

 

[nmsexperts]

The trend is towards ITIL's CMDB. Google either of these terms if you are not familiar with them. Size, complexity, number of changes, number of people making changes are some of the factors that I would use to determine how simple or complex I would make the process. If you can afford it, I would recommend automated techniques to keep track of changes.

For low volatility/impact scenarios, a spreadsheet will do just fine.

 

[mlchris2]

Thanks for the info. Looks like I've got more research to do.

Mark C.