Table Definition Repository
Moderators: chulett, rschirm, roy
Table Definition Repository
Hallo all
This is more out of interest that I am asking.
Is it only me, or is managing table definitions within DS a nightmare? I have developers creating table defs left right and centre (including me), and, even though we have predefined categories, we still have the odd definition being created in a random place within the repository. My point is that its just too easy to create definitions anywhere.
How have you guys prevented this issue?
This is more out of interest that I am asking.
Is it only me, or is managing table definitions within DS a nightmare? I have developers creating table defs left right and centre (including me), and, even though we have predefined categories, we still have the odd definition being created in a random place within the repository. My point is that its just too easy to create definitions anywhere.
How have you guys prevented this issue?
dnzl
"what the thinker thinks, the prover proves" - Robert Anton Wilson
"what the thinker thinks, the prover proves" - Robert Anton Wilson
Appoint a metadata steward. I've found that someone has to be in charge of keeping the repository clean, enforcing standards, etc. Your issue with table definitions is true also for functions, jobs, etc. A rigorously enforced standard that is periodically reviewed and refined is the best approach, in my opinion.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
I was afraid this was the case. Perhaps a good spanking is in order :D
I think we'll keep to the standards we have and accept that using the repository is a learning process for the developers.
I think we'll keep to the standards we have and accept that using the repository is a learning process for the developers.
the joys of documentationyes... the table definition IM_SAVING_THIS_AGAIN_ZZZZ is stored somewhere and doesnt mean anything to anyone else. look at the standards!
dnzl
"what the thinker thinks, the prover proves" - Robert Anton Wilson
"what the thinker thinks, the prover proves" - Robert Anton Wilson
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I recently completed a "best practices audit" for a client. One of the not-so-best practices I uncovered was use of the Saved category of Table Definitions. Developers (properly) use this as temporary storage for example to migrate column definitions from the input side of an Aggregator stage to the output side, but never clean up. I found seven saved versions of the same table definition in seven different Saved sub-categories. This is also something for your metadata steward to manage. Perhaps a rule like automatic deletion from Saved after seven days? There's nothing to prevent a Save to a "proper" category, if that's the intent.
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.
This is/was the intent, but Im interested as to how we are going to auto delete after 7 days? Are we talking a bit of BASIC code that goes into the repository and does the cleanup. Is there a topic that has covered this before so I can go do some reading..ray.wurlod wrote:Perhaps a rule like automatic deletion from Saved after seven days? There's nothing to prevent a Save to a "proper" category, if that's the intent.
dnzl
"what the thinker thinks, the prover proves" - Robert Anton Wilson
"what the thinker thinks, the prover proves" - Robert Anton Wilson
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There's nothing out there, but it wouldn't be too difficult. Date/time modified is in DS_AUDIT.
will get you started will get you even closer. You will need also to look at DTC for any that have not been modified. You may also need to join to DS_METADATA (WHERE DS_AUDIT.INSTANCE = DS_METADATA.DSRID) to get the CATEGORY.
Code: Select all
SELECT INSTANCE, DTM FROM DS_AUDIT WHERE CLASS = '4';
Code: Select all
SELECT INSTANCE, DTM FROM DS_AUDIT WHERE EVERY DTM < '2004-08-14';
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.