Just one of the reasons I like working with CapTech is our agnostic approach to technologies.  Our Data Management and Business Intelligence Practice Area includes many consultants certified with their favorite technologies.  At our internal meetings, we hear some variation of “my BI technology is better than your BI technology.”  Whether the topic is database platforms, data integration tools or data presentation capabilities, well-informed suggestions are freely shared only to be countered by alternative viewpoints.  That sort of friendly competition keeps us on our toes.

Over the years, I personally have had the good fortune to work with many database, ETL, and presentation tools.  Each of those tools impressed me in some fashion and disappointed me in some other way.  No tool was perfect.  Most importantly, each tool was at the mercy of the design attempting to leverage the tool.

Lately I have focused on Microsoft's Busines

Whatever happened to good coding practices.  It seems every Informatica map I look at these days has only the default object name from which to gleem meaning.  Why do developers insist on leaving a complete mess when they develop Informatica maps?  Does it have anything to do with unrealistic deadlines, developers in such a hurry to pump out mappings, that they don't have time to label their transformation objects?  Could it be developers have never been trained in proper naming conventions and metadata coding standards?  Or is it just the commoditization of data in