Blog

Microsoft have made announcements about bringing Hadoop to Windows, but what does that mean for SQL Server? In this talk, Jeremiah Peschka will cover a the Hadoop ecosystem at a high level and discuss specific use cases for Hadoop. By the end of this talk, you should have a general idea of how different parts of Hadoop can be used to augment SQL Server’s rich functionality. This talk is for database professionals who are looking for ways to extend the capability of SQL Server with different pieces of the Hadoop ecosystem.

Getting Started with Hadoop

 

↑ Back to top
  1. Awesome intro about Hadoop to SQL community. I am interested to see how Microsoft will integrate this with SQL Server.

  2. Pingback: Something for the Weekend – SQL Server Links 02/12/11

  3. Pingback: Introduction to Hadoop « Click-Rex

  4. Pingback: Introduction to Hadoop « Click-Rex | Programmer Solution

  5. hello my Freand
    does hadoop support CRUD and Load balance for SQL Server

    HadoopServer1 HadoopServer2 … HadoopServerN

    Hadoop Provider(For SQL Server 2012)

    User1 User2 User3 ….UserN (Send CRUD Command )
    Does Support This Solution

    • I believe that you’ve confused Hadoop with an ORM. Hadoop is a family of products based around the Hadoop Distributed File System (HDFS) and Hadoop MapReduce – a job scheduling and execution framework.

      For CRUD procedure creation, you should look something like into Entity Framework, nHibernate, or LLBLGen.

      For load balancing SQL Server, you should probably talk to an architect or consultant.

  6. Thanks.
    I need Solution for Loadbalance SQL Server in
    Insert Update Delete Select
    many user ,…
    Oracle :RAC
    SQL: ? (Hadoop or ?)

  7. Thanks for the great presentation Jeremiah.
    Do you mind sharing your thoughts about what type of queries will perform better on Hadoop as oppose to relational database and vice versa?

    Thanks,
    Matan

    • Hi Matan, great question. Honestly, the question is too complex for even a blog post comment, but I’ll give it a shot anyway.

      If you’re thinking about warehousing, any query that can easily be split among multiple nodes is likely to perform better on a Hadoop based system. Likewise, anything that you can break down into a series of Map and Reduce phases will perform well.

      If you are thinking about OLTP, things get tricky because there is no OLTP alternative in the Hadoop world that speaks a SQL dialect. Instead you have to re-arrange the way you query to make sense in HBase’s data model.

  8. Pingback: Hadoop in a Microsoft environment | Data story

  9. Pingback: Hadoop « SQLAnidma

  10. Pingback: Hadoop for SQL DBA « SQLAnidma

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>