June 17, 2014 at 12:44 pm
Hello,
I know this is a broad question, but my company is upgrading sql 2005 environment to sql 2012. My question is what affect would SSIS, SSAS, and SSRS objects in 2005 have when moved/run to 2012? Are there any known issues?
I will continue to run searches on Google, but I would like to ask the experts as SSC.
As always, thank you all in advance for your time.
SQL-TG
The are no problems, only solutions. --John Lennon
June 17, 2014 at 1:09 pm
There are quite some differences between 2005 and 2012, in all three of them.
SSAS will be OK for most parts. SSRS might be more difficult, as 2012 uses the more general tablix instead of seperate tables and matrix objects.
SSIS can give issues, especially if you have ActiveX or DTS functionality. That stuff is completely removed in 2012.
Script tasks/components have also underwent a make-over. It will be easier to copy the code and paste it into new script tasks/components.
Some code changes might be necessary, for example when dealing with SSIS variables.
SSIS 2012 has two deployment models: project deployment model and package deployment model.
The first one is brand new and uses projects, parameters and environments (in replacement of the old configurations). The package deployment model is the same as SSIS 2005/08. Maybe you can upgrade to the package deployment first, fix all issues and in a later stage upgrade to project deployment model.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 17, 2014 at 1:18 pm
Thanks very much. That really helps in my analysis. I always say that unless your really need the new "bells and whistles" of 2012, I don't see the point in upgrading that far. Personally I love 2008 R2, and I still feel that it is cutting edge technology (with the exception of cloud programming of course). Maybe that is because I never really used 2012?
The are no problems, only solutions. --John Lennon
June 17, 2014 at 1:31 pm
SQLTougherGuy (6/17/2014)
Thanks very much. That really helps in my analysis. I always say that unless your really need the new "bells and whistles" of 2012, I don't see the point in upgrading that far. Personally I love 2008 R2, and I still feel that it is cutting edge technology (with the exception of cloud programming of course). Maybe that is because I never really used 2012?
As far as SSAS and SSRS go, there is not much difference between 2008R2 and 2012. Unless you want the SSAS tabular model or you want to work with Power View.
SSIS has changed quite a bit in 2012, but since this is a back-end product it is usually not the best argument for a budget request 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 17, 2014 at 2:03 pm
As a solution I am going to install 2012 locally and see what issues arise. I think this is a good solution IF you have a license lying around.
The are no problems, only solutions. --John Lennon
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply