ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

How to Prevent Data Collisions in Databases

Updated on January 8, 2018
tamarawilhite profile image

Tamara Wilhite is a technical writer, industrial engineer, mother of two, and a published sci-fi and horror author.


Data collisions in databases occur when the same identifier is used for two different pieces or types of data. Data collisions can occur when two systems are being merged into one system or during data imports from one database into another.

When a data collision occurs, administrators or the software itself must decide which number and meta data are correct or if a new identifier must be assigned to one of the entries.

Data collisions become database errors when not resolved quickly.
Data collisions become database errors when not resolved quickly. | Source

How to Prevent Data Collisions

  • Assign different "seeds" used in databases to create the first part of a unique identifier. When systems are merged, all records will have different "seeds" and thus will not conflict.
  • Review the rules used for resolving data collisions. While the default solution is to take the newest record as the one to keep, some records should not be over-written but combined. This is especially true for medical records, insurance records and financial records.
  • Test the database merger prior to the production run and set up database monitoring tools to report data collisions. Review the data collisions that occur and whether the rules for resolving the data collision are appropriate for the database. While labor intensive, it prevents loss of information in the database merger. Testing also reduces the risk of having to migrate the data again because data collisions were not properly taken into account.
  • If you are going to upgrade a database from one application to another, verify that the naming scheme that will be used for new records won't create record identifiers that could conflict with old ones - or overwrite the existing files.
  • Compare the unique identifiers in two databases to be merged to look for potential data conflicts before the systems are merged. Combine the information in a single test database prior to go live. Alter records in at least one system if collisions are identified in a standardized way so that the newly renamed records don't end up with the same, new name.
  • Limit the ability to create a unique identifier not based upon the "seed". When users can select generic titles like "my report 2012" or "September sales pitch", the risk of data collisions increases.
  • If unique identifiers for records are tied to project names or file owners, ensure that combinations of various projects and user names cannot accidentally create a shared UID.
  • Add a letter or seed to imported vendor part numbers so their part numbers do not conflict with your own part numbers. Adding additional characters to the record identifiers of the incoming system makes them unique, preventing a data collision.
  • Use two or more sources of information to create a unique identifier. A unique identifier system based on a part number and cage code will rarely conflict compared to systems based on part numbers alone.
  • Assign unique identifiers based on a value that will rarely over-lap. A unique identifier system based on employee numbers will not conflict as often as a system based on first and last names. A unique identifier based on social security numbers will not collide as frequently as records based on initials and birth dates.
  • Ensure that new records being imported into the database don't conflict with existing record identifiers before you import the data en masse.


Submit a Comment

No comments yet.


This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

Show Details
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)