August 8, 2022 at 8:57 am
I suspect that an SSIS package in source control is not the latest deployed version in production. I want to pull the current deployed package from the production server and check its logic.
This package is deployed to an old SQL 2008R2 box that I'm currently working on moving all the SSIS packages off and on to a SQL 2017 server. Consequently, I have SSMS 17.9.1 installed. This version will not connect to the Integration Services instance of my old SQL 2008R2 server. I know that I need to match SSMS to server version.
So, which version of SSMS do I need to side by side install and use to connect to the Integration Services service on a SQL 2008R2 Server, and second question, where do I get it from? I checked the Microsoft SSMS download page and it only seems to go back to SSSM v17 and nothing earlier.
August 8, 2022 at 9:25 am
for SQL 2008 R2 SSMS was installed as part of the SQL Server installer - you can get it from there.
to avoid installing it on your pc I would check if the server has it installed - and use it from there (RDP) just for this particular purpose.
and have a look at https://docs.microsoft.com/en-us/answers/questions/394177/how-to-copy-ssis-packages-from-sqlserver-2008r2-to.html as maybe you can do it the "easier" way.
August 8, 2022 at 9:30 am
This was removed by the editor as SPAM
August 8, 2022 at 10:20 pm
You don't really need SSMS to be able to get a copy of that package - it depends on how it was deployed. For 2008 deployments you could deploy to the file system - MSDB - or the package store.
If you open up Visual Studio and create a new project - you can then add an existing package and check MSDB and the package store for the package you need.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply