To be short, I have a page which calls 16 stored procedures every time its loaded. With 50K people per day using that page, it gets slow. I am trying to combine these into 1 recordset / stored procedure and requery the results w/o another hit to the DB. The stored procedures are all the same with the exception of being filtered by a certain category ID and keyword. The keyword is full text indexed. I have tried calling a recordset set up like the stored procedure using the rs.Requery method, and it works great, except I cannot pass the full-text keyword to filter with. Using LIKE does not give me the same results as the full text CONTAINS. I also explored the possibility of sub-reports with SQL server, but am not sure if thats what I need. Could anyone shed a little light on this for me? Basically, I want to call a master set of data and then filter that data 16 times w/o another hit to the db.
Ok, I am going to bite. Why does the page call 16 stored procedures each time it loads? Tell us more about the application, data usage, number of rows returned, etc. Also, it appears that you have a solution in mind. Call the master dataset and filter without hitting the database. We can do this, but there is a caveat. If you return a small number of rows then you can refilter on the client side with no additional hits. If you are returning 1ks of rows, then we have another problem that needs to be addressed before we tackle the filtering.