This is an update of a previous thread that had a SQL Query that was showing anomalies.

It was discovered that when using the open source utility SQLAzureMW to check for compatibility and publish a db to Azure, some null values were being transposed to a zero ('0') value. This is apparently a default setting in the bcp.exe utility. To override this you can use the -k parameter.

Reference: http://technet.microsoft.com/en-us/library/ms187887.aspx

• Edited by Javamarket Wednesday, December 25, 2013 5:57 PM

Hi Mark,

I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.

Regards,
Fanny Liu

If you have any feedback on our support, please click here.

Hello,

Thanks for your post and Glad to hear that the issue is resolved. Other community members could benefit from your sharing.

If you would like to, you can post the solution a new reply and mark it as answer. 
Thanks for your understanding and support.

Regards,
Fanny Liu

If you have any feedback on our support, please click here.