{"id":14551,"date":"2015-12-09T09:00:00","date_gmt":"2015-12-09T17:00:00","guid":{"rendered":""},"modified":"2024-01-22T22:52:18","modified_gmt":"2024-01-23T06:52:18","slug":"real-time-operational-analytics-using-in-memory-technology","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2015\/12\/09\/real-time-operational-analytics-using-in-memory-technology\/","title":{"rendered":"Real-Time Operational Analytics Using In-Memory Technology"},"content":{"rendered":"

Operational workloads refer to the business transactions that are critical to running a business. For example, a retail store has a transactional system to create or modify new orders, and a credit card company tracks all charges made by vendors on behalf of its customers. These transactional systems are critical to businesses, as any downtime or slowdown will have a direct impact on the business\u2019s bottom line. Therefore, these systems are designed for performance\/scalability and configured with high availability. Equally important to operational workload are the analytics that business use to answers questions such as, \u201cWhat is the average time to fulfill an order?\u201d<\/p>\n

Most customers implement analytics by setting up a Data Warehouse on a different machine similar to the configuration described in my recent post<\/a> on using In-Memory technology with periodic flow of data through ETL (Extract, Transform and Load) from operational system to Data Warehouse. This approach of optimizing\/isolating operational and analytics workloads has served well, but there are some drawbacks:<\/p>\n