![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |