There's not enough information about the schema/query to tell what the problem is. I suggest using the SQL Profiler to capture the query being run and then running it in SSMS with the Include Actual Execution Plan option to see where the time is going.
On Wednesday, January 30, 2013 10:42:15 AM UTC-5, [email protected] wrote: > > Ok so this is a really weird issue and has our office stumped. We have a > fairly complex Query that has a few joins and a few SubQueries that each > have a join, so it's by no means the fastest query known to man, but using > NHProfiler, it takes 2400 seconds to execute the query, and ~110 seconds > total time to return the dataset for 3300 rows. NHProfiler only shows 1 > query being ran, so it doesn't appear to be an n+1. > > If I leave out one of the columns in the select, the time is acceptable, > but then I don't get the needed data. I added an index manually in MSSQL > Server Management Studio on (Id, Duration), Duration is a decimal(19,5) and > it speeds up the query time and return time, to 800ms/7400ms vs the > 2400ms/~110000ms. However, if I right click the index -> script index as, > and run it as script, it doesn't increase performance at all. > > I don't think the complete issue is whether or not we have the index, just > that it seems to help make it slightly more acceptable. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
