In the present era of code-first, you are most likely using some kind of an object-relational mapper like for instance Microsoft Entity Framework.Īnd the ORM will happily accommodate that C# type GUID as the identifier of your table's rows. And it's handy that its globally unique, thus a GUID is a great fit it's conceptually clever to have an identifier that's unique across tables, databases, servers and companies.Īmongst other things, integrating, synchronizing, importing and exporting between different locations can be much less painful and effective, simply by having one identifier to which is unique across different realms. A good ideaįor example in the Domain Driven Design-paradigm, it's often tutored that the application should set the logical identifier for an entity - not have some infrastructure like a storage layer decide that. But, there are pitfalls lurking in the complexities. But what about actual, real life practice? Where the boots hit the ground, in the professional arena? It's been very interesting to investigate and dissect this mystery, to peek into a few parts of implementation inside balanced search-trees as used in row-level indexes within the Microsoft SQL Server system. In the computer science classes I remember we learned about the theory of different kind of sorting and lookup trees, like binary trees, M-way trees and so forth. It still strikes me as feeling like some kind of magic. The performance of a modern relational database management system always blew me away. A simplified introduction to some theory and internal implementation details is helpful for understanding a problem that can easily slip under the radar, and which gets progressively worse in big tables with many inserts and/or updates to cluster index key. Not intended to explore the complex realm of database index design in full detail, but peeks progressively deeper under the hood to provide insight. Technical details are based solely upon Microsoft SQL Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |