TSQL-Debug in SQL 2000

[Werner]

One of my kindest and oldest dreams: being able to debug stored procedures
in a similar way I debug a VB-Program.....


What I can do

- SQL Query Anayzer, rightclick SP
- Select Debug, then Execute to open T-SQL Debugger
- Set Breakpoints


What I cannot do (what I would like to do most of all)

- Step into, step out, run to cursor ...
- The respective buttons, rightclick-menue-point are grayed.

Can you tell me why (would be worth a second copy of your book ;-) )!!



Kindly yours


Werner

[Rob Vieira]

Hi Werner,

What account is the SQL Server Service running under? The symptoms you are
telling me about are one of many symptoms that I've seen when running SQL
Server using the local system account. In a nutshell, the SQL Debugger
doesn't work well when SQL Server is using the local system account. If you
run it under a normal NT user account, then I suspect you'll see your
problems go away.

--
Rob Vieira
Visit www.ProfessionalSQL.com Today. It's new and improved!

"Werner" <wzoller@mbbm.de> wrote in message news:3a6ee6d3$1@news.devx.com...
>
> One of my kindest and oldest dreams: being able to debug stored procedures
> in a similar way I debug a VB-Program.....
>
>
> What I can do
>
> - SQL Query Anayzer, rightclick SP
> - Select Debug, then Execute to open T-SQL Debugger
> - Set Breakpoints
>
>
> What I cannot do (what I would like to do most of all)
>
> - Step into, step out, run to cursor ...
> - The respective buttons, rightclick-menue-point are grayed.
>
> Can you tell me why (would be worth a second copy of your book ;-) )!!
>
>
>
> Kindly yours
>
>
> Werner

[Werner]

>What account is the SQL Server Service running under? The symptoms you are

I have two instances of SQL2k: one is running under a local account (not
system) and the other under a domain account

Are there an particular rights or permissions, it must have?

>run it under a normal NT user account, then I suspect you'll see your problems
go away.

Unfortunately: No!


Werner

[Rob Vieira]

I shouldn't have put it as "normal" NT user account - the SQL Server Service
account must actually have admin rights to the box you're debugging on.

Note that I consider it very important that you limit the notion of using an
administrator account for the SQL Server Service to development systems
only.


--
Rob Vieira
Visit www.ProfessionalSQL.com Today. It's new and improved!

"Werner" <wzoller@remove.nospam.mbbm.de> wrote in message
news:3a712a00$1@news.devx.com...
>
> >What account is the SQL Server Service running under? The symptoms you
are
>
> I have two instances of SQL2k: one is running under a local account (not
> system) and the other under a domain account
>
> Are there an particular rights or permissions, it must have?
>
> >run it under a normal NT user account, then I suspect you'll see your
problems
> go away.
>
> Unfortunately: No!
>
>
> Werner
>