I've been struggling with an SSIS package for a while now.
Any time I run it in VS, it runs just fine and loads my data as I'd expect. However, when I deploy the code to my SQL Server and run it, it fails, complaining about missing column delimiters.
I'm thinking that maybe there's something wrong with the deployment (even though I've redeployed a few times) and it's Just Borked™.
I guess I'm gonna right-click Delete the package from the server and try again.
No, I don't know why I told y'all this, I guess I just needed to say it out loud.
Dear SSMS.
Why must you crash every time I try to dock the Object Explorer to the left edge of your window?
With love,
A concerned, but increasingly annoyed user
I'm glad I decided to delete the package and redeploy it. In the process, I realized what an id10t I've been...
I finally realized that I could deploy multiple projects within 1 folder in the SSISDB catalog. So, I started modifying my deployments to do that. This will allow me to have just one set of environments, instead of having to create a new Dev and Prod for every package I deploy.
I call a Stored Procedure from my VBA code to launch the package. (You can see where this is heading, right?)
I forgot to update the stored proc to call the package from the new location.
All this time, I've been beating my head on my desk trying to figure out why my fixes worked in VS but not when I call them from VBA and it's because I haven't been calling the fixed code from VBA!!!!!
