Since we have applied sp3a to the sql servers we have been experiencing
problems with dts packages importing/exporting text files. (Used to work fine
on SP1, not sure about sp2) The issue is with the number of columns being
imported/export. Here is the scenario: Exporting data from a table with 45
columns. Most of the columns are tinyint or sincle characters. Specify the
destination to be a text file (type doesn't matter delimeted, fixed). Create
a data transform task between SQL server and the destination file. Now for
the fun part. We select the table with 45 columns in the source tab of the
transform data task and hit preview. Looks goods. Everything shows up fine.
Go to the destination tab and it automatically shows all the columns to be
defined. You can even hit the populate from source button with no problems.
Now when we click on execute to save the destination columns and the list is
blank on the transform data task's destination tab. If we click on the
define columns again Enterprise manager crashes and closes. I have tried
this of different table with the same result. Any time there appears to be
more than 18 columns dts blows chunks.

This happens the same on several different servers running windows server
2003 and windows 2000 Advanced server with current services packs. As I
mentioned before all of our sql servers are SQL 2000 sp3a? Any ideas?

Thanks

The column character count of your 18 columns is probably less than 255.
Add another column and you go over 255 characters causing the crash.
This is an issue, and I believe it was addressed in SP3. Do you have SP3
Installed?

I encountered this before, and when I applied SP3 it fixed it, but the
company I work for currently uses a product to push software to desktops,
and would revert the SP3 I applied back to no service packs. So when ever I
rebooted, I got the errors again, and had to reapply the SP. I've fixed it
since so that doesn't happen any more, but was pretty annoying for awhile.

--
Simon Worth


"Ken" <Ken (AT) discussions (DOT) microsoft.com> wrote

This is a known issue with SP3

http://support.microsoft.com/default...b;en-us;814113



"Ken" <Ken (AT) discussions (DOT) microsoft.com> wrote

Thanks! The updated DTSUI.dll in Security Patch MS03-031 did the trick.

"Allan Mitchell" wrote: