ObjectDataSource design question
-
I have a web page where I need to diplay some data that is retrieved tbough an ObjectDataSource. Behind the scense ObjectDataSource is populated through a SQL server stored procedure ( let's say GetData() ). This stored procedure returns around 10K rows and depending upon some criteria I need to dipaly this data in three different Grid view controls. My questions is 1. How can I split data in one recordset that can be used in these three grid views. 2. Is there any better way of doing it rahter than using objectDataSource. Any specific links and example code will be highly appreciated. TIA
-
I have a web page where I need to diplay some data that is retrieved tbough an ObjectDataSource. Behind the scense ObjectDataSource is populated through a SQL server stored procedure ( let's say GetData() ). This stored procedure returns around 10K rows and depending upon some criteria I need to dipaly this data in three different Grid view controls. My questions is 1. How can I split data in one recordset that can be used in these three grid views. 2. Is there any better way of doing it rahter than using objectDataSource. Any specific links and example code will be highly appreciated. TIA
imak wrote:
1. How can I split data in one recordset that can be used in these three grid views.
How do you want to split the data? By a specific number of rows? You could add some paging logic to your stored procedure to do this. If each grid view displays different types of data, you would need to write separate stored procedures.
imak wrote:
2. Is there any better way of doing it rahter than using objectDataSource.
The ObjectDataSource control allows data-bound controls to bind to custom objects/collections of custom objects. If you just want to bind a control to the results of a SQL Server query, use the SqlDataSource control.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
-
imak wrote:
1. How can I split data in one recordset that can be used in these three grid views.
How do you want to split the data? By a specific number of rows? You could add some paging logic to your stored procedure to do this. If each grid view displays different types of data, you would need to write separate stored procedures.
imak wrote:
2. Is there any better way of doing it rahter than using objectDataSource.
The ObjectDataSource control allows data-bound controls to bind to custom objects/collections of custom objects. If you just want to bind a control to the results of a SQL Server query, use the SqlDataSource control.
Paul Marfleet "No, his mind is not for rent To any God or government" Tom Sawyer - Rush
-
Hi, * As paul said you can implement paging logic so, that the Ods is not heavy. * why are you complecating the things? why don't you use 3 ods for 3 grid views -Ram.
Thanks Paul and Ram for your responses. I actually gave a simplified version of the actual problem. Let me provide detail so hopefully it will provide some clarification. There are actually 30 different web pages and number of grid ( and varios other controls) vary on each page (depending upon page, number of controls vary between 20 - 40). I am using objectDataSource as this product has multiple flavors that provides ability to connect to various types of data sources(SQL Server, oracle, mySQL etc). Now in order to populate all controls on one page I was trying to avoid going back and forth between database. That's why I do not want to bind individual controls with so many ods; rather return all possible rows in one stored procedure, Call this stored procedure to fetch all data and then on client side populate different controls by splitting data. Is this a reasonable design? If so, is it possible to split data within objectdatasource logic? If so, can you provide any code examples?