I have a 100.000+ record table and I need to report just one record.
I noticed that If I use the report filter with "Fields.id_field = ...." the report seems too get all data from the server, and then filter the desired record. If I filter the query with "WHERE id_field =..." the reports runs very fast.
Is this normal? If I should use database filtering (instead of report filtering): where should I set the query parameters (@id_field)?
Thanks in advance!
I noticed that If I use the report filter with "Fields.id_field = ...." the report seems too get all data from the server, and then filter the desired record. If I filter the query with "WHERE id_field =..." the reports runs very fast.
Is this normal? If I should use database filtering (instead of report filtering): where should I set the query parameters (@id_field)?
Thanks in advance!
2 Answers, 1 is accepted
0
Accepted
Hello Jorge,
As described in the Filtering Report Data topic, the report filters works on the reporting engine side and does not filter the data on the database server. That said, if you need exactly 1 record off 100,000 it is much better to filter the data on the data source before passing it to the reporting engine.
Currently Telerik Reporting depends on external data source objects and does not handle the data itself. Our short term plans include some improvements in this direction and I hope that once we start handling the data on our side, we can move the data filtering to the data source (of course if the data source can support such type of operations, like the database servers).
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
As described in the Filtering Report Data topic, the report filters works on the reporting engine side and does not filter the data on the database server. That said, if you need exactly 1 record off 100,000 it is much better to filter the data on the data source before passing it to the reporting engine.
Currently Telerik Reporting depends on external data source objects and does not handle the data itself. Our short term plans include some improvements in this direction and I hope that once we start handling the data on our side, we can move the data filtering to the data source (of course if the data source can support such type of operations, like the database servers).
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Jorge
Top achievements
Rank 1
Rank 1
answered on 03 Jul 2009, 11:27 AM
Telerik Reporting's filtering is extremely useful as one can do everything without code, but it will be great when this filtering is "translated" to database filtering to optimize data fetching.
Cheers!
Cheers!