fiogf49gjkf0d You should be creating new records as you move them across, and using the provider to get yourself a new id. This will automatically update the SiteKeys.
Whatever your import routine is, I would scrap it and change it to the above model. Remove any records already brought across and start again.
You could fix this manually you could get max(id) from table, add one 'hex' value to it and whack that value in sitekeys. Unsupported of course. Best course is to remove the data and start again properly.
Another approach is as you move the data across change the four character site key part of your id to something like 'QAXX'. This will mean you wont get a viloation with existing data, and you wont get a primary key violation when new records are added. You will need to be careful if you try to move the same record over again though (which to be fair you would have anyway). |