Hi,
Calling stored procedure in PX, requires to define System DSN on DS server.
Does it slows performance heavily?
Calling Stored Proc
Moderators: chulett, rschirm, roy
Calling Stored Proc
Thanks,
Yuva.
Yuva.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
(Thinks: I can has cheezburger.)
Define "performance" in an ETL context. In what meaningful way can the adjective "heavy" be applied to what you have defined?
A system DSN is required because a user DSN is only accessible to whomever creates it. In any case, there is no such differentiation on UNIX; all DSNs are perforce system DSNs by virtue of the fact that there is only one currently active .odbc.ini file.
Define "performance" in an ETL context. In what meaningful way can the adjective "heavy" be applied to what you have defined?
A system DSN is required because a user DSN is only accessible to whomever creates it. In any case, there is no such differentiation on UNIX; all DSNs are perforce system DSNs by virtue of the fact that there is only one currently active .odbc.ini file.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: Calling Stored Proc
No. There's no inherent penalty in simply defining a 'system DSN'.yuva010 wrote:Calling stored procedure in PX, requires to define System DSN on DS server. Does it slows performance heavily?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers