Cannot get Debugger to work for stored procedures CLR

Trying to set up debugger to use in Visual studio, want to use stored procedures to run through managed code.  Want to debug.  Changed to compatibility level form 80 to 90 as required.  Gave developers who need debugging capabilities administrtor and sysadmin privs on the SQL SERVER 2005 database.  From Visual Studio attempt to step into stored produre from either database explorer or directly from Visual studio environment from within the Sql Server Project both resulst in the error message:
Unable to start the T-SQL Debugging.  Could not attach to SQL Server process on .....db name....
I have been going through MSDN - and it I have gone through all my permissions .. I am at a loss as to why it is not working - Can anybody help with this - Also, if using debugger on stored procedures will it cause all other gtreads on teh server to be disconnected?  And does anybody have any experience with using managed code within stored procedures - do you find it causes the server to hang at all?  Can the SDK to run these be 1.0 - I am developing in v 2.0 - But believe the production may only be 1.0..
Any help or commenst would be much, much appreciated!
MosquitoeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bob LearnedCommented:
On the Debug tab for the project properties, do you have "Enable SQL Server debugging" checked?

Bob
0
MosquitoeAuthor Commented:
Hello,
There is no "Debug" tab as such - We are developing on Visual Studio 2005 Professional Ed.
I have:  Application, Compile, References, Signing, Database, Deploy
0
Bob LearnedCommented:
I also have 2005 Professional.  What type of project are you working with (Web site, WinForms, ...)?

Bob
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

MosquitoeAuthor Commented:

We were using a Sqlserver project - for creating stored procedures with managed code.  However - as we are not going to be using managed code anymore, just straight T-SQL stored procedures - what would be the best option to run debugger?  I also read one comment that the SQl Server instance must be strted under the username/password of the developer who wishes to use the debugger - this doesn't seem right to me, but am unsure - is this correct or false?
0
Bob LearnedCommented:
Without much fanfare, I am able to execute Stored Procedures from the Server Explorer, with a connection to the server/database that I am working with.

Bob
0
MosquitoeAuthor Commented:

I am able to do the same thing - Execute the stored procedure - But I  cannot set a breakpoint, step into the stored procedure - I get the error message Unable to start T-SQL debugging. Could not attach to SQL Server process on ........
0
Bob LearnedCommented:
I have the SQL Server instance installed with the NT AUTHORITY, and I am able to debug the SQL Server instance on my machine.  I don't have access to a network server to test this out, since I can't enable debugging on that server.

Bob
0
MosquitoeAuthor Commented:

Ahh... I am using a network server... if you are comfortable with the steps required to enable debugging on a remote server - maybe we can walk through it - As what I have done - is not working for us here :(
0
Bob LearnedCommented:
I don't usually debug remote servers.  If I need to debug a stored procedure, I backup/restore the database to my local machine, where I have rights to debug.

Bob
0
MosquitoeAuthor Commented:
This is the solution that worked for us - Since I found it myself, I ama wrding myself the points.

We had to have Sql Server run under a certain account on the remote
machine. An account with the same name needed to be running Visual
Studio on the local machine. We created that account on our machine
and then did "Run As" to invoke Visual Studio. The user that connected
to the database needed to be a sysadmin (either through Windows
Authentication or Sql Server Authentication) and the local machine
needed to have the Local Security Option of "Network access: Sharing
and security model for local accounts" needed set to "Classic - local
users authenticate as themselves".
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.