It was an interesting article but it is an inordinate amount of work to transfer data to excel (32bit?). What would you do to export your data if the number of rows were greater than the excel 32 bit limitation? A good sample of test data would be exporting the Sales.Orderdetail table from AdventureWorks2012 (121,000+ rows) to excel 64 bit excel.

I am having issues (see error below) trying to load from excel 64 bit as the source from excel 64bit 2013 and I am using VS 2012 ultimate & SSDT. Another issue is that VS2012 Ultimate & SSDT are a 32bit ide. Very tough to do things in 64bit mode.

[Connection manager "SourceConnectionExcel"] Error: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode. Error code: 0x00000000.

An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".

My preference would be that SSIS should leverage either the 32 bit or 64 bit drivers transparently when creating a data flow.