Re: Breakpoints in T-SQL not hit from VS 2005 with SQL 2005
- From: "Eric Moreau" <eric.moreau_N_O_S_P_A_M@xxxxxxxxxxxx>
- Date: Wed, 3 May 2006 22:41:04 -0400
In the project properties, under the Debug tab, check "Enable SQL Server
debugging
--
HTH
Éric Moreau, MCSD, Visual Developer - Visual Basic MVP
Conseiller Principal / Senior Consultant
Concept S2i inc. (www.s2i.com)
http://emoreau.s2i.com/
"pearcz" <pearcz@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9F3880D9-3704-425C-BD14-300465FD0F32@xxxxxxxxxxxxxxxx
Hallo,
I have Visual Studio 2005 Team Edition for Software Developers together
with
SQL Server 2005 Developer Edition installed on local PC.
I created a windows project and called stored procedure using
ExecuteNonQuery.
In Server Explorer window I added a reference to SQL 2005 database, opened
a
t-sql procedure and set a breakpoint.
When running code, the breakpoint never gets hit nor can I step into the
stored procedure from .net code.
When I set the breakpoint in t-sql, there is a tooltip saying
"The breakpoint will not currently be hit. Unable to bind SQL breakpoint
at
this time. Object containing the breakpoint not loaded."
I can debug the stored procedure via righclick and Step Into ... (but that
requires setting its parameters manually).
Enabled SQL Server debugging checkbox is checked on the windows project
and
in server explorer Application debugging is checked too.
The stored procedure is pure T-SQL, no CLR.
I tried sql connection strings with both windows (integrated
security=SSPI)
and sql authentication.
What am I doing wrong?
Thanks for answers
Pavel
.
- Follow-Ups:
- Prev by Date: Killing Additional DLLs was the best bit of work we ever did
- Next by Date: Re: Breakpoints in T-SQL not hit from VS 2005 with SQL 2005
- Previous by thread: Killing Additional DLLs was the best bit of work we ever did
- Next by thread: Re: Breakpoints in T-SQL not hit from VS 2005 with SQL 2005
- Index(es):
Relevant Pages
|
