Home/ Questions/Q 8650609
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T13:51:57+00:00

Here’s a problem I experience (simplified example): Let’s say I have several tables: One

  • 0

Here’s a problem I experience (simplified example):
Let’s say I have several tables:
enter image description here

One customer can have mamy products and a product can have multiple features.

On my asp.net front-end I have a grid with customer info:

something like this: 

Name   Address   
John   222 1st st     
Mark   111 2nd st

What I need is an ability to filter customers by feature. So, I have a dropdown list of available features that are connected to a customer.

What I currently do:
1. I return DataTable of Customers from stored procedure. I store it in viewstate
2. I return DataTable of features connected to customers from stored procedure. I store it in viewstate
3. On filter selected, I run stored procedure again with new feature_id filter where I do joins again to only show customers that have selected feature.

My problem: It is very slow.

I think that possible solutions would be:
1. On page load return ALL data in one viewstate variable. So basically three lists of nested objects. This will make my page load slow.
2. Perform async loazing in some smart way. How?

Any better solutions?

Edit:
this is a simplified example, so I also need to filter customer by property that is connected through 6 tables to table Customer.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The way I deal with these scenarios is by passing in Xml to SQL and then running a join against that. So Xml would look something like:

    <Features><Feat Id="2" /><Feat Id="5" /><feat Id="8" /></Features>

    Then you can pass that Xml into SQL (depending on what version of SQL there are different ways), but in the newer version’s its a lot easier than it used to be:

    http://www.codeproject.com/Articles/20847/Passing-Arrays-in-SQL-Parameters-using-XML-Data-Ty

    Also, don’t put any of that in ViewState; there’s really no reason for that.

    • 0