Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
floker
Starting Member
6 Posts |
 Posted - 2009-12-02 : 05:23:23
|
| For my work I'm using two servers, one SQL server and one Application server. Via the application server I'm using the enterprise manager to launch some DTS which use batch files. It used to work fine but now that we have migrated the servers it's not working anymore. The problem is that when I run the DTS via the Application server, the DTS searches for the batch file on the application server instead of the SQL server. Does anyone know how to solve this? It used to work fine. So when I run the DTS from the Application server (which is just a connection to the SQL server) the DTS should search for the batch file on the SQL server as well and not on the application server. |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-12-02 : 08:23:55
|
| need to include entire unc path to batch file\\servername\sharename\yourfile.cmdNote that DTS is a client application, and as such, everything will be executed from the context of the machine executing the package. |
 |
|
|
floker
Starting Member
6 Posts |
Posted - 2009-12-03 : 06:29:07
|
quote:
Originally posted by russell
need to include entire unc path to batch file\\servername\sharename\yourfile.cmdNote that DTS is a client application, and as such, everything will be executed from the context of the machine executing the package.
Thank you, that's what I needed to know! |
|
|
|
|
|
|
DTS fails after migration