How to build an SSIS package when only 64 bit drivers are available?
I'm trying to build an SSIS package using the experimental Hive ODBC driver (http://social.technet.microsoft.com/wiki/contents/articles/6226.how-to-connect-excel-to-hadoop-on-azure-via-hiveodbc-en-us.aspx) However this only exists in 64 bit form. I can make some progress by creating a 32 bit DSN but when I try to get column metadata it falls over. Now this may be because the driver is experimental, but it's also quite possible that it's a 64 bit issue. Problem is, if I can't even build a package in the 32 bit environment, I can't test running it in a 64 bit one... So, hoping for some bright ideas on how I can build my package :)James Beresford @ www.bimonkey.com & @BI_Monkey SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
July 12th, 2012 2:51am

Try running the package using 64 bit runtime. you can set it in the projects property under debugging.-------------------------------------------------------- Surender Singh Bhadauria My Blog
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2012 3:00am

I can't build it, that's the problem. There's no 32 bit driver to use in the design of the package.James Beresford @ www.bimonkey.com & @BI_Monkey SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
July 12th, 2012 3:06am

Can you use the SSIS API to build the package first? (I'm no expert in the API.) Possibly EzAPI? Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 12:08pm

I could, but that's a fairly painful route... may be only option though. Was hoping for a cunning workaround. Think i'll have to raise a connect about getting a 64 bit dev environment.James Beresford @ www.bimonkey.com & @BI_Monkey SSIS / MSBI Consultant in Sydney, Australia SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
July 13th, 2012 5:23pm

Welcome back James, Are you trying to connect to Hadoop? I saw this article http://blogs.msdn.com/b/benjguin/archive/2012/03/07/hadoop-hive-odbc-ssis-sql-azure-sql-azure-reporting.aspx They do use the Hive ODBC driver within BIDS, thus it must be possible, is there a chance you did not get the right driver or something else? Besides, I wanted to try this to, but still waiting for the authorization to download the Hive ODBC.Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 10:48pm

Think i'll have to raise a connect about getting a 64 bit dev environment. That's an incredibly good idea! Share the link, I'll vote on it :)MCTS, MCITP - Please mark posts as answered where appropriate.
July 14th, 2012 2:09am

Hi James, I had a similar problem pulling data from a PostgreSQL database. Using some very helpful guidance from David Van De Sompele (http://blog.slalom.com/2011/03/14/connecting-to-a-postgresql-instance-using-sql-server-integration-services/), I wrote a query to cast my PostgreSQL data into a format that SSIS could interpret and I started my package from a package I saved when using the 64-bit SQL Server Import and Export Wizard. This is a "trick" I have used in the past ("trick" = starting my package through the Wizard and having the Wizard help me figure out the right settings for my connection manager). Although I do receive an architecture mismatch error when I'm in the development environment, I know that my connection manager is set up properly because I have already tested it through the Wizard and because my 64-bit ODBC driver works fine when I run/start debugging my package in the development environment. Maybe using 1) a query to cast your data and 2) the Import/Export Wizard might be a workaround for you too? Good luck! Karen
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 3:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics