I'm at a big shop with different environments in different versions of SQL. I have SQL Server Enterprise 2012 and I have Visual Studio solutions for SSRS/SSIS/DB all on 2012 for a code base that will be applicable to 2012 and 2014 (meaning we plan to use the same "solutions" on both as there is a lot of core code that we deploy). I am hearing many reports that SSIS projects get updated when they are opened in Visual Studio 2013 and SQL 2014 despite no change to SSIS in 2014.
1. Given SSIS's challenges... My question is, would it be best to just forgo using Visual Studio 2013? Will all of my 2012 SSIS/SSRS/DB projects deploy nicely to a 2014 environment? Is there a cleaner option? I don't want to maintain 2014 and 2012 solutions unless I'm forced to.
2. I have a fat client install base of Report Builder installed on some user machines. Can I just point my users to Report Builder for 2012 to hit both 2012 and 2014 instances of SQL? I'd prefer this so that reports RDL's are compatible with both as we have many reports that will go on both environments.
Thanks,
Keith