Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
lodewyk19
Participant
Posts: 2 Joined: Tue Aug 31, 2010 10:34 pm
Post
by lodewyk19 » Tue Aug 31, 2010 10:40 pm
Hi.
I'm trying to create a new SQL 2005 table by loading from a dataset into SQL. The loading stage is SQL Server Enterprise.
My problem is that it creates the table, but the column ordering is not the same as the dataset. Any assistence would be GREATLY appreciated
Thx.
ETLJOB
Participant
Posts: 87 Joined: Thu May 01, 2008 1:15 pm
Location: INDIA
Post
by ETLJOB » Tue Aug 31, 2010 10:54 pm
Is it a direct load or do you have some other logic in between?
lodewyk19
Participant
Posts: 2 Joined: Tue Aug 31, 2010 10:34 pm
Post
by lodewyk19 » Tue Aug 31, 2010 11:00 pm
ETLJOB wrote: Is it a direct load or do you have some other logic in between?
Hi there. It is a direct load.
ETLJOB
Participant
Posts: 87 Joined: Thu May 01, 2008 1:15 pm
Location: INDIA
Post
by ETLJOB » Tue Aug 31, 2010 11:30 pm
Uncheck the RCP option if it is enabled and give a try.
As an alternate, the table can be created in target first and you can use datastage to load.
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Wed Sep 01, 2010 6:57 am
It's a known "issue", no clue why it does what it does, but it does.
-craig
"You can never have too many knives" -- Logan Nine Fingers
vivekgadwal
Premium Member
Posts: 457 Joined: Tue Sep 25, 2007 4:05 pm
Post
by vivekgadwal » Wed Sep 01, 2010 8:10 am
I had a similar experience with the ODBC stage. I created the table and then ran the job, which I am sure you are also doing now. I really wonder what's the problem!
Vivek Gadwal
Experience is what you get when you didn't get what you wanted