Home > IT Answers > Business Intelligence > Spaces in Linux is getting Interpreted as ‘@’
Bakash
0 pts.
 Spaces in Linux is getting Interpreted as ‘@’
Database Management Systems, Linux, SQL Server
Hi All Need some help. I use the BCP out command to transmit data from SQL Server database table and send it to flat files. The spaces (varchar datatype in table) gets transmitted as spaces only. When I use Linux command to get these files, out of 20,000 spaces , 1 space got interpreted as '@'. Can you please tell me the reason behind this peculiar behaviour and how do I prevent it?

Software/Hardware used:
ASKED: May 16, 2005  1:23 PM
UPDATED: May 16, 2005  9:12 PM
RELATED QUESTIONS
Answer Wiki:
What I understand you are saying is that out of 20,000 spaces in some table you get 19,999 and one @. Need schema and representative info to help further. Have you tested this in Windows? Have you confirmed that there is really no @ in your data? WHERE COLUMNNAME LIKE '%@%' Cheers, Ben
Last Wiki Answer Submitted:  May 16, 2005  1:36 pm  by  BenjiT   0 pts.
All Answer Wiki Contributors:  BenjiT   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Thanks for the quick response.

Correct, 19,999 are spaces and one ‘@’.

Info:
ColumnName varchar(25) Null

Yes, I ve tried it out in Windows as well as Unix. Did not encounter any such behaviour.

And yes its confirmed that there’s no ‘@’ in the data.

Thanks Again

Bakash
 0 pts.
 

Space ASCII 32 – Hex 20 versus @ ASCII 64 – Hex 40 or
0010 0000 versus 0100 0000.
1st question is it in the same place in the transferred file every time?
2nd – Are the frame sizes set the same on both machines?

If it is about the same place every time you have found a coincidence bug. You are getting a 1 bit transposition in a 40,000 nibble transfer. At one point in the transfer between Windows and Linux the difference in TCP/IP stacks combines with the different block sizes to transpose one bit and it must be occuring at a checksum boundary since you don’t report any communication errors.

Congratulations you found a bug, bad news I don’t know how to prevent it. I will watch expectantly for the solution.

Which version of Linux, Kernel, patches, etc.

Howard2nd
 30 pts.