Re: testing with sql server



Wendy,

Regarding your SQL Server 2000 debugging problems, you should first check
that your client tools and your server are at the same Service Pack. We had
a lot of problems when we installed SP3a, but many clients did not install
SP3a and could no longer step through the debugging process.

Also, rights can be an issue although I no longer remember the details. If
you are db_owner you should be fine, and maybe db_ddladmin, but rights might
prevent the step through for lower levels of access.

RLF


"Wendy Elizabeth" <WendyElizabeth@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:CE5B59C3-9DAA-4497-9C32-F5297EBA5274@xxxxxxxxxxxxxxxx
I basically want to 'step through' t-sql 2000 statements and I have tried
the several methods. Can you tell me what would you suggest? I have tired
the following methods:
1. I have a question about setting up visual studio.net 2005 professional
version to debug with a sql server 2000 database. The visual studio.net
2005
is on my workstation and the sql server 2000 databases are on two separate
window server boxes.
My goal is to debug some t-sql commands. To do this, I have setup a
project as a database project. The insturctions on the microsoft website
url
says that I need to
attach to a process and the process that I need to attach to is
'sqlserver.exe'. However, I can not find this process to connect so. Thus,
I
can not attach to it if it is not in the drop down list.
Thus can you tell me what my next step would be?
Does it make a difference if I select wanting to debug as 'T-sql clr' or
with the 'SQL CLR' debugger?
2. I have tried to use query analyzer 2000 from my workstation so that I
can
debug a stored procedure. I select the stored procedure I want from the
object browser and right click to debug. The debug window does show up and
the only icons that are not grayed out are the set breakspoints, and start
to
run. It does not allow me to set through or 'step into'. What is wrong
here?

Thanks!


.



Relevant Pages

  • Re: Can i debug/watch on the triggers INSERTED and DELETED records/values?
    ... > Sometimes I do debug remotely. ... we found that debugging did not work when you had Windows ... Now, port 135 is not any port: ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Can not debug SQL sever 2005 Stored procedure from Visual Studio 2005
    ... I am trying to debug a SQL server 2005 SP in VS 2005. ... Direct database debugging where in we select SP and use 'Step Into ... It prompts me for parameters etc but then no window with SP ...
    (microsoft.public.dotnet.general)
  • Debugging in VS.NET
    ... I am attempting to debug a few stored procedures I created using the VS.NET ... After clicking "Run Stored Procedure" the IDE starts debugging, ... "Cannot debug stored procedures because the SQL Server database is not setup ...
    (microsoft.public.sqlserver.msde)
  • Re: Query Analyzer Debuging
    ... They put SP4 on the SQL server and debugging is so ... I hope it is not such a mission to debug in SQL 2k5. ... >server upgraded from SQL SP3 to SQL SP4: ...
    (microsoft.public.sqlserver.tools)
  • Re: SQL 2005 Tools
    ... Ah, I would install the Client tools from SQL Server Express to get to the server, but I'm not sure this is such a good idea unless you don't really care about data security or integrity. ... a clumsy or inept developer (or manager) can wreck the entire database in a heartbeat--with any client tool. ...
    (microsoft.public.sqlserver.connect)

Loading