April 6, 2016 at 10:45 am
I can't figure out if there is a 32bit dtexec utility for SQL 2012 or not. Google keeps sending me to posts about SQL 2008.
Does anyone know if SQL 2012 fix the Excel file problem that requires the 32-bit version of the dtexec or not?
April 6, 2016 at 3:20 pm
The 32bit version of DTExec still gets installed with SQL 2012 and for a default install can be found here:
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTExec.exe
Not sure about the Excel issue.
April 7, 2016 at 4:28 am
JeremyE (4/6/2016)
The 32bit version of DTExec still gets installed with SQL 2012 and for a default install can be found here:C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTExec.exe
Ummm, it doesn't appear to have gotten installed with our SQL 2012. We had an SP1 msi install. No 32bit came with it. That's why I'm asking.
And we've applied SP2 to the server, which also didn't install the 32bit.
I'm hesitant to install the 2k8 version of the dtexec utility because I'm sure there had to be an upgrade of it along the way (if it's truly separate) but I can't seem to find one.
April 29, 2016 at 6:21 am
I think I found what I needed. I will know when I've tested it.
From BOL on Integration Services job steps:
Use 32 bit runtime
Indicate whether to run the package using the 32-bit version of the dtexec utility on a 64-bit computer that has the 64-bit version of SQL Server and SQL Server Agent installed.
You may need to run the package using the 32-bit version of dtexec if for example your package uses a native OLE DB provider that is not available in a 64-bit version. For more information, see 64 bit Considerations for Integration Services.
By default, when you select the SQL Server Integration Services Package job step type, SQL Server Agent runs the package using the version of the dtexec utility that is automatically invoked by the system. The system invokes either the 32-bit or 64-bit version of the utility depending on the computer processor, and the version of SQL Server and SQL Server Agent that is running on the computer.
So apparently I don't need to install anything extra (if I'm reading this correctly). I can just tell SQL that this needs 32-bit runtime instead of 64-bit.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply