• dan-572483 (10/17/2013)


    And here's where I'm at now. I wrote a package on my workstation where BIDS is installed that combines data from a text file and an access file and imports it successfully into a table in a SQL database. From what read I should be able to copy the dtsx file to a SQL Server that was installed without Integration Services checked and run the dtsx file via a SQL Agent job.

    After giving the SQL Agent account access to the folder with the dtsx, text and MDB files, then checking the "Use 32 but runtime" it reports failer, but now the error message reads

    To run a SSIS package outside of Business Intelligence Development Studio you must install Standard Edition of Integration Services or higher. End Error DTExec: The package execution returned DTSER_FAILURE (1).

    But when I do a select on the table, I see that the data rows from the text file were imported, but the Access data was not. Now I'm thinking is is an issue of recent 64-bit versions of SQL not playing will with older version Access files, which I've wrestled with before.

    Do you think the solution is

    1) Run SQL setup on the Server and check Integration Services (This is a failover cluster and I've read wornings from microsoft about this)?

    2) Dig deeper into the 64-bit SQL 2008/Access 2003 file issues?

    3) Run the dtsx package from SQL Agent on a 32-bit installation of SQL Server, tageting the 64-but instance where the database lives?

    Phil is right, the conclusion of my blog post could have been worded better. You definately need to install SSIS, but not necessarily SQL Server.

    Regarding Access: which provider are you using? JET OLEDB or ACE OLEDB? JET is only available in 32-bit, but ACE has also 64-bit providers available.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP