performances

[Former Member]

wt is the diff between extended program check,runtime analysis,sql tracer,codeinspector?

[Sm1tje]

extended program check: when writing a program, you can have it checked for syntax errors, like SELET instead of SELECT. So only a check on syntax, data declaration etc. However, when you are doing an extended program check, it also checks for example whether you have typed your (import,export, tables) parameters correctly when calling a function module. This will give no error during standard program check, but It will give an error in extended program check.

runtime analysis: when you are creating / using a report for example, and the performance is (really) bad, you can do a runtime analysis to find out, where exactly the report takes a lot of time processing. Is it a select statement, a subroutine, or whatever. The overview will give you all the possible points in your coding where one should have a look at.

SQL tracer: when you want to know which database tables are being used in a certain transaction, screen, report, you can run an SQL trace. The overview will give you all database tables that were used.this way you can find out, for example, where your data is stored (in which DB table).

Codeins$pector: this is an even more 'extended' program check. It will give you an overview of all errors and warnings. But it will also give you some pointers as to where the performance will possibly give you problems. And much more.

I would say, try all of them and you will find out yourself. Always the best way.

[Former Member]

Hi Kranthi,

Extended Program Check:

You use this function to perform static checks, which are too time consuming for the normal syntax check. The extended program check returns both errors and warnings and it is possible to run either individual specialized tests or one whole standard check.

Run Time Analysis:

The runtime analysis provides an overview of the duration of your source code, from individual statements up to complete transactions.

For large applications it is recommended that you first analyze the entire application and hit list.

With the following information you can carry out the analysis, display and interpret the results, and use this as a basis for optimizing your programs.

SQL Tracer

The SQL Trace feature is another of R/3?s ABAP Workbench suite of tools - the Performance Trace tool. Its common usage is by Oracle DBAs and ABAP programmers for Performance Tracing (database access, locking activities and remote calls of reports and transactions) and for error/fault investigations.

ABAP programmers employ it primarily for ABAP report performance tuning and table Index verification. Our area of concern is the SQL Trace portion of the Performance Trace tool.

Code Inspector:

The Code Inspector is a tool for checking static ABAP coding and DDIC objects (i.e. generally all objects of the Object Repository) under aspects of functional correctness, performance, security, reliability, and statistical information.

These are the main uses of them. If you want more information reply me i will provide you the required information.

<REMOVED BY MODERATOR>

Edited by: Alvaro Tejada Galindo on Apr 15, 2008 3:03 PM