Re: Unable to view system stored procedures from .NET IDE and unable to debug SQL

From: Andrew Gaskell (agaskelluk_at_yahoo.com)
Date: 07/16/04 

Date: Fri, 16 Jul 2004 10:56:20 -0700

Ah right, as easy as that! I was worried there was something wrong with
my MSDE setup.

But what is the reason for the debug problem I mentioned below? When I
try to step into a stored procedure in the Northwind database, I get the
error message:

"cannot debug stored procedures because the SQL Server database is not
set up correctly or user does not have permission to execute
master.sp_sdidebug. Run SQL server setup or contact database
adminstrator."

Thanks
Andrew
 

>The IDE does not allow you to view or edit the system >stored
procedures.
>Apparently, we might mess something up that way. ;-)

>You'll need another tool for that. I keep the SQL client >tools on my
>machine just in case.

"Andrew Gaskell" <agaskelluk@yahoo.com> wrote in message
news:63c811db.0407160055.686ebb2c@posting.google.com...
> Hi All
> I installed MSDE on my Win2K machine. I can see the system stored
> procedures just fine from a remote machine's SQL enterprise manager,
> but when I use the .NET IDE, although I can connect to the local MSDE
> databases, I can't see any system stored procedures in master. When I
> attempt to debug any SQL, I get the error message:
>
> cannot debug stored procedures because the SQL Server database is not
> set up correctly or user does not have permission to execute
> master.sp_sdidebug. Run SQL server setup or contact database
> adminstrator.
>
> ...which almost certainly has something to do with me not seeing any
> system stored procedures. I am a member of the local administrators
> group on the machine.
>
> Please help!
>
> Thanks
> Andrew

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Relevant Pages

  • Re: testing with sql server
    ... Regarding your SQL Server 2000 debugging problems, ... version to debug with a sql server 2000 database. ... My goal is to debug some t-sql commands. ... attach to a process and the process that I need to attach to is ...
    (microsoft.public.sqlserver.setup)
  • Re: Identical database w/ identical stored procedures?
    ... > creating the maintence nightmare of updating the same stored procedure ... First of all, put your source code, tables, stored procedures and all ... This can be achieved with a help table in the database. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (comp.databases.ms-sqlserver)
  • Re: Does nesting stored procedures make sense to increase performance?
    ... Reducing client or middle-tier round trips to the database is a good idea in that it will reduce network traffic. ... In SQL Server 2000, because recompiles of query plans are done on a per-procedure basis, it's helpful some execute one SQL statement per procedure as well. ... If you're going to combine many calls into a single call, you'll need to add robust error handling to the "driver" procedure so as not to call procedures 2,3, and 4 if procedure 1 fails, etc. You'd need to replicate your existing client/middle-tier code's concept of success/failure results quit the batch of procedures on a failure and the return the results/return code that the client/middle-tier sees in the original. ... I've recently became aware of nesting stored procedures in SQL Server. ...
    (microsoft.public.sqlserver.programming)
  • Re: visutal studio.net 2005 debugging question
    ... version to debug with a sql server 2000 database. ... My goal is to debug some t-sql commands. ... attach to a process and the process that I need to attach to is ...
    (microsoft.public.vsnet.debugging)
  • Re: Debugging in VS.NET
    ... > "Cannot debug stored procedures because the SQL Server database is not ...
    (microsoft.public.sqlserver.msde)