In order to set up an SSAS system, I am having to install Visual Studio (SQL Server Data Tools - Business Intelligence) but when I adding this to the instance, it says it has failed the rule "Same Architecture installation", and that I have to match the new installation CPU architecture with the CPU architecture with the instance. The instance I'm trying to link to is Microsoft SQL Server 2014 - 12.0.2269.0 (X64) Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) running on Windows 7. The SSDT installation is Visual Studio 2013. I'm not sure how I can achieve this.

Is it possible to use schema compare in SSDT to compare only specific objects? Not object types, specific objects like 3 tables and 2 stored procedures instead of all tables and all stored procedures?

I'm working on upgrading some SSIS packages from SQL Server 2008 R2 to 2012 and am getting somewhat confused by the SSDT-BI tools. I have downloaded "Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2013" from here , which according to this supports "SQL Server 2014, SQL Server 2012, SQL Server 2008 and 2008 R2". When upgrading a package I don't see an option to upgrade "up to 2012" only. In other words, how can I stop the packages being upgraded too far? Or are 2012/14 pretty much cross compatible? Also, are there other similar implications for SSRS, SSAS solutions? If I need a different version to ONLY upgrade to 2012, which would I need?

Full disclosure: I posted this on SQL Server Central yesterday but got no answers. I hope someone here can assist me. I'm working on importing flat files into a database. I have used a Foreach loop in an SSIS project in SQL Server Data Tools for SQL 2012. have just started developing these packages so please let me know of any rookie mistakes I need to correct. If even one of the files has not been updated in the last day, I want the processing to stop and an alert email sent out. Schematically, the control flow I need is as follows: [Foreach loop] ---> Failure ----> Send import failure email | | ↓ Success ↓ [Proceed with import] I have tested with setting one of the files to be too old, on purpose, to trigger the failure. What happens now, though, is that I get the Failure email but I also get a SQL error from a task in the Proceed with import section, as if the Success path has also been followed. In both success and failure cases, I have tried to set Precedence Constraints with "Expression and Constraint" as the Evaluation operation, with a Boolen value set for the expressions. @[User::ProcessFile]= False or @[User::ProcessFile]= True depending on the case. Could someone explain (or direct me to a reference explaining) how to make sure the SSIS package is following the path I expect it to? EDIT: Picture of control flow is below.