Integrity of export file

  • Sounds weird. So the source data is just a query on a SQL Server database?

    Are you using a hex editor because the output files look the same in Notepad? I was wondering exactly what these spurious characters are. What is a 'space holder', by the way?

    When you perform the export using DTS, are you using exactly the same database? Same codepage?

    Phil


  • Hi Phil,

    Thanks for responding. It is curious indeed. For testing I did a select * from . Its a table that has 2 columns and rows, keepin it simple.

    The code page is 1252, but since the source is the same for both exports I really didn't think it mattered. I looked at it in the hex editor because to the naked eye the export files look exactly the same whether you export it through 2000 (DTS)or 2005 (SSIS or Import/Export wizard).

    In hex the correct format looks like:

    M1..90862 M1..98765

    In hex the strange format looks like:

    M.1....9.0.8.6.2...........M.1.....9.8.7.6.5

    The spurious character hex value to which you refer is 00.

    Testing a theory and I'll post results if it pans out. In the meantime if something comes to mind, your assistance is greatly appreciated.

    Sabrina

  • 00 is NULL - whether that helps you at all is another matter 🙂

    Phil


Viewing 3 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply