6.05 Mastering end-to-end Synapse Warehouse Solution

[@MikeFortmanBI]

Excellent video, Fikrat. It's clear that a lot of effort went into this. I really appreciate the time you take laying out the steps with slides before moving into the code.

[@fazizov]

Thanks for the feedback, Michael!

[@douglaspiresmartins2955]

Awesome content Fkrat. One question; Since the PK in Silver.Trips table are NOT ENFORCED, it´s possible to add a duplicate value in the GeographyID column right? Does it make sense to add a PK which not ensure uniqueness ?

[@fazizov]

Thanks for feedback, Douglas. Yes, you're right - PK constrains will not prevent duplicate values, so in that sense they're not even truly constraints. According to Microsoft, the potential benefits of PK and FK constrains include improved query performance and their help in showing relationships between tables in modelling tools.

[@平凡-p1v]

I saw when creating a primary key, you specifying as NonClustered index, why not Clustered?

[@fazizov]

That's right, both NONCLUSTERED and NOT ENFORCED are required clauses when adding PK constraint to Synapse WH tables, see here more details: learn.microsoft.com/en-us/sql/t-sql/statements/alter-table-column-constraint-transact-sql?view=fabric

[@Shreekanthsharma-t6x]

Fikrat, thank you for creating such a detailed content.

[@fazizov]

Glad you enjoy it, thanks!