Forum Discussion
Solved
GUID and Date primary key column size issue
Hello, I have a bit of an issue I'm trying to solve... I have data which is for all users of a platform, at daily granularity. The users have a GUID as their ID, which even on it's own is la...
Not exactly. Both the Date and Person tables would relate directly to the fact table. But you could also replace your GUID string with an integer index in both tables for the relationship.
Pat
Do you mean like,
It doesn't help with that massive GUID column... we have several fact tables (they don't just eat apples, lol!) so with that column on every table it ends up being huge.
There are also other attributes on the Person ID table we would need to filter by - e.g. person 6A7811FD-AF14-4A90-8026-A3FD92E69726 doesn't always like apples 🤔
Not exactly. Both the Date and Person tables would relate directly to the fact table. But you could also replace your GUID string with an integer index in both tables for the relationship.
Pat