January 6, 2009 at 12:53 pm
We're having difficulty importing (into our batch processes) the exports from a 2005 DB export file. Source data in SQL 2000 destination is flat file. If you use DTS (2000) to export the file the file works fine in the batch process. If you use SQL 2005 export wizard or SSIS data flow with flat file destination, the file doesn't work. Looking at the file in hex editor there are extra characters (like a space holder) in the file.
Has anyone come across this before or had the same issue?
Any help greatly appreciated,
Sabrina
January 6, 2009 at 6:07 pm
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
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 7, 2009 at 7:57 am
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
January 7, 2009 at 9:56 am
00 is NULL - whether that helps you at all is another matter 🙂
Phil
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply