November 25, 2011 at 9:04 pm
I'm an Oracle DBA that's been asked to do some work on SQL Server 2000. I've been granted domain access and have installed MS SSMS 2008. I can access the SQL Server 2000 databases via this tool and see the tables, views, functions, stored procedures, etc. However, if I try to access the data in the tables or run queries against any of the user tables or system tables I get the following error message.
"Cannot execute script. Unable to start the Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
I'm assuming it's a permissions problem. I can where the sysadmin SQL Server Fixed Role is assigned to the BUILTIN\Administrators role. I've read where administrators - local, domain, etc. - are implicitly assigned to the BUILTIN\Administrators role so I'm not sure why this is not working.
Does anyone have any ideas? Thanks in advance for your assistance.
November 26, 2011 at 2:30 am
Have you tried clicking on the red exclamation point icon (execute) instead of the green right-pointing arrow icon (debug)? I've never tried looking at a 2000 database from 2008 SSMS, but the debugger has both client side and server side components and the server side components are only in 2008, not 2005 or earlier, so clearly you can't use the 2008 debugger with 2000 and the error message you are getting suggests that this, rather than permissions, is your problem.
Tom
November 27, 2011 at 11:15 am
I believe Tom has this nailed. The Green Arrowhead used to be the "run" command prior to SQL Server 2000. In 2005 and up, it's now the "run debugger" command. You need to click on the Red exclamation point in the menu or, alternately, press f5 to run a script in SSMS.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 27, 2011 at 6:21 pm
Jeff Moden (11/27/2011)
I believe Tom has this nailed. The Green Arrowhead used to be the "run" command prior to SQL Server 2000. In 2005 and up, it's now the "run debugger" command. You need to click on the Red exclamation point in the menu or, alternately, press f5 to run a script in SSMS.
I use CTRL-E myself to execute - hardly ever hit the execute button or F5.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 28, 2011 at 12:20 am
Jeffrey Williams 3188 (11/27/2011)
Jeff Moden (11/27/2011)
I believe Tom has this nailed. The Green Arrowhead used to be the "run" command prior to SQL Server 2000. In 2005 and up, it's now the "run debugger" command. You need to click on the Red exclamation point in the menu or, alternately, press f5 to run a script in SSMS.I use CTRL-E myself to execute - hardly ever hit the execute button or F5.
I use ALT-X. These buttons are even closer together :w00t:
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 28, 2011 at 1:24 am
haha click the F5 button dude! 😀
===============================================================
"lets do amazing" our company motto..
November 28, 2011 at 8:33 pm
Duh! Thank you! I assumed the green arrow was the same as the execute. Thanks for taking the time help.:w00t:
November 28, 2011 at 8:35 pm
Thanks Jeff. You guys were "Steel on Target!" Thanks for taking the time to help.:w00t:
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply