Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 430
  • Last Modified:

RPC Call VS. Query Analyzer

I have a weird problem here that I can't seem to figure out.  Here's the jist of it:

When a certain VB application executes a stored procedure via an RPC call, it ends up timing out (beyond 5 minutes).  I verified that the SQL server is indeed receiving the RPC call (it shows up in Profilder, and Ethereal).  The VB app terminates the process after 5 mintues because the SP apparently is still going.  

When I execute the SAME stored procedure using the same paramters from Query Analyzer, it takes 25 seconds.  

I have some index tuning plans I will implement soon that will take it from 25 down to 1 seconds or less using the Analyzer, but, I still don't know why it times out from the RPC call.

So my question is, what's the main difference here that makes the Query Analyzer so much quicker?

Thanks for the help.
0
TheTull
Asked:
TheTull
  • 5
  • 2
1 Solution
 
sathyagiriCommented:
Do you have any RAISERROR WITH NOWAIT in your SP?

If so, it seems there's a bug in SQL server which causes your situation
0
 
TheTullAuthor Commented:
There are several RAISERROR statements, but none with a NOWAIT statement included.

What is this bug?
0
 
sathyagiriCommented:
Are you using a clustered server  of some sort?

Please post your OS, Server versions etc
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
TheTullAuthor Commented:
No clustered servers,

Running Microsoft SQL Server 2000 on Windwos 2000 Server.

0
 
TheTullAuthor Commented:
Another interesting thing I will throw out there,

Sometime over a month ago, our SQL server process sqlservr.exe was running happily at 1.7 Gigs of RAM usage.  When I restarted it about a month ago, it will no longer go past 90,000 K of RAM.  However, the RAM availalbe under the task manager is at 1 GIG (we have 4 GIG on this server).  And SQL server appeared to have been running well.  So, I don't know why it is sticking at 90 Megs like that instead of jumping back to 1.7 Gigs.
0
 
TheTullAuthor Commented:
Suddenly it takes forever using Query Analyzer too....

Sigh, I am going to have to do some more testing and whatnot.
0
 
TheTullAuthor Commented:
Fixed the "Entire" problem by dropping the primary key on the table, then re-applying it.  This caused the PK index (which was corrupted) to be re-created, thus fixing all issues where I was unable to select any data what so ever.

Everything is nice and happy with the server now, thanks for the help.

0
 
NetminderCommented:
Closed, 500 points refunded.
Netminder
Site Admin
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now