Re: Breakpoints in T-SQL not hit from VS 2005 with SQL 2005

Tech-Archive recommends: Fix windows errors by optimizing your registry

I did this prior to writing this inquiry.

I tried the other way:
in VS 2005 -
Debug - Attach process sqlserver.exe
Open stored procedure in server explorer and set breakpoint
Run the procedure from SQL Server Management Studio
to no avail.

I noticed that when attaching slqserver.exe proces in VS 2005 - Debug -
"Attach to process" window, type column is x86, while there are processes
which have other types such as T-SQL, Managed, Script. Should sqlserver.exe
not have T-SQL type present?

I wonder if anyone is debugging T-SQL this way?

"Eric Moreau" wrote:

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




.

Relevant Pages

  • Re: Problem using SP as record source with Access2002 & SQL Server 7
    ... I've installed a brand new copy of SQL Server 2000 with the original ... I've created the folowing stored procedure for the resync ... Resync Command: ALL_CUSTOMERS_RESYNC? ... I need to upgrade to a newer version of Microsoft SQL ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Creating a database
    ... Please do yourself a favor, find a local user group, or buy a beginning book on SQL Server or take a class, you will save yourself a great deal of pain in the long run. ... CREATE DATABASE Products ... I can create a stored procedure from within the Server Explorer and from ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL/ADO (2.8) Timeout Error - Cant resolve
    ... > Server 2000 back end. ... > timeout limit. ... And I’ve used SQL Query Analyzer to run the ... I am running a stored procedure that will backup a SQL Server ...
    (microsoft.public.sqlserver.clients)
  • Re: "IF" test in SP evals to True and False at same time using DataAdapter.FillSchema()
    ... Also tested in my code after adding "SET FMTONLY OFF" to the Stored Procedure. ... There's just no reliable way to get the column metadata from a stored ... >select the SQL Server Debugging check box. ... > "The breakpoint will not currently be hit. ...
    (microsoft.public.dotnet.framework.adonet)
  • RE: Stored procedure / .NET woes
    ... Check the available network protocols on both the server and the client (web ... using the SQL client and server network tools. ... > Strangely enough running the same stored procedure through the SQL ...
    (microsoft.public.dotnet.framework.adonet)