Showing posts with label queryanalyzer. Show all posts
Showing posts with label queryanalyzer. Show all posts

Friday, February 17, 2012

Debugger Interface Problem in QA

Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:

> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>

Debugger help

Could anyone please give me a quick head start on the debugger in SQL Query
Analyzer. I right click on my 'sp' and select debug. This shows my code in
the right pane. However I seem unable to step though. The only buttons
highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go' d
o
the step through, step over, etc buttons become highlighted by which time it
is too late as my sp is already processing.Set a breakpoint at the beginning of the procedure then click 'Go'.
ML|||Hi
I think that if you click on the procedure declaration your buttons should
become active.
John
"Chubbly Geezer" wrote:

> Could anyone please give me a quick head start on the debugger in SQL Quer
y
> Analyzer. I right click on my 'sp' and select debug. This shows my code
in
> the right pane. However I seem unable to step though. The only buttons
> highlighted are 'Go' and the 2 breakpoint buttons. Only when I click 'go'
do
> the step through, step over, etc buttons become highlighted by which time
it
> is too late as my sp is already processing.

debug stored procedure

I created a stored procedure that is referenced by a SQLDataSource& DetailView on a web page. I tested the stored procedure in QueryAnalyzer & everyting looks good.
When I get to the page to display the detailview, nothing is displayed.I ran SQL Profiler, to see what was happening & the storedprocedure isn't being called.
I checked & rechecked the references to the SQLDataSource & even tested them in the configuration wizard.
I replaced the stored procedure with the query & it worked, except I had to 'hardcode' the variable values.

The stored procedure does return error results when they occur - how can I intercept them?

How can I determine what is happening with this stored procedure? Is there a way to trace it other than with SQL Profiler?

Thanks in advance.

OldSamIf your stored proc works fine in Query Analyzer and not from your app unless the parameters are hardcoded => your values from the app are not being properly communicated with the stored proc. You could do a response.write of the values you are passing to see whats being passed.|||You are correct. I found it just before your post arrived - one of my nvarchar fields was NULL.
I still wish there were a better way to see these values in debug mode. I suspect there is; I just don't know how to get to it.

Thanks

OldSam|||

If you have VS 2005 you can create a Database Project and supposedly you can debug stored procs. I havent yet done that though.

Debug sp in Query Analyzer

Hi all,
Is it possible to debug sp in client workstation by using sql query
analyzer? how?
It's only work to me when debug sp in the SQL server by using sql query
analyzer
Thanks in advance!!
MartinNo it is possible only from Query Analyser
Madhivanan|||it means that the Query Analyser and the SQL server must be within the same
machine, rite?
"Madhivanan" <madhivanan2001@.gmail.com> wrote in message
news:1122472249.786547.271590@.z14g2000cwz.googlegroups.com...
> No it is possible only from Query Analyser
> Madhivanan
>|||Yes
Madhivanan|||thx!
"Madhivanan" <madhivanan2001@.gmail.com> wrote in message
news:1122476462.825295.300700@.z14g2000cwz.googlegroups.com...
> Yes
> Madhivanan
>|||No - you can have Query Analyzer on one machine, and the SQL server instance
on another machine, and still debug a stored procedure (I just debugged a
stored procedure on our development server from my own workstation to verify
this). You do need to have the SQL Server properly configured, but Query
Analyzer does not need to be run from the same machine as the SQL server
instance.
"Atenza" <Atenza@.mail.hongkong.com> wrote in message
news:ufjA2ZrkFHA.3436@.tk2msftngp13.phx.gbl...
> it means that the Query Analyser and the SQL server must be within the
same
> machine, rite?
>
> "Madhivanan" <madhivanan2001@.gmail.com> wrote in message
> news:1122472249.786547.271590@.z14g2000cwz.googlegroups.com...
>|||what do you mean by: 'You do need to have the SQL Server properly configured
,
but Query Analyzer does not need to be run from the same machine as the SQL
server instance.'? What do I need to configure differently on the sql serve
r
so that developers can use the debug feature from their work stations?
"Jeremy Williams" wrote:

> No - you can have Query Analyzer on one machine, and the SQL server instan
ce
> on another machine, and still debug a stored procedure (I just debugged a
> stored procedure on our development server from my own workstation to veri
fy
> this). You do need to have the SQL Server properly configured, but Query
> Analyzer does not need to be run from the same machine as the SQL server
> instance.
> "Atenza" <Atenza@.mail.hongkong.com> wrote in message
> news:ufjA2ZrkFHA.3436@.tk2msftngp13.phx.gbl...
> same
>
>

Tuesday, February 14, 2012

debug

Hi all,
I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
database, right click the SP I want and select Debug. It prompts me for the
parameters and I enter them. It seems to execute the procedure and give me
@.RETURN_VALUE =0. I go through the procedure and set breakpoints at every
line. I hit F5 for GO and it runs right through it again and gives me the
return value. It does not break at my break points.
Sql Server is running under a domain user account, not the local system
account.
Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
8.00.194, Windows XP, SP2.
I've read Sql Server Tools Troubleshooting, but everything is ok.
Anyone have an idea why I can't debug?Please post the stored procedure so that we can better assist you. Without
being able to see what you are working with, we are just guessing.
--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"meri2" <meri2@.gmail.com> wrote in message
news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
> Hi all,
> I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
> database, right click the SP I want and select Debug. It prompts me for
> the parameters and I enter them. It seems to execute the procedure and
> give me @.RETURN_VALUE =0. I go through the procedure and set breakpoints
> at every line. I hit F5 for GO and it runs right through it again and
> gives me the return value. It does not break at my break points.
> Sql Server is running under a domain user account, not the local system
> account.
> Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
> 8.00.194, Windows XP, SP2.
> I've read Sql Server Tools Troubleshooting, but everything is ok.
> Anyone have an idea why I can't debug?
>
>|||It happens with all the stored procedure.
thanks
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:OdmWh1zqGHA.5008@.TK2MSFTNGP05.phx.gbl...
> Please post the stored procedure so that we can better assist you. Without
> being able to see what you are working with, we are just guessing.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "meri2" <meri2@.gmail.com> wrote in message
> news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
>> Hi all,
>> I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for
>> my database, right click the SP I want and select Debug. It prompts me
>> for the parameters and I enter them. It seems to execute the procedure
>> and give me @.RETURN_VALUE =0. I go through the procedure and set
>> breakpoints at every line. I hit F5 for GO and it runs right through it
>> again and gives me the return value. It does not break at my break
>> points.
>> Sql Server is running under a domain user account, not the local system
>> account.
>> Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client
>> is 8.00.194, Windows XP, SP2.
>> I've read Sql Server Tools Troubleshooting, but everything is ok.
>> Anyone have an idea why I can't debug?
>>
>

debug

Hi all,
I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
database, right click the SP I want and select Debug. It prompts me for the
parameters and I enter them. It seems to execute the procedure and give me
@.RETURN_VALUE =0. I go through the procedure and set breakpoints at every
line. I hit F5 for GO and it runs right through it again and gives me the
return value. It does not break at my break points.
Sql Server is running under a domain user account, not the local system
account.
Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
8.00.194, Windows XP, SP2.
I've read Sql Server Tools Troubleshooting, but everything is ok.
Anyone have an idea why I can't debug?Please post the stored procedure so that we can better assist you. Without
being able to see what you are working with, we are just guessing.
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"meri2" <meri2@.gmail.com> wrote in message
news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
> Hi all,
> I go into SQL QueryAnalyzer for debugging. Expand Stored Procedures for my
> database, right click the SP I want and select Debug. It prompts me for
> the parameters and I enter them. It seems to execute the procedure and
> give me @.RETURN_VALUE =0. I go through the procedure and set breakpoints
> at every line. I hit F5 for GO and it runs right through it again and
> gives me the return value. It does not break at my break points.
> Sql Server is running under a domain user account, not the local system
> account.
> Server is SQL Server Enterprise Edition, version 8.00.818 (SP3). Client is
> 8.00.194, Windows XP, SP2.
> I've read Sql Server Tools Troubleshooting, but everything is ok.
> Anyone have an idea why I can't debug?
>
>|||It happens with all the stored procedure.
thanks
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:OdmWh1zqGHA.5008@.TK2MSFTNGP05.phx.gbl...
> Please post the stored procedure so that we can better assist you. Without
> being able to see what you are working with, we are just guessing.
> --
> Arnie Rowland
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "meri2" <meri2@.gmail.com> wrote in message
> news:OLFOQzwqGHA.1796@.TK2MSFTNGP03.phx.gbl...
>