sql server 2005 - Slow performance of Reporting Services, very fast in QueryAnalyser -


We are using SQL Server 2005 with reporting services.

We have many reports, each containing a relatively simple SQL query - by "relatively" - I mean we get something, but nothing is worse than this. Also do not call the stored procedure - this is not a case of sniffing the parameter.

By executing one of these reports through reporting services (we call it Report A), it takes a very long time to complete - Tens of tens or hours of order to complete On. When executing related SQL queries in Query Analyzer, this completes in a few seconds.

The number of rows returning from the database can be as 1 - However, the report is never complete.

Other reports are working fine.

Looking at the reporting table on the reporting services, I can see that the timeadata is in recovery most of the time (and we're talking here for hundreds of millions of minutes ..) - the report actually gets completed at that time If the report has been manually canceled, the timeout recovery is zero and time processing is rather high.

I have seen in the logging of the reporting services, but all look normal.

Now, before suggesting "lock", OK, NOLK signal is in our questions.

As I stand, I have reached the limit of my imagination, to find the error, any thoughts, insights will be appreciated happily.

/ Christoffer

I wasted the query that ended, basically a A statement in the bar, until I find the culprit. The one joining the query is included in the ever increasing table (millions of rows) using a "sometimes (nolok index (x))" sign.

Removing the indicator signal in the query analyzer resulted in the same result in reporting services - a too slow query is not surprising in itself - but it really seemed like That the queries run through the RS did not use the signal.

I tried to turn the report into RS again, statement on Set Forsilan ... and ... this work - execution time is now a few seconds, as it should be. As I understand it, the FORCEPLAN option forces the SQL server to process when prompted for the signal, and keeps any signal in mind.

Does anyone have any information, signs, when the query analyst is obviously taking it into account?


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -