January 16, 2009 at 3:15 am
i have encountered an sissue in 64-Bit version of a script task. On further investigating, i have found that there is a property for a project
Run64BitRuntime is required to be set to false.
My question is:
if iam intending to install the package in the 64 bit machine and 64-Bit version of Integration Services is installed, will setting the it to false and make it 32 bit work?
To make it simpler, if the a package with 64Bitruntime is set false, work in a 64 bit environment?
January 16, 2009 at 7:12 am
nabajyoti.b (1/16/2009)
i have encountered an sissue in 64-Bit version of a script task. On further investigating, i have found that there is a property for a projectRun64BitRuntime is required to be set to false.
My question is:
if iam intending to install the package in the 64 bit machine and 64-Bit version of Integration Services is installed, will setting the it to false and make it 32 bit work?
To make it simpler, if the a package with 64Bitruntime is set false, work in a 64 bit environment?
This property controls the execution behavior only inside Visual Studio. When executing under SQL Job Agent, you decide what runtime to use by selecting DTEXEC from different location - "Program Files" (64bit) or "Program Files (x86)" (32bit). In SQL 2008, there is a new option, which allows you to specify if you want to use 32bit mode. In SQL 2005, you have to use OS ExecProcess step instead and specify the DTEXEC and the appropriate parameters.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply