I built an SSIS package to pull data from YellowBricks Cloud dataware house using an ODBC connection and load it into SQL Server. On my local machine? Flawless. The DSN is configured, credentials are stored, everything runs without a hitch.
Then I deploy it to the server… and it falls apart.
The job fails with an AcquireConnection error.
I double-checked everything:
- Postgres Driver installed DSN , connecting.
- Created the exact same System DSN on the server (both 32-bit and 64-bit)
- Matched every detail—server, database, username, password, port
- Verified DSN names are identical everywhere
- Switched the Agent job between 32-bit and 64-bit runtime
- Built and tested in both Visual Studio 2017 and 2022.
- 32-bit checked in SQL agent job.
- Validate external metadata checked off.
Permissions shouldn’t be the issue—the SQL Agent job runs under a service account with sa privileges. Also considerign other jobs running fine.
My thoughts "Everything looks right. Everything should work. But on the server? It justwon’t connect"
Finally found 32 bit driver have limitations. Yes data limitation that the reason 64 bit drivers were created to handle big load. My source above 4.5 million rows and that 32-bit couldn’t handle the load.
That was the creating the issue. And just like that, it could finally breathe knowing how adjust the SSIS package to over the limitation.