Installation on Windows Server 2012

[paulwoll]

We would like to purchase your components to create an SSIS package to import data from an Oracle 8.1.7 database into a SQL Server 2014 database on a Windows Server 2012 R2 64-bit server and then create a SQL Agent job on the database to execute this package unattended at night.
1) Should this work fine?
2) Do we need to run in 32-bit mode?
3) Are there any installation gotchas or instructions?

[Shalex]

We would like to purchase your components to create an SSIS package to import data from an Oracle 8.1.7 database into a SQL Server 2014 database on a Windows Server 2012 R2 64-bit server and then create a SQL Agent job on the database to execute this package unattended at night.
1) Should this work fine?

Yes, this should.

2) Do we need to run in 32-bit mode?

The Devart assemblies are built with the /platform:anycpu option. So, you can use them in both x86 and x64 modes.

3) Are there any installation gotchas or instructions?

Trial: just install SSIS Data Flow Components to evaluate the product.

Adding the license (after purchase) in production:
* install Devart SSIS Data Flow Components for Oracle (the same installation like for trial) on both development and production workstations
* on the development computer, enter the license key via the License Info dialog of Devart Oracle Connection Manager Editor (in the Integration Services project). As a result, a license file will be generated
* now you need to copy the generated license file to the production computer. When you install SSIS Data Flow Components, it adds the LicenseFolder entry to the HKEY_LOCAL_MACHINE\SOFTWARE\Devart\SSIS Data Flow Components registry key for x86 operating system or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Devart\SSIS Data Flow Components registry key for x64 operating system. This key specifies the folder where license information must reside. By default this is the C:\ProgramData\Devart\SSIS Data Flow\License folder. Copy the SSISOracle.lic file from the development computer to this folder on the production computer