sql server - Import Excel To SQL -

hello have little issue i'm unable resolve. here context:

i have 64-bits sql server 2014 instance on computer , 32-bits office installation (on component installed excel, no word, no office tools, no office shared features...). try import data stored in .xls file on network drive on daily basis, i'm unable find right way it. here's why:

i try command:

insert bbimport         select *         opendatasource('microsoft.jet.oledb.4.0','data source=w:\..\aaa.xls;extended properties=''''excel 8.0;hdr=yes''''')...[sheet5] 

after resolving permission issues, got error:

"the 32-bit ole db provider "microsoft.jet.oledb.12.0" cannot loaded in-process on 64-bit sql server."

note: tried microsoft.ace.oledb.12.0, same error.

i try install microsoft ace 64-bits, not compatible 32-bits office installation -_-...

---

however succeed import data using import wizard of sql specifying followings:

data source: microsoft excel | excel version: microsoft excel 97-2003 (or 2007 both worked) | destination: sql server native client 11.0

since worked, created ssis package , import integration services catalog new project. when try right-click/execute, sql server management studio stops working , errors in event viewer:

1. application: ssms.exe framework version: v4.0.30319 description: process terminated due unhandled exception. exception info: system.io.filenotfoundexception stack:    @ microsoft.sqlserver.integrationservices.uitasks.executetask.showreport()    @ system.threading.threadhelper.threadstart_context(system.object)    @ system.threading.executioncontext.runinternal(system.threading.executioncontext, system.threading.contextcallback, system.object, boolean)    @ system.threading.executioncontext.run(system.threading.executioncontext, system.threading.contextcallback, system.object, boolean)    @ system.threading.executioncontext.run(system.threading.executioncontext, system.threading.contextcallback, system.object)    @ system.threading.threadhelper.threadstart() 2. faulting application name: ssms.exe, version: 2014.120.2000.8, time stamp: 0x5306c06d faulting module name: kernelbase.dll, version: 6.1.7601.18409, time stamp: 0x53159a86 exception code: 0xe0434352 fault offset: 0x0000c42d faulting process id: 0x8d8 faulting application start time: 0x01d06c81bcb45ec2 faulting application path: c:\program files (x86)\microsoft sql server\120\tools\binn\managementstudio\ssms.exe faulting module path: c:\windows\syswow64\kernelbase.dll report id: 84f7630f-d87a-11e4-a40a-005056ae5914  3. fault bucket , type 0 event name: clr20r3 response: not available cab id: 0 problem signature: p1: ssms.exe p2: 2014.120.2000.8 p3: 5306c06d p4: mscorlib p5: 4.0.30319.18063 p6: 526766b5 p7: 170b p8: 14 p9: system.io.filenotfoundexception p10:  attached files: these files may available here: c:\users\administrator.casgrain\appdata\local\microsoft\windows\wer\reportarchive\appcrash_ssms.exe_5c1853936685e7ed85eece7cc3339e468fa8b7_0aee4fe2 analysis symbol:  rechecking solution: 0 report id: 84f7630f-d87a-11e4-a40a-005056ae5914 

i google errors, did not find fix.

and when try execute via stored procedure running code, nothing happens (no results, no message , table still empty).

declare @execution_id bigint exec [ssisdb].[catalog].[create_execution] @package_name=n'bbimport2.dtsx', @execution_id=@execution_id output, @folder_name=n'test', @project_name=n'bbimport2', @use32bitruntime=false, @reference_id=null  exec [ssisdb].[catalog].[start_execution] @execution_id go 

do have idea me?

i solved issue uninstalling office 32b , installing office 64b. after lot of test, problem either compatibility between sql(64) , office(32) or file wasn't import since excel had lot of vlookup function search other sheets , sheets needed run bdp function (bloomberg function) filled.

i run command import xls file:

insert main select *      opendatasource('microsoft.ace.oledb.12.0','data source=[path\filename.xls];extended properties=excel 8.0')...[tablename] 

i still can't understand why running wizard , vs2013 when run package manually, not when importing package ssis catalog or when executing query directly. it's working now. guess it's thing matters...