US 11,080,166 B2Granted

Database trace debugger

AssigneeSap SE

InventorsLong Du, Yu Wang

Life of this patent

Estimating the term…

Loading patent…

Abstract

This disclosure describes a trace debugger (TDB) that is used for database workload replay and database debugging. The TDB maintains consistency through synchronization of the state between the database and a corresponding database trace replay. The TDB can provide a sliding window environment for code block execution and global context sharing. The TDB can be used to interactively analyze and troubleshoot various types of database problems by debugging the database itself, query code (e.g., SQL), performance, end-to-end execution, and plan traces, which can be recorded using scripts. In some implementations, the TDB also provides reverse debugging for historical database state analysis, and/or incremental debugging for dynamic editing and debugging within a session without the need to exit the debugger and perform a full rebuild of the code.

Claims17

Dependent claims

A computer-implemented method performed by at least one processor, the method comprising:

capturing, by the at least one processor, a trace from a production version of a database that operates in a production environment, wherein the trace is a log that indicates a state of the database and of a program executing to access the database, wherein the state is a recording of variables, classes, modules, and functions in a code block;
executing, by the at least one processor, a trace debugger (TDB) in a test environment that is separate from the production environment;
replaying, by the at least one processor, the captured trace in the TDB to debug the trace in a debugging session while the trace is executing in a test version of the database operating in the test environment;
receiving, by the at least one processor, at least one edit to code of the program, the at least one edit made through the TDB;
rebuilding, by the at least one processor, the program, within the debugging session, to incorporate the at least one edit, wherein the rebuilding of the program is incremental to rebuild at least one portion of the program that was altered through the at least one edit;
and
resuming, by the at least one processor, debugging of the trace, through the TDB, within the debugging session, at a checkpoint that was previously generated to describe a snapshot of the trace at a point that is proximal to current line number of the program.

4 more elements

A computer system, comprising:

at least one processor;
and
a non-transitory memory communicatively coupled to the at least one processor, the memory storing instructions which, when executed by the at least one processor, cause the at least one processor to perform operations comprising:
capturing a trace from a production version of a database that operates in a production environment, wherein the trace is a log that indicates a state of the database and of a program executing to access the database, wherein the state is a recording of variables, classes, modules, and functions in a code block;
executing a trace debugger (TDB) in a test environment that is separate from the production environment;
replaying the captured trace in the TDB to debug the trace in a debugging session while the trace is executing in a test version of the database operating in the test environment;
receiving, by the at least one processor, at least one edit to code of the program, the at least one edit made through the TDB;
rebuilding, by the at least one processor, the program, within the debugging session, to incorporate the at least one edit, wherein the rebuilding of the program is incremental to rebuild at least one portion of the program that was altered through the at least one edit;
and
resuming, by the at least one processor, debugging of the trace, through the TDB, within the debugging session, at a checkpoint that was previously generated to describe a snapshot of the trace at a point that is proximal to current line number of the program.

7 more elements

One or more non-transitory, computer-readable media storing instructions which, when executed by at least one processor, cause the at least one processor to perform operations comprising:

capturing a trace from a production version of a database that operates in a production environment, wherein the trace is a log that indicates a state of the database and of a program executing to access the database, wherein the state is a recording of variables, classes, modules, and functions in a code block;
executing a trace debugger (TDB) in a test environment that is separate from the production environment;
replaying the captured trace in the TDB to debug the trace in a debugging session while the trace is executing in a test version of the database operating in the test environment;
receiving, by the at least one processor, at least one edit to code of the program, the at least one edit made through the TDB;
rebuilding, by the at least one processor, the program, within the debugging session, to incorporate the at least one edit, wherein the rebuilding of the program is incremental to rebuild at least one portion of the program that was altered through the at least one edit;
and
resuming, by the at least one processor, debugging of the trace, through the TDB, within the debugging session, at a checkpoint that was previously generated to describe a snapshot of the trace at a point that is proximal to current line number of the program.

4 more elements

Dependencies are inferred from the claim text.