DSXchange

Version 8.1 has corrected this issue.

Thanks to everyone who took the time to read this post.

Replace the ODBC Enterprise with the SQL Server Enterprise Stage. That is the target stage that we use to load our SQL Server databases and it seems to perform much faster than ODBC. I would create a copy of the job and change the copy's target to SQL Server Enterprise. Run job 1 and then the copy a...

I figured it out. I am so used to working on SQL Server I forgot that Oracle has the nice feature ROWNUM. DUH!!!

In the user defined SQL, all I have to do is:

SELECT * FROM #ORACLE_DB_SRC_TBL# WHERE ROWNUM <= 500

Works like a charm.

Sorry for the post.

Thanks,
Josh

I am loading data using this setup ODBC Enterprise --> Transformer --> SQL Server Enterprise. I am trying to select the top 500 rows from my source to load my Development Environment. I know this can be accomplished using the Sequential File Stage via the Read First Rows option, but I am reading fro...

Inside of DataStage Director, go to Tools and select Options. Once the Options dialog box pops up select the Limits tab and change warnings to No limit or select Abort job after: value to something > 50.

Hope this helps.

Create a User Defined Environment Variable with the 2 email addresses and place that variable in the Recipients email address: field in the Notification Activity. In our shop we have these addresses seperated by a ;

Hope this helps

Change your ODBC Enterprise to a Dynamic RDBMS stage. In the Update Action drop down of the Input/General tab you can choose "Truncate table then insert rows" or you could write your own custom before SQL that will be executed before the table is loaded. Under the SQL tab there is a before...

I have been using the Stored Procedure Stage in several parallel jobs to call various SQL Server stored procedures. I am now trying to invoke a SQL Server stored procedure and also pass-through additional column information to the output link for further processing. The job is set up like this (SQL ...