December 21, 2013 at 8:37 am
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
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
December 21, 2013 at 9:29 am
[updated]
December 21, 2013 at 10:34 am
[updated]
December 21, 2013 at 10:48 am
[updated]
December 21, 2013 at 5:14 pm
[updated]
December 21, 2013 at 5:50 pm
I know no one came to your rescue but I sure do appreciate the "log" of the problem. It'll help other folks, I'm sure.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply