HiI am facing a strange situation with a prepared query sent from Java application, SQL profiler is showing a very high reads about 250 000 pages (CPU:63155, duration 63640), when I look in the Query plan captured by SQL profiler there is no table or index scan, there are around 5 main tasks with:cost between 15 and 20%Actual number of rows : between 1 and 400Physical access : Clustered or Index seekI am trying to figure out what is causing the 250 000 pages reads without success, since this a prepared query this is hard to reproduce the issueHere is what looks like the query : exec sp_execute 95503,325138,...with the handle 95503 I am able to find the original query and when run the query on Management studio the number of reads is low just 380 pages and duration is only 345 ms compared to the original one 63640 msthe reads in SQL profile will incude the read from the cache but this will not explain the very high of the reads, any idea how to track the root cause of this veru high reads ?
↧