dbTalk Databases Forums  

Export to Text File Fails from Server Box

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Export to Text File Fails from Server Box in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
TomTait747
 
Posts: n/a

Default Export to Text File Fails from Server Box - 10-08-2004 , 09:49 AM






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.

Reply With Quote
  #2  
Old   
ilona
 
Posts: n/a

Default Re: Export to Text File Fails from Server Box - 10-08-2004 , 09:57 AM






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

Quote:
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.



Reply With Quote
  #3  
Old   
TomTait747
 
Posts: n/a

Default Re: Export to Text File Fails from Server Box - 10-08-2004 , 11:23 AM



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:

Quote:
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.




Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Export to Text File Fails from Server Box - 10-09-2004 , 05:32 AM



DTS is a client side tool so.

The location of the text file has to be relevant to the place where you push
the button.

If you are on WKSTN1 and you pick up a package from SVR1 and press execute,
the package is executing on your box _NOT_ the server.

You should not have to change the package at all. You should also be using
UNC to specify the location of the text file.



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


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

Quote:
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.






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.