JoshDBGuy (1/20/2015)
Phil Parkin (1/20/2015)
JoshDBGuy (1/20/2015)
Koen Verbeeck (1/20/2015)
JoshDBGuy (1/20/2015)
That's going to be a nightmare, I'd prefer to not do that.I'm not sure why a SQL Server instance would be a nightmare.
It's not a nightmare, that was an exaggeration, but with all of the other stuff I'm working on, I'd rather not do that. My hope was I could remove ssis 12.0 as it's not being used and then upgrading 11 to 12.
I was thinking I could run the uninstall services process, uninstall 2014 ssis. Then run the upgrade of the 2012 service to 2014.
Given the unusual nature of the task and 2014's newness, I don't think you'll find many people who have done that, so you might have to experiment in the knowledge that it could all go wrong. So have a recovery plan ready.
By the way, the Integration Services service actually does very little: you can turn it off and you'll still be able to work just fine (see here[/url]).
That's some great information. I thought packages would not run, thank you.
No no, all the service does is keeping track of packages running in the package deployment model and to display the packages in a tree structure when you log into the service. When using the project deployment model, it's of very little use. You can safely disable it.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP