Become a sponsor to access source code ► [ Ссылка ]
Join Discord server with topics on C# ► [ Ссылка ]
Enroll course *Beginning Object-Oriented Programming with C#* ► [ Ссылка ]
Subscribe ► [ Ссылка ]

I will give you the database system ingredients, the most ordinary ones, but if you combine them lightly, there will be a nasty performance bug in your database. A puzzle? Yes, it's a puzzle.
Hear the ingredients first. GUID IDs are common both in relational and NoSQL databases. One can generate them in a distributed system and never produce a collision, which is nice. SQL Server supports GUIDs natively. Does this sound familiar?
Add one more detail, and your perspective might change: SQL Server creates a clustered index on the key column by default.
Now, stop for a moment and think. An application generates GUID values stored as new row keys in the SQL Server database table with the clustered index. The stage is set for the disaster that will only become apparent when the table grows large. And so, the correcting action will be equally costly.
This video will display the dangers of using GUID IDs with default SQL Server behavior and the order of steps to correct the issue once it has been added to the solution. You will also learn how to define your entities and never cause this problem when persisting them.

00:00 Intro
01:08 The Wrong Clustered Index
06:15 Turning to Nonclustered Index
12:15 The Correct New Entity
14:48 Conclusion

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
👨 About Me 👨
Hi, I’m Zoran, I have more than 20 years of experience as a software developer, architect, team lead, and more. I have been programming in C# since its inception in the early 2000s. Since 2017 I have started publishing professional video courses at Pluralsight and Udemy and by this point, there are over 100 hours of the highest-quality videos you can watch on those platforms. On my YouTube channel, you can find shorter video forms focused on clarifying practical issues in coding, design, and architecture of .NET applications.❤️
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️RIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content. Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.

#csharp #dotnet #sqlserver

свернуть