“It is better to use UNIQUEIDENTIFIER type in tables when you use database mirroring” – is it myth?
What may be a reason to use unique primary key for mirroring purpose (single database mirroring case)?
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
No reason at all.
In mirroring only one database is in-use so there are no collision issues.
Is someone confusing this with replication where several sites are in-use and synch to each other? uniqueidentifier has a use here (and is mandatory in some cases) but still not as clustered index. And you use NOT FOR REPLICATION clauses on triggers and IDENTITY etc