![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a package that successfully exports to a text file from my desktop (where I originally developed it). I now want to run the package from the box where the SQL Server happens to reside (in case that's relevant) and cannot do it despite deleting the text object and rebuilding the "connection-to-text file output". It is while rebuilding that "transform data task", the black line between the db connection and export-text-file connection, that the problem becomes evident. When I click on the Destination tab, there is an execute button. From my desktop, after I click on the execute button, I can go to the transformation tab and all of the field have transmation lines/arrows going from the source side to the destination side. After I click on the execution button on the SQL Server box, I do not get the transformation lines/arrows. This is the case regardless of deleting both connection objects and starting from scratch. Is there some limitation concerning exporting to a text file from the box that holds the SQL Server? What could be the limiting factor here? Any help would be greatly appreciated. |
#3
| |||
| |||
|
|
It is ok to export from SQL Server box. Look in the file location for your text file (Connection Properties/File Name) and make sure it points to the correct directory that exists on the box that you run your DTS on. Regards, Ilona Shulman Senior Development Consultant, DBA SSE Inc http://www.sseinc.com "TomTait747" <TomTait747 (AT) discussions (DOT) microsoft.com> wrote in message news:BEF31A7D-F24F-40DF-82CB-EC55BD65F50F (AT) microsoft (DOT) com... I have a package that successfully exports to a text file from my desktop (where I originally developed it). I now want to run the package from the box where the SQL Server happens to reside (in case that's relevant) and cannot do it despite deleting the text object and rebuilding the "connection-to-text file output". It is while rebuilding that "transform data task", the black line between the db connection and export-text-file connection, that the problem becomes evident. When I click on the Destination tab, there is an execute button. From my desktop, after I click on the execute button, I can go to the transformation tab and all of the field have transmation lines/arrows going from the source side to the destination side. After I click on the execution button on the SQL Server box, I do not get the transformation lines/arrows. This is the case regardless of deleting both connection objects and starting from scratch. Is there some limitation concerning exporting to a text file from the box that holds the SQL Server? What could be the limiting factor here? Any help would be greatly appreciated. |
#4
| |||
| |||
|
|
I should have specified in my question that in re-creating the text connection, I did point in to a file local to the SQL Server. This is not the problem. "ilona" wrote: It is ok to export from SQL Server box. Look in the file location for your text file (Connection Properties/File Name) and make sure it points to the correct directory that exists on the box that you run your DTS on. Regards, Ilona Shulman Senior Development Consultant, DBA SSE Inc http://www.sseinc.com "TomTait747" <TomTait747 (AT) discussions (DOT) microsoft.com> wrote in message news:BEF31A7D-F24F-40DF-82CB-EC55BD65F50F (AT) microsoft (DOT) com... I have a package that successfully exports to a text file from my desktop (where I originally developed it). I now want to run the package from the box where the SQL Server happens to reside (in case that's relevant) and cannot do it despite deleting the text object and rebuilding the "connection-to-text file output". It is while rebuilding that "transform data task", the black line between the db connection and export-text-file connection, that the problem becomes evident. When I click on the Destination tab, there is an execute button. From my desktop, after I click on the execute button, I can go to the transformation tab and all of the field have transmation lines/arrows going from the source side to the destination side. After I click on the execution button on the SQL Server box, I do not get the transformation lines/arrows. This is the case regardless of deleting both connection objects and starting from scratch. Is there some limitation concerning exporting to a text file from the box that holds the SQL Server? What could be the limiting factor here? Any help would be greatly appreciated. |
![]() |
| Thread Tools | |
| Display Modes | |
| |