Sql query runs in seconds but same query inside store procedure is taking time to execute

Question

0.00/5 (No votes)

See more:

I have created one store procedure which is taking too much time compile but when i ran same query within stored procedure separately it gets executed with in seconds. I am not able to find the reason behind that. Please help me out what will be the problem behind that. It is very helpful for me. Thanks in advance.

Posted 4-Jun-15 20:39pm

NareshChingu

Add a Solution

Comments

DamithSL 5-Jun-15 2:50am

can you explain the testing steps for both in detail?

Tomas Takac 5-Jun-15 3:16am

Did you check the query plans? Maybe a wrong one is cached for the SP.

OriginalGriff 5-Jun-15 3:58am

This is not a good question - we cannot work out from that little what you are trying to do.
Remember that we can't see your screen, access your HDD, or read your mind.
We need to know how you are executing the two queries for comparison, what code if any you are using, how you are timing them. At the moment, you have called the garage, said "my car is slow sometimes" and put the phone down. The garage needs to know if it's when you are going up hill, or it's very cold - or very hot, if you are towing a caravan, etc.

Use the "Improve question" widget to edit your question and provide better information.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jörgen Andersson · Answer 1 · 2015-06-05T02:35:00

Solution 2

I'm assuming you're using SQL Server here.
When you have different execution times in different environments it's usually the plan cache that's the culprit.
For a better understanding I'll refer you to an article[^] by the real SQL Server Guru, Erland Sommarskog.

Posted 5-Jun-15 2:35am

Jörgen Andersson

Advay Pandya · Answer 2 · 2015-06-05T00:28:00

Hi,

I have faced this issue many times. If u execute the same query many times then SQL will return the query result from cache. So it will provide fast result.

Please use below lines before executing your query.

SQL

CHECKPOINT;
GO
DBCC DROPCLEANBUFFERS;
GO

That will remove the cache and provide you the fresh result.

I believe your query will take the same time as your stored procedure.

Please let me know if you have any concern or query on this.

Thanks
Advay Pandya