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 |
|
KLang23
Posting Yak Master
115 Posts |
 Posted - 2006-04-17 : 12:51:42
|
| Hello,I've got a simple SSIS package that imports data from one system (SQL2K) to another (SQL2K5). Each data source is using SQL Server authentication (legacy). The package runs fine when executed manually, but fails when executed as a job (unable to connect to the foreign data source - very poor logging messages if I may say so). I suspect of course that this has something to do with the SQLServerAgent account on the calling server, but I would like a confirmation. Anybody have any experience with this?Thanks. |
|
|
ewebb02
Starting Member
6 Posts |
Posted - 2006-04-20 : 10:29:38
|
| Welcome to my world. What I had to do to get it to work is assign the SQL Server Agent's job owner using a domain account that had access to both SQL Servers (with appropriate permissions). I'm still looking to find out the best way to handle all of this, but that's the solution that worked for me for the time being.I found some help using Google and copy/pasting the error message directly in the search engine. But, I will certainly agree that the error reporting is very lacking; but at the same time it's more error reporting than traditional DTS. |
 |
|
|
|
|
|
SSIS launched from a job