October 8, 2025 at 4:43 pm
hi, just to get this part out of the way, if my intended target for an ssis project is 2019, i always change the project over to 2019 before starting whatever i'm going to do. Locally and on my vm i work in vs 2022.
It might be just as of late, when i import an ssis project into vs on my local, vs complains about the provider not being available. It seems to change the provider over to something really generic looking. My response in simpler projects is to switch it over to the ms sql provider and all is usually fine.
but today as i wanted to add a pkg to a more complicated project i imported from our 2019 dw server, i got concerned that if i went to deploy the modified project back to that server, that provider issue would remain/become broken on all the other pkgs in the project even though i wasnt doing anything with them. i became so concerned that instead of trying to add the new pkg to that project i made a different project with only that pkg in it. on my 2022 vm i also run vs 2022 and never see this behavior. i saw other weird behavior when trying to add the new pkg from a file location. the button to proceed remained gray pretty much blocking me from moving forward. i believe the same thing happened when trying to add from the catalog but i was so harried i didnt take notes of each nuance.
does the community know why on import ssis seems to lose the connection info? Interestingly, when it was still lost the query (sql command) didnt show any more. But when i picked a valid provider, the command suddenly showed.
October 9, 2025 at 5:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply