{"id":14561,"date":"2015-12-08T11:00:00","date_gmt":"2015-12-08T19:00:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/dataplatforminsider\/2015\/12\/08\/speeding-up-business-analytics-using-in-memory-technology\/"},"modified":"2024-01-22T22:52:18","modified_gmt":"2024-01-23T06:52:18","slug":"speeding-up-business-analytics-using-in-memory-technology","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2015\/12\/08\/speeding-up-business-analytics-using-in-memory-technology\/","title":{"rendered":"Speeding up Business Analytics Using In-Memory Technology"},"content":{"rendered":"

New challenges<\/h1>\n

Businesses have always used data and analytics for improved business decisions. As the new age of the IOT (Internet of Things) approaches, businesses are experiencing exponential data growth and the challenges that come along with managing large data sets. At the same time, tools like Power Pivot democratize data access to these large data sets across the whole business. As more employees have access to these large data sets, the analytics queries asked by these employees tends to be more ad-hoc rather than queries easily answered by pre-aggregated cubes. In-Memory analytics improvements in SQL Server 2016 addresses these new challenges by providing significant data compression and speeding up analytics query performance up to 100x.<\/p>\n

Common configuration<\/h1>\n

Traditionally, customers have modeled the data using multidimensional online analytical processing (MOLAP<\/a>) with pre-aggregated data or with Tabular Model<\/a> and the source of data in the database with periodic ETL (Extract, Transform and Load). The picture below shows a typical deployment using SQL Server for relational DW and SQL Server Analysis Server (SSAS) for data modelling.<\/p>\n

\"<\/a>For both MOLAP and Tabular models the analytical queries run inside SSAS as shown by the blue box. This allows customers to gain the best analytical performance, even when their data sources are slow, but this approach has some challenges as described below.<\/p>\n