hashed file - (project directory or different directory)
Moderators: chulett, rschirm, roy
hashed file - (project directory or different directory)
Is there any advantage of having hashed files in project directory (i.e. under account name) over having hashed files in different directory.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Only one. It's easier to delete the project.
Best practice is to keep your hashed files in a separate directory, perhaps a sub-directory in the project directory. But if they're going to grow large, then maybe a separate file system is indicated. Create a script to delete the hashed files.
Best practice is to keep your hashed files in a separate directory, perhaps a sub-directory in the project directory. But if they're going to grow large, then maybe a separate file system is indicated. Create a script to delete the hashed files.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hi ArndW
Your answer i cannot view fully properly...because it seems u r premium context .For Temporary basis can you mail your answer on vinita.bhate@gmail.com so that i will be clear in understanding
Thanks in advance
Your answer i cannot view fully properly...because it seems u r premium context .For Temporary basis can you mail your answer on vinita.bhate@gmail.com so that i will be clear in understanding
Thanks in advance
Regards and Thanks,
Vinita Bhate
Vinita Bhate
Hi,
As stated earlier, it is better to store the hashed files in a particular directory. In this case you can track the hashed files easily rather then seraching for them in the project home. In our project for all the jobs we have separate folders where the hashed files are explicitly stored. You can also delete the hashed files on a timely basis, as the hashed files get generated every time the job runs.
Sai
As stated earlier, it is better to store the hashed files in a particular directory. In this case you can track the hashed files easily rather then seraching for them in the project home. In our project for all the jobs we have separate folders where the hashed files are explicitly stored. You can also delete the hashed files on a timely basis, as the hashed files get generated every time the job runs.
Sai
-
- Participant
- Posts: 7
- Joined: Wed Sep 19, 2007 1:56 am
- Location: County Durham, UK
Personally, I like to use the project area because then you have all the Universe commands available to you. I know you can set a pointer in the VOC to get around this but if you want to check whether a row exists its so much easier to just go into Administrator and type in a bit of SQL.
BUT... a lot of people say you should never use the project area because if you run out of space you'll leave Datastage rolling around on its back kicking its legs in the air. Datastage saves all its internal hashfiles in the project area. Its easy enough for the log files to get huge, if you're putting all your data in there as well then things can fill up quickly. If you run out of space then you'll usually end up corrupting the internal hashfiles and leave things in right a mess.
So I tend to save small hashfiles for lookups in the project area but big 64 bit hashfiles always go into an area of their own.
Hope that helps,
Dave
BUT... a lot of people say you should never use the project area because if you run out of space you'll leave Datastage rolling around on its back kicking its legs in the air. Datastage saves all its internal hashfiles in the project area. Its easy enough for the log files to get huge, if you're putting all your data in there as well then things can fill up quickly. If you run out of space then you'll usually end up corrupting the internal hashfiles and leave things in right a mess.
So I tend to save small hashfiles for lookups in the project area but big 64 bit hashfiles always go into an area of their own.
Hope that helps,
Dave
DataStageSolutions - I tend to take the best of both worlds in this case. I will always place the hashed files (regardless of initial or expected size) in a different directory. But I will then put a remote pointer to the hashed file in the project VOC so that I can use normal commands. Filling up the project directory is a bad thing that usually done once per project...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 7
- Joined: Wed Sep 19, 2007 1:56 am
- Location: County Durham, UK