@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!
@user-dy8xu7uj8k Ай бұрын
Fikrat, thank you for creating such a detailed content.
@fazizov Ай бұрын
Glad you enjoy it, thanks!
@douglaspiresmartins2955 2 ай бұрын
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 2 ай бұрын
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-ce9tn6qh5r 2 ай бұрын
I saw when creating a primary key, you specifying as NonClustered index, why not Clustered?
@fazizov 2 ай бұрын
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
KnowledgeBank by obviEnce
Рет қаралды 639
Ankit Bansal
Рет қаралды 38 М.
WACO Designers
Рет қаралды 37
Data with Zach
Рет қаралды 29 М.
Learn Microsoft Fabric with Will
Рет қаралды 30 М.