Configuration Management usually focuses on source code management, build and release engineering with automated deployment. Data is often left to the business analysts and DBAs who focus entirely on data every day. I am seeing an interesting trend where data is becoming an essential consideration for CM gurus to consider. First and foremost is the fact that data can involve complex configuration management. The configuration of many systems is being driven by hundreds, if not thousands, of XML based configuration and property files. Getting these configuration exactly correct is no small task.

 

I am also seeing a strong focus on disguising data to produce robust and useful test data that does not contain any confidential information. Data has not always been the main concern of CM gurus - but it is now! What other ways does data impact configuration management? Why don't we have standards for the configuration management of data?

 

What do you think? What's your experience?

 

Bob Aiello

Editor in Chief

CM Crossroads

TrackBack URI for this entry