How to execute ssis package developed in 34 bits with a database source from 64 bits

Question

How to execute ssis package developed in 34 bits with a database source from 64 bits

darlenehl 77733

Grasshopper

Points: 18
More actions
November 3, 2010 at 5:46 pm

#143332

I developed a ssis project into 32 bits server, my package runs perfectly in my project, even if I create the Package for SQL server 2005 it's run. This package has a connection to a database into 64 bits, I mean my Package Project is into a 32 bits server and my database into a 64 bits server.
When I create a job into 32 bits server this job fails.
Plese someone help me
Thanks in advance
dhl

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

tmitchelar Hall of Fame Points: 3391 More actions · Answer 1

There is a solution property called Run64BitRuntime. You can set it to false to run in 32 bit mode. Note - I wrote 32 bit, not 34 🙂

darlenehl 77733 Grasshopper Points: 18 More actions · Answer 2

darlenehl 77733

Grasshopper

Points: 18

November 3, 2010 at 6:31 pm

#1246350

:hehe: Ouch! You are rigth, 32 bits :O

Thanks

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 3

tmitchelar (11/3/2010)
There is a solution property called Run64BitRuntime. You can set it to false to run in 32 bit mode. Note - I wrote 32 bit, not 34 🙂

That is a debug property.. It has no effect at runtime outside of BIDS..

I was a little unclear what you meant by "This package has a connection to a database into 64 bits". Do you mean that the destination of one of the connections is a 64-bit server? If so you don't need to care..

By-and-large unless your connections require 32-bit libraries your package will run on 32 or 64 bit without change. Where most of us run into problems is using the jet drivers which used to require us to run the package in 32-bit mode. Jet drivers were typically used to access Excel files. There is a new package that has 64-bit jet drivers.

Could you clarify what you exactly you meant above?

CEWII

tmitchelar Hall of Fame Points: 3391 More actions · Answer 4

Elliott Whitlow (11/11/2010)
tmitchelar (11/3/2010)
There is a solution property called Run64BitRuntime. You can set it to false to run in 32 bit mode. Note - I wrote 32 bit, not 34 🙂
That is a debug property.. It has no effect at runtime outside of BIDS..
I was a little unclear what you meant by "This package has a connection to a database into 64 bits". Do you mean that the destination of one of the connections is a 64-bit server? If so you don't need to care..
By-and-large unless your connections require 32-bit libraries your package will run on 32 or 64 bit without change. Where most of us run into problems is using the jet drivers which used to require us to run the package in 32-bit mode. Jet drivers were typically used to access Excel files. There is a new package that has 64-bit jet drivers.
Could you clarify what you exactly you meant above?
CEWII

Thank you for the correction Elliott. I read through his question too fast. :blush:

I wonder if it could also be a connection to Oracle that is causing the problems between BIDS and Job Agent. I know that BIDS requires 32 bit provider for Oracle, and Job Agent requires the 64 bit provider when on a 64 bit OS...I've definitely had some problems in the past in this regard.

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 5

tmitchelar (11/11/2010)
Elliott Whitlow (11/11/2010)
tmitchelar (11/3/2010)
There is a solution property called Run64BitRuntime. You can set it to false to run in 32 bit mode. Note - I wrote 32 bit, not 34 🙂
That is a debug property.. It has no effect at runtime outside of BIDS..
I was a little unclear what you meant by "This package has a connection to a database into 64 bits". Do you mean that the destination of one of the connections is a 64-bit server? If so you don't need to care..
By-and-large unless your connections require 32-bit libraries your package will run on 32 or 64 bit without change. Where most of us run into problems is using the jet drivers which used to require us to run the package in 32-bit mode. Jet drivers were typically used to access Excel files. There is a new package that has 64-bit jet drivers.
Could you clarify what you exactly you meant above?
CEWII
Thank you for the correction Elliott. I read through his question too fast. :blush:
I wonder if it could also be a connection to Oracle that is causing the problems between BIDS and Job Agent. I know that BIDS requires 32 bit provider for Oracle, and Job Agent requires the 64 bit provider when on a 64 bit OS...I've definitely had some problems in the past in this regard.

This is generally true, in sql 2008 you can select a checkbox that says to run the package as 32-bits, in 2005 you have to do it manually.. In most cases I have installed both the 32 and 64-bit providers where available. I prefer to run things with the 64-bit runtime whenever I can as I almost always get better performance. I am still a little fuzzy on what the OP meant and would love to see a clarification.

CEWII