Null handling for 200 / 300 columns at one go.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 28
- Joined: Sat May 03, 2008 3:57 am
- Location: chennai
Null handling for 200 / 300 columns at one go.
Hi,
I have a table with 400 columns and i may expect 200 columns with null data ( say 10% of cases ) , and my job will get aboret in dev / sit / production if no of warnings > 50 , if i want to handle this at one go instead of writing for each and every column, how to achieve this?
Any easier method to achieve the same.
Thanks,
friend.kak@gmail.com
I have a table with 400 columns and i may expect 200 columns with null data ( say 10% of cases ) , and my job will get aboret in dev / sit / production if no of warnings > 50 , if i want to handle this at one go instead of writing for each and every column, how to achieve this?
Any easier method to achieve the same.
Thanks,
friend.kak@gmail.com
- Dev
Re: Null handling for 200 / 300 columns at one go.
Hi
suppress the warnings from director .
Thanks
sanjay
suppress the warnings from director .
Thanks
sanjay
friend.kak@gmail.com wrote:Hi,
I have a table with 400 columns and i may expect 200 columns with null data ( say 10% of cases ) , and my job will get aboret in dev / sit / production if no of warnings > 50 , if i want to handle this at one go instead of writing for each and every column, how to achieve this?
Any easier method to achieve the same.
Thanks,
friend.kak@gmail.com
Re: Null handling for 200 / 300 columns at one go.
Hi
suppress the warnings from director .
Thanks
sanjay
suppress the warnings from director .
Thanks
sanjay
friend.kak@gmail.com wrote:Hi,
I have a table with 400 columns and i may expect 200 columns with null data ( say 10% of cases ) , and my job will get aboret in dev / sit / production if no of warnings > 50 , if i want to handle this at one go instead of writing for each and every column, how to achieve this?
Any easier method to achieve the same.
Thanks,
friend.kak@gmail.com
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 28
- Joined: Sat May 03, 2008 3:57 am
- Location: chennai
Thanks for replies so far, but still I need a smart method of handling this at one go , may be handling at source side as suggested , or may be a routine which can help on this..... Yet to decide on this implementation. Thanks, friend.kak@gmail.com
- Dev
-
- Participant
- Posts: 28
- Joined: Sat May 03, 2008 3:57 am
- Location: chennai
Thanks for replies so far, but still I need a smart method of handling this at one go , may be handling at source side as suggested , or may be a routine which can help on this..... Yet to decide on this implementation. Thanks, friend.kak@gmail.com
- Dev
-
- Premium Member
- Posts: 892
- Joined: Thu Oct 16, 2003 5:18 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 28
- Joined: Sat May 03, 2008 3:57 am
- Location: chennai
Hi Sreeni,
Thanks for info, Do you mean to say to create schema file like this and try.
col1: nullable timestamp {null_field=""} ;
col2: nullable timestamp {null_field=""} ;
...
col400: nullable timestamp {null_field=""}
Do you mean the same? if this is the same , then we are doing Null handling here itelf. i tried this. Thanks. friend.kak@gmail.com
Thanks for info, Do you mean to say to create schema file like this and try.
col1: nullable timestamp {null_field=""} ;
col2: nullable timestamp {null_field=""} ;
...
col400: nullable timestamp {null_field=""}
Do you mean the same? if this is the same , then we are doing Null handling here itelf. i tried this. Thanks. friend.kak@gmail.com
- Dev