Hi All,
I have to change the Timestamp of length 23 to 19 in the Hash file for about a set of 500 Jobs. What could be the best practice to do this. Can we write some query to reduce the time spent to do this work .
Please let me know , if anyone can answer this question.
Thanks in Advance,
lax
Hash File and the Timestamp.
Moderators: chulett, rschirm, roy
a) I'd be very careful if you take that route. You wouldn't want to change every occurance of 23 - only the entries associated with your hash file.
b) Out of curiousity, why do you feel you 'need' to do this? What kind of a problem is this causing?
c) Welcome aboard!
b) Out of curiousity, why do you feel you 'need' to do this? What kind of a problem is this causing?
c) Welcome aboard!
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi Chulett
we perform this conversion from 23 to 19(timestamp). This is because we supress the millisec part in the datefield . If not done, the lookup might fail, even though the date and the time of the source is matching with that of the lookup.
Eg: normally we have the datefield as:
2004-11-11- 12:21:32.002. we truncate the last millisec part".002".
we perform this conversion from 23 to 19(timestamp). This is because we supress the millisec part in the datefield . If not done, the lookup might fail, even though the date and the time of the source is matching with that of the lookup.
Eg: normally we have the datefield as:
2004-11-11- 12:21:32.002. we truncate the last millisec part".002".