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.
I would like to request an admin change the thread title to:
SQL 2008 R2 <null> values transposed to zero value with SQLAzureMW (bcp.exe)
to help those searching for a related problem