Share
ReportWhich datatype is recommended to use for Customer table primary key and how it affects on refresh performance?
You’re offline. This is a read only version of the page.
7
Which datatype is recommended to use for Customer table primary key and how it affects on refresh performance?
Hi James,
The primary key is an attribute unique to the table.
For an attribute to be a valid primary key, it shouldn't include duplicate values, missing values, or null values. String, integer, and GUID data type attributes are supported as primary keys.
There's not quite the same number of datatypes you're probably used to in a RDBMS. I believe everything is ultimately ingested into SPARK / parquet files so most things will ultimately end up as Strings. Guids for instance do. Unless it's changed recently you can't use Integers so overall, Strings are the most common type. Regarding performance, I don't think there's a whole lot of difference, the m3 process takes a while to process and I don't think you'll notice a whole lot of difference one way or other in general.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (
