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!

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@discussions.microsoft.com> wrote in
message news:CE5B59C3-9DAA-4497-9C32-F5297EBA5274@microsoft.com...
> 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!

Russell:

I am assuming that you mean service pack SP3A on sql server 2000, correct?

thanks!

"Russell Fields" wrote:

> 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@discussions.microsoft.com> wrote in
> message news:CE5B59C3-9DAA-4497-9C32-F5297EBA5274@microsoft.com...
> > 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!
>
>
>

Correct.

RLF

(Must remember to always include full context. Since I am studying Chinese,
you would think that I would remember that already.)

"Wendy Elizabeth" <WendyElizabeth@discussions.microsoft.com> wrote in
message news:53CAEF7C-BDD7-4614-9543-5B04DC4C63E3@microsoft.com...
> Russell:
>
> I am assuming that you mean service pack SP3A on sql server 2000,
> correct?
>
> thanks!
>
> "Russell Fields" wrote:
>
>> 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@discussions.microsoft.com> wrote in
>> message news:CE5B59C3-9DAA-4497-9C32-F5297EBA5274@microsoft.com...
>> > 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!
>>
>>
>>