共用方式為

SSIS 64-bit setting

  • 發行項

These days, while working on SSIS 2005 (SQL Server Integration Services), I came across a porting issue. My SSIS packages ran fine on my 32-bit dev-box. But as soon as I ported them to 64-bit deployment machine, I started getting errors on connection managers, my connection managers could not connect to the respective data sources.

The thing to note here is that though the 64-bit editions of Microsoft SQL Server 2005 include Integration Services, some Integration Services features are available only in 32-bit versions, or have limitations on 64-bit computers. For one thing, the ODBC, OLEDB and drivers for Office 12 files have a different 64-bit version. So, if you have tested your SSIS packages (and the connection managers there-in) on a 32-bit machine, they might not behave similarly on 64-bit machine. 

For the SSIS packages that really don't make use of the 64-bit processor, the SSIS project property Run64BitRuntime can be set to False. This is a instruction to load 32-bit runtime environment rather than 64-bit, and your packages would still run without doing any plumbing work. The property can be found under SSIS Project Property Pages -> Configuration Properties -> Debugging.

You can find more information on 64-bit Integration Services considerations here

Comments

  • Anonymous
    December 10, 2007
    These days, while working on SSIS 2005 (SQL Server Integration Services), I came across a porting issue
  • Anonymous
    April 16, 2008
    The comment has been removed
  • Anonymous
    May 22, 2009
    Hi..I am facing same problem for SSIS on 64bit.Please help me to sort it out..Thanks in advance
  • Anonymous
    June 02, 2009
    The comment has been removed
  • Anonymous
    June 15, 2009
    GuysI think this may solve your problemhttp://ssis.trigonblue.com/Precompiledin64bit/tabid/522/Default.aspxor else you guys might have to install this fixhttp://support.microsoft.com/kb/931593.Hope this helps.EnjoyRegardsMoin.H
  • Anonymous
    September 29, 2009
    Unfortunately, gents - the Run64BitRuntime property ONLY applies to running packages interactively through BIDS.  If you're running your packages with DTExec or through SQL Agent, you need to do something different.  I recommend reading "64-bit Considerations for Integration Services": http://msdn.microsoft.com/en-us/library/ms141766.aspx
  • Anonymous
    August 10, 2010
    Thanks for the imformation above!  It helped with my situation perfectly. :S
  • Anonymous
    October 19, 2012
    Hi Amit,Thanks a lot , i was facing the same issue . after set Run64BitRuntime  to false realy its work