Another thing about Hadoop is that the files contain data in raw unstructured format (perhaps not necessarily but at least typically) and the MapReduce process parses and performs complex computing just-in-time. I can see how that's practical for some specific applications, like ad-hoc analysis of documents or emails, and Hadoop may be a natural fit there.
But my belief is that most enterprise business users actually would prefer their data warehouse contain structured, relational, indexed data that can be retrieved using a familiar SQL interface. They don't want some MapReduce programming geek to get between them and their data.
Sure, Hadoop can follow-up with indexing, strong data typing, and a more fully featured SQL interface, but then they'd have to compete head to head with SQL Server in the deep end of the engineering pool. For SQL Server to take their existing relational engine and add federation is actually less of a stretch.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho