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!
@user-dy8xu7uj8kАй бұрын
Fikrat, thank you for creating such a detailed content.
@fazizovАй бұрын
Glad you enjoy it, thanks!
@douglaspiresmartins29552 ай бұрын
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 ?
@fazizov2 ай бұрын
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.
@user-ce9tn6qh5r2 ай бұрын
I saw when creating a primary key, you specifying as NonClustered index, why not Clustered?
@fazizov2 ай бұрын
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