Ansicht
Dokumentation
01519 - Deleting SQL Packages
rdisp/max_wprun_time - Maximum work process run time ABAP Short ReferenceThis documentation is copyright by SAP AG.
Deleting SQL Packages
Another question to further our understanding of SQL packages in general:I had thought that there was an SQL package for each physical table (ie, PF) in
the database. For example, the SQL package for table VBAK is called VBAK in
library R3PRDX0000. However, I have not found this to be the case for all
tables. For example, if I search for all objects called ANLZ*, I find the
following:
Object Type Lib Attribute
ANLZ *FILE R3DVDDATA PF
ANLZ_00001 *FILE R3DVDDATA LF
ANLZ_00002 *FILE R3DVDDATA LF
ANLZLD *SQLPKG R3DVD31970
Note the sqlpkg has a different name from the file. Are these related? For
table MONI, I find the following:
MONI *FILE R3PRDDATA PF
MONI *SQLPKG R3PRDX0000
MONIKT *SQLPKG R3PRD31950
There are 2 sql packages that might be for table MONI. And for other tables I
do not find any sql package of a similar name. Does this table not have an sql
package or is it named quite differently? So the question is,
==> How do you determine what sqlpkg contains the optimized sql statements for a
particular table?
This can be valuable, because if you create a secondary index over a table as
Mike mentioned, you need only delete the sql package for that particular table,
not all sql packages. This would save lots and lots of time and reduce the
subsequent performance hit when the packages are rebuilt.
Hopefully, we have an SQL package "guru" who can shed some light on these
questions for all of us!
Regards,
Claudia Pillich
Basis Consultant
Intelligent Technology, Inc.
Atlanta, GA, USA
404-320-9102
-----Original Message-----
From: Mike Martin
I also like to delete packages after secondary index creations.
Additionally, I delete them after HP applications since HPs usually contain
many DDIC changes. I'm not certain if this is necessary, but it seems
logical. For someone who knows, is it necessary to delete them after HPs or
after creating new indexes? [For table changes, I presume that SAP always
performs a data export, drop table, create table, and then imports the data
back. This should delete the packages as well, correct?]
As for an 'expiration' time or useful life of the package, I'm not certain I
could ever reach that point with so many patches, etc., constantly being
applied.
Sorry I couldn't be more help, but I just want to add these questions to the
discussion.
Regards,
Mike D. Martin
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Matt MilneZe... [mailto:mattmilneZe...]
Sent: Tuesday, March 27, 2001 4:06 PM
To: Jim Sanders/Ontario/IBM
Cc: sap400
Subject: Deleting SQL Packages
Hi
How often do people delete SQL packages ?. After DB fixes and kernel
patches it is advisable but is anyone aware of a point at which it is worth
deleting the SQL packages and allowing them to be re-created ? It would seem
logical that there comes a point where the performance advantage of using an
existing package is outweighed by the time taken to search for it.
Any thoughts ?
Matt Milne
Freelance BASIS consultants
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
rdisp/max_wprun_time - Maximum work process run time Vendor Master (General Section)
This documentation is copyright by SAP AG.
Length: 3760 Date: 20240603 Time: 051338 sap01-206 ( 4 ms )
