Hi, I am new to using any reporting suite. Usually I query data from the db and manually parse it out and generate my html layout. I was hoping using a reporting toolset would make things easier.
I've been reading and following along some telerik reporting guides.
It looks like paramaters and filtering do not take place at the db-level and are instead after the data is pulled. This is a big problem for me. I need to use params when i pull the data. I could be pulling a million records if i can't have the report pull only the records for a specific userID and then report on it.
Is there any way to make it work like i expected it to?
Or am i going to have to stick to using a grid?
I've been reading and following along some telerik reporting guides.
It looks like paramaters and filtering do not take place at the db-level and are instead after the data is pulled. This is a big problem for me. I need to use params when i pull the data. I could be pulling a million records if i can't have the report pull only the records for a specific userID and then report on it.
Is there any way to make it work like i expected it to?
Or am i going to have to stick to using a grid?
1 Answer, 1 is accepted
0
Hi Matt,
We've already replied in your support ticket. Please restrain from opening multiple threads on the same matter as this only slows us down, contrary on people's believe that they would get higher priority. Here is the answer:
"It all depends strictly on your exact scenario you have. If the goal is to show thousands and millions of records, then yes, probably the best solution for you would be to use a datagrid control which is meant for showing data. Reporting solutions are not meant for showing data - they filter/sort/group that data according to some conditions and present this data in some form where the end goal is to extract knowledge and make conclusions. More info on what reporting is and what it is not is available in our White Paper.
Now, directly to your question - there is no limitation to how you bind your report (see support DataSources) and if you need to filter it on database level then you can do that. The NeedDataSource event handler provides all the flexibility you need for such purposes and you can see how it is used to bind a report to a stored procedure with parameters here. In this event you can build your query on the fly, change connectionStrings and everything else you might want to do before passing the data as datasource to the report. It is only when you use the built-in report filtering along with the report parameters when the whole data would be pulled, as the report needs it."
Kind regards,
Steve
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.
We've already replied in your support ticket. Please restrain from opening multiple threads on the same matter as this only slows us down, contrary on people's believe that they would get higher priority. Here is the answer:
"It all depends strictly on your exact scenario you have. If the goal is to show thousands and millions of records, then yes, probably the best solution for you would be to use a datagrid control which is meant for showing data. Reporting solutions are not meant for showing data - they filter/sort/group that data according to some conditions and present this data in some form where the end goal is to extract knowledge and make conclusions. More info on what reporting is and what it is not is available in our White Paper.
Now, directly to your question - there is no limitation to how you bind your report (see support DataSources) and if you need to filter it on database level then you can do that. The NeedDataSource event handler provides all the flexibility you need for such purposes and you can see how it is used to bind a report to a stored procedure with parameters here. In this event you can build your query on the fly, change connectionStrings and everything else you might want to do before passing the data as datasource to the report. It is only when you use the built-in report filtering along with the report parameters when the whole data would be pulled, as the report needs it."
Kind regards,
Steve
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.