Is there any major complication that one could run into while using the latest (developer) version of SSMS with older SQL Server 2005 instances?
Any way one could affect the data by using this version?
SSMS 2014 – Working with SQL Server 2005 Instances
sql serversql server 2014sql-server-2005ssms
Related Question
- Sql-server – Why are zero length spaces being returned from a Union All against an empty table in SQL Server 2005 but not SQL Server 2012
- SQL Server – Restoring 2008 R2 Backup on 2005
- SSMS 2014 – Deploy Database Feature with Old SQL Azure Settings
- Managing Mixed SQL Server Instances with Static and Dynamic Ports
- Sql-server – Is it possible to remote connect to SQL Server 2008 database with SQL Server Management Studio 2005
- Sql-server – Moving Databases between Instances of different Versions of SQL Server
- Sql-server – SSMS 2014 does not launch Graphical Execution Plan from clicking hyper-linked query plan – ShowPlanXML
Best Answer
My motto is to always use the most recent version of the tools and always have tools >= highest engine you manage. Generally, most of everything in modern versions is backward compatible going back as early as 2005 instances.
There are a couple of exceptions, in addition to those others have mentioned:
The nice thing is that you can install both the 2005 version of the tools as well as the most recent version side-by-side. This way, if you come across any compatibility issues, you can fire up the older version.
In general, you should be able to use the newer version for just about everything, and not worry about any negative effects on your data (full disclosure though - I don't use the UI functionality for a whole lot, particularly the buggy designers).