![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
-----Original Message----- I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...4/09/21/175.as px . |
#3
| |||
| |||
|
|
I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...09/21/175.aspx |
#4
| |||
| |||
|
|
Have you tired looking at the file in hex? Sometimes the data can be dirty causing this error. |
|
-----Original Message----- I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...4/09/21/175.as px . |
#5
| |||
| |||
|
|
Have you applied the post-SP3 hotfix that would take you up to version 818? That fixed some DTS problems for me. |
|
Jonathan Levine <myfoo (AT) nospam (DOT) nospam> wrote: I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...09/21/175.aspx |
#6
| |||
| |||
|
|
Hi, Pete, "Peter A. Schott" wrote: Have you applied the post-SP3 hotfix that would take you up to version 818? That fixed some DTS problems for me. Thanks for the pointer. Do you remember which hotfix? I'm already at version 818. Regards, Jonathan Jonathan Levine <myfoo (AT) nospam (DOT) nospam> wrote: I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...09/21/175.aspx |
#7
| |||
| |||
|
|
Did you verify that your file is correct? I had issues with NUL entries in a UNIX file I was trying to import. I used a program called "Notepad2" from www.flos-freeware.ch to view the file and see all of the details. |
|
Jonathan Levine <myfoo (AT) nospam (DOT) nospam> wrote: I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...09/21/175.aspx |
#8
| |||
| |||
|
|
Peter, Thanks for your reply. "Peter A. Schott" wrote: Did you verify that your file is correct? I had issues with NUL entries in a UNIX file I was trying to import. I used a program called "Notepad2" from www.flos-freeware.ch to view the file and see all of the details. The file is definitely correct. It imports fine when I run the package. The only problem in the UI for the Text File object. -- Jonathan Jonathan Levine <myfoo (AT) nospam (DOT) nospam> wrote: I'm seeing a strangeness with the DTS designer in SQL Server 2000 SP3a. I'm trying to import a Unicode (UTF-16) file. The file has pretty long lines with tab delimiters between columns and dos-style line termination (CR-LF). It has 100 rows. If I do the following: 1. Open the DTS Package editor (in Enterprise Manager), 2. Drag out a Text File (Source) object, 3. Set the File name to my UTF-16 file 4. Click Properties 5. Select Delimited, Unicode, {CR}{LF} Row delimiter, no text qualifier 6. Click next then I OBSERVE: 1. An error message that says "Format error detected in rows 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 2. The "Specify Column Delimiter" is set to Tab (this is correct). Lines 2, 12, 14, 15, 17, 20, 24, 25, 26, 27, 34, 37, 39, 41, 42, 54, 55, 65, 84, 90 and 101 - 200 are blank. If I then hook this up (via Transform Data Task) and import, it appears to import correctly. If I go back to Text File Connection Properties/Column delimiter, I get the same error. WEIRDNESS: If I use DTS Wizard to Import the same file and save the package, then go in and edit the package created by DTS Wizard, I can edit the Text File object with no problem (that is, I can go to Text File Connection Properties/Column Delimiter and I get no error). Has anyone else seen this? Known bug? Thanks, Jonathan http://kerblog.com/earlyedition/arch...09/21/175.aspx |
#9
| |||
| |||
|
#10
| |||
| |||
|
|
Hi Jonathan and Pete, Thanks for your post. Based on my scope, this issue is similar to one known issue of us. However the troubleshooting steps might be so complex that not suitable to do it in the newsgroup. I would like to recommand you open a case with our Microsoft Product Support, it will be a free case if it is confirmed to be an known issue. Unfortuantely, based on my test, it was not fixed in sp3a or 818, which is to say no hotfix available now. Additionaly, I have tested it in SQL 2005 (Yukon) Beta 1 and found it was fixed. So if this has much business impact for you, you can contact Microsoft Product Support directly to discuss additional support options you may have available, by contacting us at 1-(800)936-5800 or by choosing one of the options listed at http://support.microsoft.com/default...d=sz;en-us;top. Thank you for your patience and corperation. If you have any questions or concerns, don't hesitate to let me know. We are here to be of assistance! Sincerely yours, Mingqing Cheng Online Partner Support Specialist Partner Support Group Microsoft Global Technical Support Center --------------------------------------------------------------- Introduction to Yukon! - http://www.microsoft.com/sql/yukon This posting is provided "as is" with no warranties and confers no rights. Please reply to newsgroups only, many thanks! |
![]() |
| Thread Tools | |
| Display Modes | |
| |