Re: ADO.NET query execution much slower than SQL Management Studio
- From: "Cowboy \(Gregory A. Beamer\)" <NoSpamMgbworld@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Feb 2008 12:42:38 -0600
Make sure you are testing properly. Run the query twice from ADO.NET and see
if you have a different read time. There are two reasons I can think of,
without much thought, why you might get different read times from #1 to #2.
1. JIT time
2. Stats being compiled on SQL Server
If you find a difference, it may just be preloading your app before use will
solve your issue. If not, here are a variety of things you can look at:
1. Library used to connect to SQL Server - If you can use In Memory, it is
fastest; none should be overall slow, so this is just shaving a bit of time,
not a full solution
2. ADO.NET library used (ODBC, OLEDB or SQL)
3. Check the indexes
a) Any fragmented indexes need to been recompiled
b) Do you have the right indexes for your query
4. Would adding some locking hints, etc. help your query?
5. Do you need hints for statistics?
6. Can you improve the query? - Look at the execution plan, as it will give
you a lot of information on straightening out your world
If you are dynamically adding statements in a sproc, you will find that it
will end up having to recompile each time and redo its stats. When you
compare this to the profiler command (meaning what is actually run in the
sproc versus running the sproc statement from profiler), you can see a huge
difference in time. This is why you need to make sure you are running the
sproc in each instance and not just the statement. Depending on how you
profile, you might only see the sproc call.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
*************************************************
| Think outside the box!
|
*************************************************
"dustbort" <d_nospam_bortner@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%2321JRBYdIHA.4220@xxxxxxxxxxxxxxxxxxxxxxx
I have a stored procedure that when called from SQL 2005 Management Studio
takes less than one second to execute. The same SP, when called from .NET
code takes about 13 seconds. I am using a SqlCommand object with
CommandType set to StoredProcedure and I am passing arguments through the
parameters collection. I have tried using a SqlDataReader and a
DataAdapter
to retrieve the data, but both are equally slow. From stepping thru the
debugger, I know that the specific statement that takes a long time to
execute is either reader.ExecuteReader() or dataAdapter.Fill(dataTable),
equivalently depending on the method I tried. I did a trace in the
Profiler, and got nearly identical result for either method of .NET
SqlClient Data Provider. Here is an example:
EventClass: RPC:Completed
CPU: 13390
Reads: 559475
Writes: 0
Duration: 13496
Binary Data: (a long hex value)
When I copied the TextData (SQL Statement being executed) from Profiler
into
SQL Management Studio, I get the following trace:
EventClass: SQL:BatchCompleted
CPU: 437
Reads: 9998
Writes: 0
Duration: 440
BinaryData: (empty)
(Immediately prior to this there is a corresponding SQL:BatchStarting
trace,
with empty CPU, Reads, Writes, and Duration columns.)
What could explain the orders of magnitude difference in reads and
duration?
Is the problem due to RPC? What about the binary data? I have tried
using
the overload of ExecuteReader(CommandBehavior.SingleResult) with no
improvement. What can I try to improve it?
Thanks,
Dustin
.
- Follow-Ups:
- References:
- Prev by Date: ADO.NET query execution much slower than SQL Management Studio
- Next by Date: Re: load flat file into datatable
- Previous by thread: ADO.NET query execution much slower than SQL Management Studio
- Next by thread: Re: ADO.NET query execution much slower than SQL Management Studio
- Index(es):
Relevant Pages
|
Loading
