I personally don't understand why people try to use guid PKs everywhere and I hate them with a passion. They've probably seen Microsoft using them all over the place and have thought they should use them in all tables because it's smart. It's a brain fart.
If you need surrogate keys use int identity field (or the appropriate type, if you have billions of records, even though in that case I would probably question your database of choice hint, hint - that's a discussion for another time and only over beer). If you have varchar PKs use meaningful codes. I wouldn't think twice about getting rid of them. They might be appropriate in some cases (maybe you have some data that needs to interface with a external system?) but don't use them in all of your tables! -- 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/-/i_yHaE_3bPUJ. 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.
