dbTalk Databases Forums  

dts package transfer local file remote server idiosyncrasy

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


Discuss dts package transfer local file remote server idiosyncrasy in the microsoft.public.sqlserver.dts forum.



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

Default dts package transfer local file remote server idiosyncrasy - 11-05-2004 , 11:35 AM






Greetings,

I am going mad with DTS. I have two SQL Servers, one on my PC for test
purposes and the other at a remote location.

I developed a DTS package on my local PC and on the local SQL Server
which contains connections to the local SQL Server and some files on
the local PC for text import.

1) To play safe instead of writing the explicit name of the local sql
server I typed (local)\abc as the server name(abc is the instance
name) so that when I pulish the package to the remote server it
connects itself instead of the sql server on my pc (the instance names
are equivalent). However when I execute the package on the remote sql
server by connecting to the remote machine from my PC it insists on
connecting my PC. I read that it has to be scheduled, but this is
crazy, do I have to schedule packages everytime I run a test on the
production system?

2) When importing text files, I tentatively used the files on my own
PC hoping to fix the paths later when the package is transfered to the
remote machine. But again when I connect to the remote server I am
unable to list the files on the remote machine, the file dialog
insists on browsing the files on the local PC, unless BulkImport is
used (however I designed the whole package using regular file import).
Again I read that one should use UNC, but that's again crazy I need to
use some terminal services device to figure out where the file exists
on the remote machine.

Are there some clever solutions to these problems (other than using
UNCs, or completeley rewriting packages), or is this DTS brain dead?

Thanks

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

Default Re: dts package transfer local file remote server idiosyncrasy - 11-06-2004 , 02:15 AM






1. No you do not need to schedule a package to have it run

Execution
(http://www.sqldts.com/default.aspx?104)

When you say you publish it to the other server and then run it what do you
mean?

If you mean that you save it to server "SrvOverThere" and then go to EM
retrieve the package and press play in EM on your workstation then yes you
will be using your instance of the DB because DTS is running on your box
(Client Side)

2. Again DTS is client side so yes if you are opening the package on your
PC it looks at your PC.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Cagdas Ozgenc" <cagdasozgenc (AT) hotmail (DOT) com> wrote

Quote:
Greetings,

I am going mad with DTS. I have two SQL Servers, one on my PC for test
purposes and the other at a remote location.

I developed a DTS package on my local PC and on the local SQL Server
which contains connections to the local SQL Server and some files on
the local PC for text import.

1) To play safe instead of writing the explicit name of the local sql
server I typed (local)\abc as the server name(abc is the instance
name) so that when I pulish the package to the remote server it
connects itself instead of the sql server on my pc (the instance names
are equivalent). However when I execute the package on the remote sql
server by connecting to the remote machine from my PC it insists on
connecting my PC. I read that it has to be scheduled, but this is
crazy, do I have to schedule packages everytime I run a test on the
production system?

2) When importing text files, I tentatively used the files on my own
PC hoping to fix the paths later when the package is transfered to the
remote machine. But again when I connect to the remote server I am
unable to list the files on the remote machine, the file dialog
insists on browsing the files on the local PC, unless BulkImport is
used (however I designed the whole package using regular file import).
Again I read that one should use UNC, but that's again crazy I need to
use some terminal services device to figure out where the file exists
on the remote machine.

Are there some clever solutions to these problems (other than using
UNCs, or completeley rewriting packages), or is this DTS brain dead?

Thanks



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.