DSXchange

Hi,

Calling stored procedure in PX, requires to define System DSN on DS server.
Does it slows performance heavily?

(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.

with performance, I mean time and server utilization.
with heavy, i mean slower ETL server.
if it helps you

yuva010 wrote:Calling stored procedure in PX, requires to define System DSN on DS server. Does it slows performance heavily?

No. There's no inherent penalty in simply defining a 'system DSN'.

if i use 'Stored Proc stage' to call stored procedure using system DSN and pass some parameters to this stored proc.
Does it slows ETL performance in terms of Time?

That would depend entirely on the proc, would it not? Try it, let us know.

I don't think you will have performance issue with DSN. All that DSN is used is to make a call to storedproc in the database. Once the call is made the performance depends on your database and server where your database is residing. Only at the end the results are returned.

Thanks guys!
I'll let you know.. once it goes in Build Phase.