We are profiling some tables that are joined together with GUIDs. When we get to Key and Cross Domain Analysis IA correctly identifies the PKs but does not identify FK candidates.
I must admit that we have never gone this far into profiling so we may be doing something wrong here in order to identify the FKs, however, we discovered that it may have something to do with the LENGTH of the GUID columns (length=64). With some experimentation using shorter length idenitifiers, the FK candidates DO get identified. The magic number seems to be somewhere between 48 characters (this works) and 56 characters (does not work). As well, we have noticed that using the longer lengths results in the Format of the data being changed from a real format like '99a9a.999aa9.a9a9a.999a999.999a9a9a.999aa9.a9a9a.999a999' to simply 'NA'.
Is someone able to help resolve this issue so we can do Cross Domain analysis using GUIDs?
Thanks in advance!
Key Analysis on GUIDs
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Do your metadata correctly specify 64 as the length of the GUID columns in both the tables?
If so then you've probably uncovered a bug, and you should contact your official support provider. You might also search Fix Central to see whether there's any patch available for a bug of this kind.
If so then you've probably uncovered a bug, and you should contact your official support provider. You might also search Fix Central to see whether there's any patch available for a bug of this kind.
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.