Surrogate Key - wrong generation
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 151
- Joined: Fri Feb 13, 2009 4:19 pm
-
- Premium Member
- Posts: 151
- Joined: Fri Feb 13, 2009 4:19 pm
-
- Premium Member
- Posts: 151
- Joined: Fri Feb 13, 2009 4:19 pm
-
- Premium Member
- Posts: 151
- Joined: Fri Feb 13, 2009 4:19 pm
Hi
I changed the "Pre-Load file to memory" to Disabled and the job didnt have any problem. It generated sequence in correct fashion.
I suspesct the file might be locked from getting updating and thats why it was reading the most recent value and generating the error. Or dure to less memory / cache the issue might have arrised. Now i recall that my co-worker was also running a job that had lots of look up stages and join and he consumed most of the resources. That could be the reason why my job was running slow.
Please share your comments.
Criag I would like to thank you personally for your support. You helped me to fix this issue. Thank you so much.
I changed the "Pre-Load file to memory" to Disabled and the job didnt have any problem. It generated sequence in correct fashion.
I suspesct the file might be locked from getting updating and thats why it was reading the most recent value and generating the error. Or dure to less memory / cache the issue might have arrised. Now i recall that my co-worker was also running a job that had lots of look up stages and join and he consumed most of the resources. That could be the reason why my job was running slow.
Please share your comments.
Criag I would like to thank you personally for your support. You helped me to fix this issue. Thank you so much.
Thanks
Karthick
Karthick
No problem, that's why I do this.
I too would think this is memory / cache related, I would wager that your in memory footprint for this hashed file grew until it would no longer fit into memory and generated the informational message you saw. After that, perhaps your updates were only stored on disk at that point and what you were pulling from memory was stale as it was no longer being updated properly. [/guess]
Anyway, all better now.
![Wink :wink:](./images/smilies/icon_wink.gif)
I too would think this is memory / cache related, I would wager that your in memory footprint for this hashed file grew until it would no longer fit into memory and generated the informational message you saw. After that, perhaps your updates were only stored on disk at that point and what you were pulling from memory was stale as it was no longer being updated properly. [/guess]
Anyway, all better now.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
![Laughing :lol:](./images/smilies/icon_lol.gif)
So... "not quite". Was that strictly a forum related response or does the Master have the real explanation of the issue waiting up his sleeve for a post-forum-move reveal?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers