Are there problems with using GUID's as indexed fields in SQL Server? -


i've read lot of articles mention using guid clustered indexed (or primary key) in sql server cause performance issues.

however, due design decisions, need field guid in each line of 1 table.

if define primary key of table autoincrement integer, , add guid normal column indexed, have performance issues similar having guid primary key?

edit: side note, know guid primary key bad idea, asking if have performance issues if set indexed (non clustered) field

what type of index want use guid field? clustered? unique? if unique, guid not differ other unique field. can use without doubt. in case of clustered index affect performance. can use sequential guid. can solve performance issues. generating of guid on client-side can improve performance.


Comments

Popular posts from this blog

Spring Boot + JPA + Hibernate: Unable to locate persister -

go - Golang: panic: runtime error: invalid memory address or nil pointer dereference using bufio.Scanner -

c - double free or corruption (fasttop) -