Bringing back-in-time debugging down to the database

2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER) Pub Date : 2017-01-19 DOI:10.1109/SANER.2017.7884666

Arian Treffer, M. Perscheid, M. Uflacker

{"title":"Bringing back-in-time debugging down to the database","authors":"Arian Treffer, M. Perscheid, M. Uflacker","doi":"10.1109/SANER.2017.7884666","DOIUrl":null,"url":null,"abstract":"With back-in-time debuggers, developers can explore what happened before observable failures by following infection chains back to their root causes. While there are several such debuggers for object-oriented programming languages, we do not know of any back-in-time capabilities at the database-level. Thus, if failures are caused by SQL scripts or stored procedures, developers have difficulties in understanding their unexpected behavior. In this paper, we present an approach for bringing back-in-time debugging down to the SAP HANA in-memory database. Our TARDISP debugger allows developers to step queries backwards and inspecting the database at previous and arbitrary points in time. With the help of a SQL extension, we can express queries covering a period of execution time within a debugging session and handle large amounts of data with low overhead on performance and memory. The entire approach has been evaluated within a development project at SAP and shows promising results with respect to the gathered developer feedback.","PeriodicalId":6541,"journal":{"name":"2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)","volume":"35 1","pages":"521-525"},"PeriodicalIF":0.0000,"publicationDate":"2017-01-19","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/SANER.2017.7884666","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 2

Abstract

With back-in-time debuggers, developers can explore what happened before observable failures by following infection chains back to their root causes. While there are several such debuggers for object-oriented programming languages, we do not know of any back-in-time capabilities at the database-level. Thus, if failures are caused by SQL scripts or stored procedures, developers have difficulties in understanding their unexpected behavior. In this paper, we present an approach for bringing back-in-time debugging down to the SAP HANA in-memory database. Our TARDISP debugger allows developers to step queries backwards and inspecting the database at previous and arbitrary points in time. With the help of a SQL extension, we can express queries covering a period of execution time within a debugging session and handle large amounts of data with low overhead on performance and memory. The entire approach has been evaluated within a development project at SAP and shows promising results with respect to the gathered developer feedback.

查看原文本刊更多论文

将回溯时间的调试带到数据库中

使用回溯时间调试器，开发人员可以通过跟踪感染链回到其根本原因来探索在可观察到的故障之前发生了什么。虽然有几个这样的面向对象编程语言调试器，但我们不知道在数据库级别有任何回溯功能。因此，如果失败是由SQL脚本或存储过程引起的，开发人员就很难理解它们的意外行为。在本文中，我们提出了一种将回溯时间调试带到SAP HANA内存数据库的方法。我们的TARDISP调试器允许开发人员向后步进查询，并在以前和任意时间点检查数据库。在SQL扩展的帮助下，我们可以在调试会话中表达覆盖一段执行时间的查询，并以较低的性能和内存开销处理大量数据。整个方法已经在SAP的一个开发项目中进行了评估，并根据收集到的开发人员反馈显示出有希望的结果。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文求助全文

来源期刊

2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)

自引率

0.00%

发文量