As SQL Management Studio won't run on Windows Server 2003, can tables be opened in Design mode, "Edit Top 200 Rows", etc., using SQL 2008 Management Studio?
I can connect to the SQL Server 2012 (from SQL 2008 Management Studio), see the databases and tables, but can't open them.
I get this error when trying to "Design" a table: "This backend version is not supported to design database diagrams or tables. (MS Visual Database Tools)"
And I get this error when trying to "Edit Top 200 Rows": "Invalid prefix or suffix characters (MS Visual Database Tools)"
I've tried this from two separate machines (one on Windows Server 2008 R2, and one on Windows 7)...Any ideas? I have a client that accesses their databases from a Windows 2003 system, and would like to get the Management Studio working for them ASAP.
asked Apr 30 '12 at 07:54 PM in Default
Usually tools such as SSMS are only backward compatible, not forward. So, while you may be able to connect up to a SQL 2012 server using SQL 2008 SSMS, it would probably be best not to try to do any design work. There are metadata/system changes in 2012 that the 2008 SSMS won't know how to handle.
Why won't SSMS 2008 run on Windows Server 2003? Is this a 2012 or 2008 version of SSMS that you are referencing? SQL Server 2008 is installable on Windows 2003, so the Management Studio should be as well. Reference here: http://technet.microsoft.com/en-us/library/ms143506%28v=sql.100%29.aspx
Can you clarify a little?
answered Apr 30 '12 at 08:18 PM
Yep - SSMS 2012 will not run on Windows Server 2003. As you have found, you can access the databases and run against SQL no problem from that platform (so for example any applications running on Server 2003 will still run), but if you want to develop and admin against 2012, you are going to have to find an OS platform that is supported - and that's limited to Vista / Win 7 / Server 2008 / Server 2008R2.The client must have, or be open to having a build of one of those somewhere surely? Especially if they've already taken the plunge with SQL 2012.
answered May 01 '12 at 07:24 AM
Kev Riley ♦♦
I have similar issue, where the backend is a SQL2012 but the application is supported only on SQL2008 R2. so i have to install 2008 R2 native client on web server to connect properly to backend. when i registered SQL2012 to the 2008 R2 client and right-click the login -> properties for example, it has error saying similar to "the feature is not available in SQL 7.0"... sound strange... lol.. what i did is install the SP2 for the SQL2008 R2 and the issue gone. :-)
answered Jan 21 '13 at 12:26 AM