Prev: Query for merge column
Next: Update order
From: Erland Sommarskog on 16 May 2010 04:58 Siegfried Heintze (siegfried(a)heintze.com) writes: > Can you be more explicit in your instructions? I cannot find the SQL > Surface Area Configuration. I ran the SQL Server Network utility and saw > that TCP/IP and pipes were already enabled. I'm wondering if I am really > running SQL Server 2005 or some older version. I also ran the client > network utility and saw that TCP/IP was already enabled. Under > properties it said the default port is 1433. How do I tell what version > I am running? Since you mention the SQL Server Network Utility, I would guess that you have SQL 2000. But it should be clear from looking at the Start menu. Unless you've rearranged it at some point, the name of the Program Group includes the version. But else, you can always run SELECT @@version from a query window. Or Help About in any GUI tool. In this case 8 is SQL 2000, 9 SQL 2005 etc. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Erland Sommarskog on 16 May 2010 05:01 Geoff Schaller (geoffx(a)softxwareobjectives.com.au) writes: > 2. A 2005 installation cannot manage a 2008 instance but the reverse > is quite ok. This is not relevant to Siegfried's issue, but you can connect to SQL 2008 with SSMS 2005, provided that you have SP3 of the tools. You cannot handle everything in SQL 2008 from SSMS 2005, but you can run queries, and Object Explorer is also usuable. -- Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
From: Geoff Schaller on 16 May 2010 18:52
Cool - but it isn't ideal. It would be better just to uninstall the 2005 tools and install 2008. "Erland Sommarskog" <esquel(a)sommarskog.se> wrote in message news:Xns9D7A702111B02Yazorman(a)127.0.0.1: > Geoff Schaller (geoffx(a)softxwareobjectives.com.au) writes: > > > 2. A 2005 installation cannot manage a 2008 instance but the reverse > > is quite ok. > > > This is not relevant to Siegfried's issue, but you can connect to SQL 2008 > with SSMS 2005, provided that you have SP3 of the tools. You cannot > handle everything in SQL 2008 from SSMS 2005, but you can run queries, > and Object Explorer is also usuable. > > > -- > Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se > > Links for SQL Server Books Online: > SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx > SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx > SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx |