I've been given the "honor" of being the guinea pig with a new installation
of SQL 2005 to replace an aging database.

The task is simple. I need to retrieve a table of ~12M rows from a remote
TERADATA server and store it in a local table. I've built the package in
development studio and it work perfectly in debug mode.

Now here comes the rub. I install the package as a SQL Job (same box) and
try to execute manually. After it spins a few seconds I get the following
error.

-------------
The AcquireConnection method call to the connection manager
"xx.xx.xx.xx.visions" failed with error code 0xC0202009.
-------------

What I can't understand is why it works fine under development studio but
fails under SSIS on the same machine.

Thanks in advance...

I dont know the answer to your problem, but I have found it simple to create
a linked server to the remote server via EM, then use a simple "select into"
statement to move the data.

--run from local server
select <column names> into <local table> from <server>.<db>.<owner>.<table
name>



"CG in AL" wrote:

If you look up that code, it means "An OLE DB error has occurred. Error
code: ...". So what is the OLE-DB error? Have you got logging turned on for
the package?

Security issues are always favourite for scheduled packages.

Some more links that may help going forward -

An SSIS package does not run when you call the SSIS package from a SQL
Server Agent job step
(http://support.microsoft.com/kb/918760)

Scheduled Packages
(http://wiki.sqlis.com/default.aspx/S...dPackages.html)


"CG in AL" <CG in AL (AT) discussions (DOT) microsoft.com> wrote