How to speedup the execution of a query in Sql Server?
-
How to speedup the execution of a query in Sql Server?
-
How to speedup the execution of a query in Sql Server?
In SSMS under tool the first entry is SQL Server Profiler - use that as your first step.
Never underestimate the power of human stupidity RAH
-
How to speedup the execution of a query in Sql Server?
You need to present a bit more detail so that some suggestions can be given. Generally, are you linking tables together ? How many? How many rows are in each table? How many rows are being returned in your query? With the SQL profiler you will be able to tell whether the server is scanning the table or seeking data via an index. Your question is too vague to get a valuable answer.
-
You need to present a bit more detail so that some suggestions can be given. Generally, are you linking tables together ? How many? How many rows are in each table? How many rows are being returned in your query? With the SQL profiler you will be able to tell whether the server is scanning the table or seeking data via an index. Your question is too vague to get a valuable answer.
Hi David Mujica, Thanks for your reply,but I need just rough idea or tips.
-
Hi David Mujica, Thanks for your reply,but I need just rough idea or tips.
My response was a tip, without more information we can't really be more specific. Statements like check you indexes (profiler helps) and check your syntax are going to be basically all we can do. Tuning a DB and queries is almost an art so you need to give us some subject matter. What you have given us is like asking why your painting is rubbish!
Never underestimate the power of human stupidity RAH
-
How to speedup the execution of a query in Sql Server?
After checking your keys and indexes, you could try to omit as much functions in the query as possible, limit the case-when switches and remove any unused tables and/or columns. MSDN also has a few pages on the subject :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
After checking your keys and indexes, you could try to omit as much functions in the query as possible, limit the case-when switches and remove any unused tables and/or columns. MSDN also has a few pages on the subject :)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
Hi Eddy Vluggen, It helps me a lot. :) :thumbsup: