1
Vote

Data Difference after export

description

I noticed a data discrepancy after I migrated from SQL 2008 r2 to windows SQL azure. The error is with primary key 2099. It did have three dots at the end of the search_code field and after the migration it only has one. I had a unique key on this field and it picked it up as an error. Is it a collation thing? Is it bcp?
 
Original Data
order_id search_code
2095 10138
2096 10138*
2097 10138.
2098 10138..
2099 10138…

Data after exported into SQL Azure
order_id search_code
2095 10138
2096 10138*
2097 10138.
2098 10138..
2099 10138.
 
Any help would be appreciated. I am a little worried if my data isn't copied over exactly as it was.
 
Matt.

comments

ghuey wrote Feb 22, 2012 at 3:04 PM

Taking offline so that we can resolve.

Thanks Matt.

ghuey wrote Feb 22, 2012 at 3:12 PM

As a side note, I use BCP to export and inport the data. What you can do it you want is truncate the table and just BCP the data up by hand. Also, you can play with the BCP switches in SQLAzureMW.exe.config file (look for BCPArgsIn and BCPArgsOut. For example, you might change the -n to -c. If you use the -c switch, then you can edit the bcp output file and see the data in text and look and see if the data is correct there. Let me know how it goes.