Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / probability of GUID Co...
Microsoft Dynamics CRM (Archived)

probability of GUID Collision while Data Migration in MS CRM 2013

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi guys,

We are doing CRM data migration in order to keep two CRM Systems in Sync. And removing history data from Primary CRM. Target CRM is been created by taking Source as base. Now while we migrate the data we keep guids of record, same in order to maintain data integrity. This solution expects that in target systems that GUID must be available to assign to new record. There are no new records created directly in target system except Emails, that too very low in number. But apart from that there are ways in which system creates its guids, e.g when we move newly created entity to target solution using Solution it will not maintain the GUID of entity and attributes and will create its own, since we do not have control on this. Also some of the records which are created internally will  also get created by platform and assigned a new GUID. Now if we do not  have control over guid creation in target system(Although number is very small), i fear of the situation where Source System has guid which target has already consumed!! And at time of data migration it will give errors.

My Question is there any possibility that above can happen? because if that happens to us whole migration solution will loose its value.

*This post is locked for comments

  • ashlega Profile Picture
    ashlega 34,475 on at
    RE: probability of GUID Collision while Data Migration in MS CRM 2013

    It does not necessarily mean that it's unique per db - contacts and accounts are very "related" entities (customers etc), but it might work for custom entities. Like I said, it's not clear what will happen. Still, I have a feeling you are overthinking this. Basically, this is how all data migration is done in Dynamics, and it has not caused issues so far.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: probability of GUID Collision while Data Migration in MS CRM 2013

    Thank you Aileen, we are using kingswaysoft and it preserves the GUID from source to destination. But there are situations in which guid creation in target organization will not be in our control e.g. if i create new entity in Source and move it though Solution it will create a new entity record and attribute records with autogenerated guids by CRM DB. My fear is if in future same guid is used by some record in Source , than at time of migration it will give error

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: probability of GUID Collision while Data Migration in MS CRM 2013

    Thanks, but i have checked that too,  for CRM i have created contact with a perticular GUID and used the same GUID to create account record and it gave me error, that means its unique per DB atleast

  • Aileen Gusni Profile Picture
    Aileen Gusni 44,522 on at
    RE: probability of GUID Collision while Data Migration in MS CRM 2013

    Hi Manish,

    It will be very less if we talk about the probability.

    If you migrate the records with the same GUID from the source an you are using the Configuration Migration utility by Microsoft, it is safe, that's why it is being used.

    You can refer to this blog that it is common to export out the same GUID between source and destination/target system

    crmbusiness.wordpress.com/.../crm-2016-the-importance-of-keeping-the-same-guids-between-crm-instances

    Also, if that even happen, it will stop and saying 'Cannot insert duplicate key' which will be very least likely to happen. Thanks.

  • Suggested answer
    ashlega Profile Picture
    ashlega 34,475 on at
    RE: probability of GUID Collision while Data Migration in MS CRM 2013

    Hi Manish,

     it's a good question, but I don't think there can be an absolute guarantee that there will be no identical guids in those two databases. That said, the process of Guid generation is random enough for the most of us not to even think of this issue until it happens (and I have not heard of this happening to anyone)

     Besides, technically Guids have to be unique within the entity (it's a primary key on the SQL level). Although, it's not quite clear what will happen if there is the same guid assigned to the records of different entity types. Still, that reduces the risk even further.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans