64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie > Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLSer...=12511
7

64-bit JET drivers or alternative?

Hi all -
I'm enountering the same problem many have previously reported.
Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
Data Flow Task in SSIS where the destination in an Excel spreadsheet
because there is no 64-bit JET driver for Excel.
Is anyone aware of a 64-bit driver now available or any 3rd party
options? Running the entire package in 32-bit mode is not a
possibility, so I can't use the DTExec workaround.
Any assistance would be appreciated --
Jamie :)> Running SQL Server 2005 x64 on Windows Server 2003, and I can't use a
> Data Flow Task in SSIS where the destination in an Excel spreadsheet
> because there is no 64-bit JET driver for Excel.
> Is anyone aware of a 64-bit driver now available or any 3rd party
> options? Running the entire package in 32-bit mode is not a
> possibility, so I can't use the DTExec workaround.
You can vote here:
Microsoft Connect > SQL Server: x64 Jet provider
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125117

64 bit(part II)

In a recent post, I've read that Jet Provider is only provided with 32-bit.

I wonder, is there any problem if you run a SSIS package 32-bit which read from Access and then call another SSIS package 64 bit? We've got quite 2000 dts which pulling data from MDB and within a time it'll disappear in favour 2005 environment .

Another question, what sort of Providers don't offer us 64-bit versions?

Any link or thought will be as usual welcomed

It will work - you can run first package in 32-bit mode, move data to staging table or flat file, then call second package in 64-bit mode and do further processing of the data.|||The msdaora drivers also don't function in 64bit. This is a bit of a hassle since the oracle provided 64bit drivers don't work correctly. ODBC is also a bit tricky since you have to create dsn's for 32 bit and 64 bit since the desinger is 32 and the runtime is 64.|||Thanks to both for the info provided.

64 bit(part II)

In a recent post, I've read that Jet Provider is only provided with 32-bit.

I wonder, is there any problem if you run a SSIS package 32-bit which read from Access and then call another SSIS package 64 bit? We've got quite 2000 dts which pulling data from MDB and within a time it'll disappear in favour 2005 environment .

Another question, what sort of Providers don't offer us 64-bit versions?

Any link or thought will be as usual welcomed

It will work - you can run first package in 32-bit mode, move data to staging table or flat file, then call second package in 64-bit mode and do further processing of the data.|||The msdaora drivers also don't function in 64bit. This is a bit of a hassle since the oracle provided 64bit drivers don't work correctly. ODBC is also a bit tricky since you have to create dsn's for 32 bit and 64 bit since the desinger is 32 and the runtime is 64.|||Thanks to both for the info provided.