Are you awared of CpBT? When you have such requirement in your application Identity PK are the last choise. Generally if i cannot use guid.comb i then use HILO instead, but never identity int.
El martes, 27 de noviembre de 2012 16:13:15 UTC-3, Sam Jonesom escribió: > > Hello All! > > I do not mean to beat a dead horse, but the blog posts and articles I have > read on this are 3 or more years old, and refer to NH 2.x. > > Why I am asking: > We have a large SQL DB. We are finding that the use of GUIDs as primary > keys and clustered indexes is creating LARGE indexes. Very large (many GB). > Our research has clearly shown that using an int / identity as a primary > key will dramatically cut our db size (like by %50), and simultaneously > give our SQL server a huge perf boost (like over %100). > > (You can see one write up on this topic here: > http://www.sqlskills.com/BLOGS/KIMBERLY/post/GUIDs-as-PRIMARY-KEYs-andor-the-clustering-key.aspx) > > So, I have started an internal process to evaluate migrating our .NET-4 / > NH-3.2 application to use SQL Server Identity columns as primary keys. > > Please advise as to any write ups, success/horror stories, etc. > > Thank you very much! > > > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/XixMEgAnVmsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
