Ansicht
Dokumentation
03503 - DB2 Locking
Vendor Master (General Section) BAL Application Log DocumentationThis documentation is copyright by SAP AG.
DB2 Locking
I have a general question for the group. Our data warehouse team isrecommending that we use ODBC access to read and download SAP production
table data to an SQL server. My thoughts are that this isn't a very good
idea, yet I need your help to clarify and define objections (and quickly if
possible...the train is moving very fast in this wrong direction!).
First, the memory of the 400 will be used for the ODBC queries outside of
SAP's memory management which could force swapping and invalidations of SAP
memory objects. Second, I've heard that while long reads are occurring on
these tables, data cannot be updated (if the read is using an index, for
example). I'm not certain if this is true, but I think that someone on this
list will definitely know. Third, I am uncertain of the overhead on
communications, disk subsystems, memory, etc, of ODBC access. I thought one
of you would know that as well. Lastly, almost all system monitoring, etc,
currently occurs in SAP, whereas this proposal would force more monitoring
on AS/400 server level.
Any clarification on the above objections are greatly appreciated. Also,
any other benefits/downsides that I haven't considered?
Thanks in advance,
Mike D. Martin
SAP Basis Administrator
AO*SOLA
707-763-9911 x6106
email: <mailto:mmartinZs...>
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
General Material Data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 1953 Date: 20240425 Time: 231631 sap01-206 ( 3 ms )
