Hi robinsonpr, Thanks for your post. You are right, Report Model return all of the data (~3 million rows) to the report, and then the report apply Semantic Query to the report model to retrieve the desired data, which is the root cause to affect the query performance. So, I would suggest you to query the relevant data from database instead of cooperating with report model. Thanks, Bill Lu Bill Lu TechNet Community Support

I have created a Report Model in SSRS 2008R2. It retrieves data from a view in an Oracle database. It's a very basic model, literally a pass through. The Report Model retrieves all of the data in the view, but note that it's a large dataset of almost 3 million records. I created a test report (using BIDS) which returns the data using the Report Model. In the Dataset in the test report I added a filter to the SemanticQuery, a very simple filter of USER_ID > 0 and USER_ID < 1000, so only looking for a small subset of data. I ran a preview of the report and it ran for over an hour, in fact it still IS running now and still hasn't come back with any results! In the meantime I created another test report which does not use the Report Model, but goes directly to the View. In this second test report I put the same query, but this time rather than the Dataset creating a SemanticQuery from the Query Designer it generated the following SQL: SELECT USER_ID, TITLE, FIRSTNAME, SURNAME, EMAIL_ADDRESS FROM ODS_LGA.VW_TBL_USER_PROFILE WHERE (USER_ID > 0) AND (USER_ID < 1000) When I run this report it completes in seconds and shows me the data. So my question is what's happening when I build the report using a Report Model as the "middle man"? Is the Report Model trying to return all of the data (~3 million rows) to the report which would then be filtered by the SemanticQuery??? That's just a guess, I don't really know how SSRS works, but I don't see what else could be happening.... Thanks for any assistance!