Official News from Microsoft’s Information Platform
Machine Learning Blog
Data warehousing technology began as a framework to better manage, understand, and capitalize on data generated by the business, and it worked extremely well for many years. This is a space that Microsoft knows well with warehousing capabilities since 1995 with SQL Server.
However, there are several forces working to stretch the traditional data warehouse. Data volume is expanding tenfold every five years. Even the most robust SMP warehouse will require costly forklift operations to a larger and more expensive hardware footprint to keep up with the growth. Companies are using real-time data to optimize their businesses as well as to engage in dynamic, event-driven processes. The variety of new data types is proliferating with over 85 percent of new data coming from non-relational data such as logs, mobile, social, RFID, and devices.
Modernizing your data warehouse with new technologies can help you meet the needs of today’s enterprise to connect all volumes of any data with agile and familiar BI to business decision makers. This was validated by The Data Warehousing Institute (TDWI) who published a checklist to enable the modern data warehouse. At a high level, your new warehouse must be able to handle:
Microsoft has a comprehensive solution to modernize your data warehouse across software, appliance, and cloud for this new world of data. We invite you to learn more of our offerings:
SQL Server 2014
SQL Server Fast Track
Parallel Data Warehouse with PolyBase
SQL Server for DW in WA Virtual Machine
Non-relational Data (Hadoop)
Hadoop on Windows
Windows Azure HDInsight
You can learn more about Microsoft solutions for the modern data warehouse by tuning in for a live stream of our April 15th Accelerate your insights event and by visiting these resources:
Comments in this blog are open and monitored for each post for a period of two weeks after the posting date. If you have a specific question about a blog post that is older than two weeks, please submit your question via our Twitter handle @SQLServer