SQL is delicious (5/21/2014)

---

Koen Verbeeck (5/20/2014)

---

SQL is delicious (5/1/2014)

---

brad.mccollum (5/1/2014)

To give you a little more insight as to the general nature of the SSIS package, it will basically be looping through a folder once nightly to determine if customers have uploaded Excel files into this location. The SSIS job will then go through each of the Excel files found and do ETL on them & create new individual Excel files with the original data transformed into a consistent layout preferred by my client so all of the files end up looking the same aside from of course different data in each file. Most of the Excel files coming in from customers are going to be from fairly recent version of Excel, so I've installed the Microsoft Access Database Engine 2010 Redistributable on my development environment's virtual machine (the 32-bit version... AccessDatabaseEngine.exe).

Others here know far more about this than I do, but here is a suggestion:

Make sure the packages using Excel sources/destinations are configured to run AS 32-bit packages. If you're using Excel as a source or destination then you have to do this; I've never seen a workaround for it. I think there are a couple of others that require a 32-bit environment too, but most don't.

If I'm wrong I am 100% positive someone here will pick it up. 😀

I'll pick it up.

There is a 64-bit ACE OLE DB provider, so you can run a package with Excel source/destination perfectly on a 64-bit machine.

Really? Sweet! See, you learn something new every day. Hopefully that's not the only thing I learn today as it's not even 9am yet. 😀