[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 292
  • Last Modified:

Can't run a script in debug mode on SQL Server 2012

I'm running SQL Server Express 2012 on Win 8.1 with Eset firewall. When I try to run a query in debug mode, I get the message
Unable to start T-SQL Debugging. Could not connect to computer '(local)'. The debugger cannot connect to the remote computer. This may be because the remote computer does not exist or a firewall may be preventing communication to the remote computer. Please see Help for assistance.
I've tried suspending the Eset firewall but that doesn't help. Ideas?
0
BlearyEye
Asked:
BlearyEye
  • 3
1 Solution
 
lcohanDatabase AnalystCommented:
"Could not connect to computer '(local)'." - do you have a LOCAL SQL Server installation?
0
 
nemws1Commented:
There are several things you need to do to get this working.  Follow the instructions here:

http://msdn.microsoft.com/en-us/library/cc646024.aspx
0
 
BlearyEyeAuthor Commented:
lcohan: yes, it's local.

nemws1: I'm running v. 2012 so the Configure part should be OK. I tried running with the firewall turned off, so the Firewall Rules shouldn't be an issue. I guess that leaves Requirements for Starting, so I need to figure out if I'm a "member of the sysadmin fixed server role".
0
 
BlearyEyeAuthor Commented:
I found the answer: http://stackoverflow.com/questions/18310383/cant-debug-t-sql-statement-could-not-connect-to-computer. Have to connect as "localhost\..." rather than "(local)\...".
0
 
BlearyEyeAuthor Commented:
I found the answer on my own.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now