In its non-Big Data world, STAD data would be resorted to whenever an SAP Basis admin got a call from the users saying that the performance of a specific program was slow. Let me expand a bit on how the use cases are being transformed. With no way of customizing the views or aggregating them, the notion of using them to do anything other than a narrow performance analysis in the past was simply impossible.īottom line: without capturing STAD data and moving it to an SAP-certified analytics platform, leveraging STAD was a non-starter.Įnter PowerConnect, and its ability to connect SAP to Splunk, fulfilling the Big Data promise in SAP. Pulling these reports in a production environment creates heavy load, the investigation process is tedious, and to make things worse, STAD records are only stored for a few days at maximum. Most SAP Basis teams I meet only see STAD as a transaction to be used in moderation to troubleshoot performance. So, it’s no mystery why this has been one of the most difficult datasets to analyze and work with across SAP environments that were primarily designed to process business data in real-time, rather than crunching huge volumes of analytical performance data. generating “big data” way before it was cool. Exciting, huh? STAD is the “hipster” T-Code in SAP. STAD data, AKA Business Transaction Analysis records, deliver granular performance statistics on essentially every unit of work processed by SAP.
0 kommentar(er)
