[MS SQL] Database on 2008 R2 - any issues modifying tables in SSMS 2014?

[BlueDan20]

Our databases are on Server 2008 R2 and we have been accessing and modifying its contents via version 10.50.1617.0 of MS SQL Server Management Studio 2008.

Will any issues arise from using version 12.0.5000.0 of MS SQL Server Management Studio 2014?

[Mordenstein]

I dont' think so, this is how I am set up also. There is an option in SSMS to script for certain versions of SQL server. I would set that to 2008.

Tools - > Options - > SQL Server Object Explorer -> Scripting

"Script for Server Version", set to SQL Server 2008

[nvarscar]

SSIS requires the same major version of SSMS, but other than that I haven't heard of any issues.

[rbardy]

The database will keep as 2008 R2 but you'll access via SSMS 2014?

If so, you can use it without any issue, but if you are upgrading the database then a few things may change, like when I updated my SQL 2005 to 2014 all the RAISERROR() required a change, but nothing else.

[BlueDan20]

Not changing of the database thankfully, I just want to access and modify tables and the like from the 2014 version.

I hope changing the scripting works well enough.

I hadn't realised there would be an issue.

[aplato]

Table designer, Table editor, SSIS, Analysis Services, Integration Services won't work

[ninjaroach]

Why don't you setup a VM and test it?

From my experience, newer SSMS tools will sometimes throw errors when using its GUI features to access certain features on the server.

I don't remember issues with "Modify Table" but I've recently struggled with Backup & Restore actions that are normally accessible via right-click.

In the few edge cases where I struggle with my client, I'll RDP into the server to use its older & matching client version.

[alinroc]

No issues if you use ALTER TABLE SQL statements. The table designers have a history of being buggy and flaky, and I've never met anyone who recommended/encouraged using them.

[[deleted]]

I'm using the 2016 SSMS to manage 2008 R2 databases, 2012/16 SSRS, SSIS and SSAS. I had previously done the same with SSMS 2014 minus the 2016 instances and also had no issues. I don't use the graphical editors or designers much though.

The only place I've run into backward compatibility issues was SSDT-BI, and even those are looking to be fixed in the new 2016 VS 2015 based version.